Enterprise DNA

Instead of Cloud Compliance DataMasker

Stop renting Cloud Compliance DataMasker. Own your test-data masking system.

We build your version around the records your team tests with, map your masking rules and exported Salesforce records, and run the review process with you.

The DataMasker pricing page lists $6.99 per user monthly and a $19,999 annual minimum. It does not state the currency. Confirm your current quote, as other vendor pages show different figures.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

A minimum annual commitment before your next test copy

DataMasker sells a native Salesforce masking service. The recurring work beneath it is choosing which fields to change, preparing test copies and keeping evidence of what happened.

payments

An annual minimum

The current pricing page lists a $19,999 annual minimum. Use your actual quote and currency when comparing it with a system you own.

group

A per-user price

The same page lists $6.99 per user monthly. Your own version can be scoped around the people who prepare and review test data.

layers

Multiple test environments

The vendor includes unlimited sandboxes. Each test environment still needs clear field rules, a responsible owner and a review process.

rule

Field-by-field treatment

DataMasker provides object and field masking rules. The equivalent decisions in your own system are explicit records with a reason attached.

sync

Native automation

The vendor describes running after a sandbox refresh and muting automation. We scope the connections your version needs around your actual refresh process.

fact_check

Evidence after each run

The vendor documents masking reports and audit trails. Your own version keeps the rules used, counts, reviewer decisions and exception history together.

Your own masking desk

Know which test copies need attention before anyone uses them

Rules

Every field has an explicit decision

An import stops when a field has no rule. Nothing becomes a trusted test value just because it appeared in an export.

  • check Erase fields outside the test purpose
  • check Replace identifying values with random substitutes
  • check Keep matching references connected within one import
  • check List every field kept unchanged and its justification

Copies

Bring related records across together

Import a batch of exported records, preserve their column order and reconcile how many records were processed.

  • check Test the import before writing any transformed records
  • check Reject duplicate identifiers and malformed input
  • check Repeat an identical batch without creating another copy
  • check Keep the exact rules used with each completed run

Review

A past decision does not excuse a changed copy

Readiness is recalculated against the current refresh, rules, retention date and unresolved work.

  • check Require a different reviewer label and an evidence reference
  • check Block acceptance when the retention review date has passed
  • check Flag earlier decisions after masking rules change
  • check Track unresolved exceptions with owners and due dates

Evidence

Prepare the handover from the records

Generate a masking evidence report, a handover draft and the weekly review in your own business name.

  • check Show counts and field treatments for each run
  • check Keep review decisions and their supporting references
  • check Read the week, attention list and retention review as reports
  • check Ask which copies changed after review across your own history

Make it yours

Design your own Cloud Compliance DataMasker replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Cloud Compliance DataMasker. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Cloud Compliance DataMasker replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Cloud Compliance DataMasker data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Three actual runs on invented demonstration records. No customer records are shown.

forum

Test Data Masking for Claude Code

Connected to your own database

Which test copies and follow-ups need attention?

ISSUE

Item
Confirm training copy disposal
Owner
Theo West
Due
2026-11-04
Detail
Partner training

ISSUE

Item
Review regional field justification
Owner
Aroha Bell
Due
2026-11-09
Detail
Release rehearsal

NO-CURRENT-RUN

Item
Release rehearsal
Owner
Aroha Bell
Due
2026-11-07
Detail
No masking run for the current refresh

RETENTION

Item
Partner training
Owner
Theo West
Due
2026-11-05
Detail
Retention review due or expired

UNREVIEWED

Item
Mask 2026-11-07 39c10486
Owner
Theo West
Due
2026-11-07
Detail
Partner training

UNREVIEWED

Item
Mask 2026-11-07 ab0f2f32
Owner
Mira Chen
Due
2026-11-07
Detail
Partner acceptance

Ask it anything

Ten questions for your own review process

Each answer comes from the working demo. Add your own records and rules to make the review yours.

chat_bubble Which refreshes have no masking run yet?
chat_bubble Which runs were reviewed against rules we have since changed?
chat_bubble Which copies have passed their retention review date?
chat_bubble Which fields are deliberately kept and why?
chat_bubble Who has unresolved work before a test copy can be accepted?
chat_bubble How many fields are erased, replaced or kept for each object?
chat_bubble Which run contains each imported object and how many records?
chat_bubble Who accepted or rejected each run and what evidence did they record?
chat_bubble Which test purposes and owners sit behind stored copies?
chat_bubble Who changed the rules or recorded a refresh?

