Product comparison
DataMasker vs Salesforce Data Mask & Seed
Both tools mask personal data inside your Salesforce org. Data Mask & Seed is Salesforce's built-in app. It needs the Salesforce Data Mask add-on license, which Salesforce lists at 10% of net spend (subject to change). DataMasker is our AppExchange package, priced per user. Data Mask & Seed fits simple, first-party masking. DataMasker fits pipeline-driven sandboxes, post-refresh cleanup, and large jobs.
We sell DataMasker. Every claim about Salesforce's product below links to Salesforce's own documentation, and where Salesforce doesn't document something, we say so.
Salesforce documentation last checked .
Why this comparison comes up now
Salesforce's old Data Mask managed package lost support on July 9, 2026. Its display becomes read-only on December 31, 2026. Salesforce's replacement is Data Mask & Seed, a Core app available since the Summer '26 release.
Policies from the old package do not carry over. Salesforce asks you to create new policies in Data Mask & Seed. Custom libraries are shared between the two, so those do not need rebuilding.
So every team on the old package is rebuilding its masking setup anyway. That makes it a sensible time to compare options. The full timeline is on our Data Mask end-of-service page.
Where each one fits
Plenty of orgs are well served by Data Mask & Seed. Match your situation to a column.
Data Mask & Seed fits when
- You already hold the Salesforce Data Mask add-on license, or will buy it through your Salesforce contract.
- You want a first-party Salesforce tool with no package to install.
- Your masking is library substitution: names, emails, phone numbers, addresses.
- Your jobs stay under 20 million records, where Salesforce preserves data distributions.
- One policy on refresh is enough for every sandbox.
- You run a Professional Edition org.
- You need masked values in many locales.
DataMasker fits when
- A CI/CD pipeline creates your sandboxes and masking must be a step in it.
- You need Remote Site Settings, custom labels, and user emails fixed in the same run.
- Jobs run past 20 million records and cross-object consistency still matters.
- Different sandboxes need different masking profiles.
- Some fields need regex patterns or Apex-based encryption.
- You would rather pay per user than a percentage of net spend.
Feature by feature
The Data Mask & Seed column reflects Salesforce's Help documentation and its pricing page, checked . On pricing, Salesforce states: “This page is provided for information purposes only and subject to change. Contact a sales representative for detailed pricing information.” The DataMasker column reflects our product pages and AppExchange listing.
| Salesforce Data Mask & Seed | CC DataMasker | |
|---|---|---|
| How it is delivered | Core app built into the platform since the Summer '26 release (July 18, 2026). Nothing to install. | Managed package installed from AppExchange. |
| Editions | Professional, Enterprise, Unlimited, and Developer, with the Salesforce Data Mask add-on license. | Enterprise and Unlimited. See the AppExchange listing for the full list. |
| User access | Data Mask And Seed User permission set license, then the Data Mask And Seed User permission set. | DataMasker permission set, or the System Administrator profile. |
| List price | 10% of net spend (Salesforce list price, subject to change). | Per user, per month, with an annual minimum. Current figures are on our pricing page. |
| Where masking runs | Inside your Salesforce org. Policies are built in production; jobs run only in sandboxes. | Inside your Salesforce org. Non-production orgs only. |
| How a job starts | Run Now, a schedule (once, daily, weekly, or monthly), or Run on Refresh. | After sandbox create or refresh, from a CI/CD pipeline through a REST API, or on a schedule. |
| Different masking per sandbox | One policy at a time can be set to Run on Refresh. Other policies run by hand or on a schedule. | Multiple named masking profiles, for example Developer, QA, and Demo. |
| Trigger from a DevOps pipeline | Salesforce doesn't document an API or external trigger. | Yes. REST API, used with Copado, Flosum, Jenkins, Gearset, AutoRabit, and GitLab. |
| Automations during masking | Bypasses workflow rules, triggers, validation rules, and managed-package automations at job start. Some deletes and Duplicate Detection are not bypassed. | Mutes Flows, Process Builders, and Apex triggers. Suppresses outbound email and external callouts. |
| Post-refresh cleanup | Deletes Case Comments, Email Messages, and Chatter Comments on request. Salesforce doesn't document updating Remote Site Settings or custom labels. | Updates Remote Site Settings and custom labels, removes the .invalid suffix from user emails, deletes files, case comments, and tasks. |
| Replacement values | Built-in and custom libraries. A locale per policy (35+ languages). Einstein can generate library entries. | Names, emails, phones, addresses, date offsets, numeric ranges, picklists, regex patterns, and Apex-based encryption. |
| Finding PII fields | Proactive PII detection from each field's Sensitivity and Categories values. | Pre-built templates for standard objects. Custom fields added by hand or found with Personal Data Discovery. |
| Record filters | Yes, per object, with AND or OR conditions. | Yes, filter conditions per object. |
| Consistency across objects | Not applied to identical fields across objects once a job exceeds 20 million records. | Related objects are grouped and sequenced so masked values carry across related records. |
| Volume limits | 350 million records per job (job is canceled if over). 12 jobs per sandbox per rolling 24 hours. | No published per-job cap. |
| Published throughput | Salesforce doesn't publish a throughput figure. | Up to 5 million records an hour. 99 million records in 24 hours. |
| Shield Platform Encryption fields | Can mask fields encrypted with Field Level Encryption. | Works alongside Shield. Masks the decrypted values. |
| Synthetic data and seeding | Listed by Salesforce as coming soon. | No. DataMasker masks existing records. It does not generate them. |
Licensing and cost
Data Mask & Seed is built in, and it still needs a license. Salesforce's Help lists it as available in Professional, Enterprise, Unlimited, and Developer Editions “with the Salesforce Data Mask add-on license.” Each user also needs the Data Mask And Seed User permission set license. Salesforce's pricing page lists Data Mask & Seed at 10% of net spend.
Salesforce doesn't document whether an existing entitlement to the old Data Mask package covers Data Mask & Seed. Ask your account executive, and get the answer in writing. Ask too what 10% of net spend comes to on your contract.
DataMasker is a separate subscription, priced per user per month with an annual minimum. It includes unlimited sandboxes. Current figures are on our pricing page. The two pricing models scale differently. A percentage of net spend tracks your whole Salesforce contract. A per-user price tracks headcount. Model both against your own numbers.
What happens on a sandbox refresh
Data Mask & Seed
- You build policies in production. You can't run jobs there.
- On every sandbox create or refresh, all production policies are copied into the sandbox. Any existing sandbox policies are overwritten.
- If a production policy has Run on Refresh turned on, it runs automatically. Only one policy can have Run on Refresh at a time.
- At job start, it bypasses workflow rules, triggers, validation rules, and automations from managed packages.
- It can delete Case Comments, Email Messages, and Chatter Comments from the Home tab. Those deletes don't bypass automations.
- Salesforce doesn't document updating Remote Site Settings, custom labels, or user email addresses after a refresh.
Sources: Policies Tab, Run a Masking Job, Home Tab
DataMasker
- Masking starts after a sandbox create or refresh, from a pipeline through the REST API, or on a schedule.
- Different sandboxes can use different named masking profiles.
- It mutes Flows, Process Builders, and Apex triggers during the run, and suppresses outbound email and callouts.
- It deletes files, case comments, and tasks.
- After masking, it updates Remote Site Settings and custom labels and removes the .invalid suffix Salesforce adds to user emails on refresh.
Details: How DataMasker works, DevOps integration
Limits Salesforce documents for Data Mask & Seed
Quoted from Data Mask & Seed Requirements and Limitations. Salesforce asks you to read this page before you start. These limits matter most for large orgs and heavy automation.
Above 20 million records in a job
“The app doesn't preserve existing data distributions in the sandbox. … The app doesn't apply consistent field masking across objects.”
Per-job maximum
“Per masking job, Data Mask & Seed supports masking a maximum of 350,000,000 records. … If the job exceeds this limit, Data Mask & Seed cancels the job, doesn't perform any masking”
Jobs per sandbox per day
“Per sandbox, Data Mask & Seed supports running a maximum of 12 masking jobs during the current 24-hour rolling window.”
User records
“When you include the User object in a masking policy, Data Mask & Seed masks only the following types of users: PowerCustomerSuccess CustomerSuccess CspLitePortal PowerPartner Partner”
Automations on some deletes
“Data Mask and Seed doesn't bypass automations when deleting records in the following scenarios: When deleting the Feed Items and History records of masked sandbox objects, during a masking job”
Duplicate Detection
“Data Mask & Seed doesn't bypass the Duplicate Detection automation. Therefore, duplicates may be created, unless the user manually disables the automation before the masking job”
What Salesforce lists as coming soon
Despite the name, Salesforce lists seeding in Data Mask & Seed as coming soon. Its retirement article (updated October 5, 2026) lists these under “More enhancements are coming soon”:
- Generating synthetic data to populate an empty sandbox.
- Filling empty fields with new masked values.
- Seeding, including Data Cloud seeding and AI seeding.
The same article says performance improvements are coming on November 26. We will re-check this page after that date.
Salesforce separately documents Seeding by Own from Salesforce, listed with the Data Mask managed package (Legacy) add-on license. DataMasker does not seed. It masks the records a refresh copies from production.
DataMasker vs Data Mask & Seed: common questions
No. Salesforce's documentation lists it as available in Professional, Enterprise, Unlimited, and Developer Editions with the Salesforce Data Mask add-on license. Each user needs the Data Mask And Seed User permission set license. Salesforce's pricing page lists Data Mask & Seed at 10% of net spend and says the page is provided for information purposes only and subject to change. It needs no installation, which is a different thing from needing no license. Ask your account executive what it costs on your contract.
Not according to Salesforce's retirement article for the old managed package, updated October 5, 2026. It lists generating synthetic data, filling empty fields, and seeding under enhancements that are coming soon. Salesforce separately documents Seeding by Own from Salesforce, which its Help lists with the Data Mask managed package (Legacy) add-on license. If seeding matters to you, ask your account executive which product and license you would need.
Salesforce doesn't document an API or external trigger for Data Mask & Seed. Its Help pages describe three ways to start a job: Run Now, a schedule, and Run on Refresh. If your sandboxes are created by a pipeline and masking has to be a pipeline step, confirm the integration path with Salesforce before you design around it. DataMasker exposes a REST API for this.
You build policies in production. Each time a sandbox is created or refreshed, Data Mask & Seed copies all production policies into the sandbox and overwrites any policies that were already there. If one production policy has Run on Refresh turned on, that policy runs automatically. Only one policy can have Run on Refresh at a time. Jobs run only in sandboxes, never in production.
No. Salesforce says new functionality is only available through newly created policies, so you create new policies to replace your existing configurations. Custom libraries do not need migration. You can run the old package and Data Mask & Seed side by side, but if both have Run on Refresh turned on, only the Data Mask & Seed policy runs. The old package has been unsupported since July 9, 2026 and becomes read-only on December 31, 2026.
Above 20 million records in a job, it doesn't preserve existing data distributions and doesn't apply consistent masking to identical fields across objects. A job is capped at 350 million records and is canceled without masking anything if it exceeds that. A sandbox can run at most 12 masking jobs in a rolling 24-hour window. When the User object is in a policy, only PowerCustomerSuccess, CustomerSuccess, CspLitePortal, PowerPartner, and Partner users are masked. Some deletes don't bypass automations, and Duplicate Detection is not bypassed.
When you already hold the Data Mask add-on license or are happy to buy it through your Salesforce contract, you want a first-party tool with no package to install, your jobs stay under 20 million records, one masking policy on refresh is enough, and you don't need masking triggered from a pipeline. It is also the option for Professional Edition orgs, which Salesforce lists and our AppExchange listing does not.
When a pipeline creates your sandboxes and masking has to run as a step in it, when you need post-refresh cleanup such as Remote Site Settings, custom labels, and user emails handled in the same run, when jobs are large enough that cross-object consistency above 20 million records matters, when different sandboxes need different masking, or when you need custom logic such as regex patterns or Apex-based encryption.
Sources
All checked .
- Salesforce Help: Data Mask Managed Package Retirement (KA 005299299) Updated October 5, 2026. Support end date, read-only date, Core app, coming-soon list, policy migration.
- Salesforce Help: Protect Sensitive Data with Data Mask & Seed Editions, add-on license, how jobs run.
- Salesforce Help: Data Mask & Seed Requirements and Limitations Permissions, record limits, job concurrency, automation bypass limits.
- Salesforce Help: Data Mask & Seed Policies Tab Run on Refresh, policy copy on refresh, PII detection, Shield fields.
- Salesforce Help: Run a Masking Job Sandbox-only jobs, automation bypass at job start.
- Salesforce Help: Define Masking Policy Schedules Schedule options.
- Salesforce Help: Data Mask & Seed Home Tab Deleting Case Comments, Email Messages, and Chatter Comments.
- Salesforce Help: Populate and Secure Data Sets with Seeding Seeding by Own from Salesforce and its license.
- Salesforce: Data Privacy & Compliance pricing Data Mask & Seed list price.
- AppExchange: DataMasker listing Editions, pricing model, feature list.
Not sure which one fits your org?
We will walk through your sandboxes, refresh process, and record counts with you, and tell you plainly whether Data Mask & Seed covers it. No obligation to switch.