Skip to main content

Getting Started with Sandbox Seeding and Compliance

Gearset's Sandbox Seeding and Compliance product gives your team the tools to seed sandboxes with realistic data, keep that data compliant, and test and develop with confidence.

Written by Aga Peryie
Updated this week

Gearset's Sandbox Seeding and Compliance license includes access to three tools:

Sandbox Seeding

Seed realistic data directly into your Salesforce sandboxes from production (or another sandbox). You can filter the data you want to move, and Gearset will give you a clear visual map of object relationships, so you can see exactly what's available and choose precisely what gets included in your deployment.

In-Place Masking

Apply masking rules directly within a Salesforce org to anonymise sensitive data in place. Designed with compliance and security in mind, In-Place Masking helps you meet data protection requirements and ensure sensitive customer information is never exposed in non-production environments, without the need for manual anonymisation or lengthy Apex scripts.

Data Deployments

An advanced tool for configuration data development, Data Deployments lets you move config data up and down your pipeline - between any two Salesforce orgs. Whether you're promoting data through environments or pulling it back for review, you have full control over which records are moved, how they're upserted, and what gets masked along the way.

Enabling data deployments in Gearset

By default, data deployments in Gearset are disabled and Gearset will not access any data in any of your orgs. To enable data deployments, you must manually enable it via the account page in the app clicking on the Backup & archiving section.


Only a team owner can do this, as well as this, please ensure that the Team Owner has an active license assigned to their user. If you’re not a team owner you’ll need to ask them to enable this on your Gearset account.



Together, these tools allow you to seed your sandboxes with the data your teams need, stay compliant by masking sensitive information, and give developers and testers the confidence to work in realistic, safe environments.

Did this answer your question?