Switching

How to switch from Cloud Compliance DataMasker

A move usually involves exporting the Salesforce records you use, mapping your fields to masking rules, then testing and checking the imported data before you retire the current tool.

  1. 1

    Export the records

    Export the Salesforce records that Cloud Compliance DataMasker operates on, using the export options your account allows. These are usually CSV or Excel files, but check with Cloud Compliance DataMasker for the options available to you. The records can be brought across, but the export does not include DataMasker’s proprietary package configuration, historical jobs or native automation.

  2. 2

    Map fields to rules

    Before loading records, map each exported field to a masking rule and decide which test purpose and owner the copy belongs to. Every imported column needs a rule. Plan separately for any DataMasker package settings or historical jobs you want to carry forward, because they do not transfer automatically with the Salesforce records.

  3. 3

    Test, then load

    Use the import path for the exported Salesforce object files and run a test first. The import works with a directory of CSV files, with each field mapped to a rule before records are written. Keep the original exports separate from the test copy, and do not use transformed records in a live system.

  4. 4

    Check the import results

    Review what the import flags before relying on the new test copy. It checks for missing or unclassified fields, malformed files and missing or duplicate record IDs, and the whole directory is treated as one transaction. Reconcile the imported object and record counts against your exports, then inspect masked output, kept fields and relationships before accepting a run.

  5. 5

    Run both, then switch

    Keep Cloud Compliance DataMasker running while you check the new process against your actual workflows and controls. Confirm that the records, rules, reviews and any required connections or automation are covered before you switch off the old tool. The base works on local CSV copies and does not mask a live Salesforce sandbox or restore files to Salesforce, so include those needs in your check.

construction

Where the real effort goes

The main work is usually mapping your own fields and masking rules, then deciding which history to bring across. DataMasker package settings and historical jobs need separate mapping, and native connections or refresh automation may need to be scoped. When you have Enterprise DNA run your version, Enterprise DNA handles the mapping and record migration as part of the custom work.

Not ready for a call?

Get your Cloud Compliance DataMasker switch plan by email

We will send you the step-by-step plan for moving your business off Cloud Compliance DataMasker, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Start with the free base or have your version built

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, run npm install, npm test and npm run demo.
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor.
  3. 3 Map each field, then run import datamasker on your authorised Salesforce CSV exports with --dry-run first.
  4. 4 Inspect the transformed records, reconcile relationships and record the review evidence.
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your records, masking rules and review responsibilities mapped
  • check Your exported Salesforce records brought across and reconciled
  • check Your refresh process and native connections scoped and tested
  • check A web front end or a different stack if your team needs one
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Access, backups and restore checks set up for your version
  • check The weekly review and handover evidence prepared
  • check Your field rules and connections maintained as work changes
Book a call with Sam

Questions

Instead of Cloud Compliance DataMasker, answered

Does this replace masking inside Salesforce? expand_more

The free base prepares local test copies from exported Salesforce records. Enterprise DNA can build the native connections and refresh automation your version needs. We check those requirements against your current DataMasker workflow before you switch.

Can I bring my existing records and rules? expand_more

Yes. The free base imports exported Salesforce records after each field has been mapped to a rule. DataMasker package settings and historical jobs need separate mapping. Enterprise DNA handles that work as part of your custom version and reconciles what has carried across.

Does a passed review mean the data is anonymous? expand_more

No. Replacing names is one control. Kept fields, combinations of values and access arrangements still need inspection. The system records that inspection and flags changed conditions. The responsible reviewer decides whether the copy is suitable for its purpose.

Why does your price comparison differ from another vendor page? expand_more

The pricing page checked for this comparison lists a $19,999 annual minimum and $6.99 per user monthly, with no currency stated. Other vendor pages show different figures. Bring your current quote so the comparison uses the terms you actually pay.

What does Enterprise DNA charge? expand_more

We agree one setup fee and then a retainer for your version. The scope covers the records, rules, connections and ongoing work you need. There is no fixed service price on this page.

Bring your masking quote and one test-data workflow

Spend 30 minutes with Sam. Compare your current DataMasker bill, the records you need for testing and the connections your team relies on. We will work through what your own version needs and whether the switch makes sense.

Book a 30-minute call with Sam Get the free version

Test Data Masking for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Cloud Compliance DataMasker?

Get your version built