Use real production data to seed sandboxes while respecting data confidentiality. Disguise personal data and sensitive information with configurable data masking.
Use real production data to seed sandboxes while respecting data confidentiality. Disguise personal data and sensitive information with configurable data masking.
Gearset’s data deployment tool makes our dev sandboxes really powerful and relevant. It means developers can work with real org data in context, and make informed decisions at every stage of production. If you don’t have sight of example data, you can make all sorts of assumptions which may not be correct.
Whether critical business data or customers’ PII, your Salesforce org holds sensitive information. Confidentiality rules and data protection regulations such as the CCPA often restrict what you can do with sensitive information. The EU’s General Data Protection Regulation (GDPR), in particular, applies to the use of personal data both inside and outside the EU - whether you’re based in the US, India, Australia or elsewhere.
We want our users to benefit from the full range of Gearset’s DevOps and backup tools without them worrying about the confidential nature of their business information and customer data. Gearset’s data compliance add-on allows you to do this, giving you extra peace of mind by letting you mask your sensitive data to comply with rules on data protection.
Data masking means your team can use real data from production while masking personal information and sensitive business records during data deployments to development orgs. When you turn on data masking, Gearset substitutes your real data for fictitious data in the same format. So the data deployed to your target looks and behaves like authentic data, which is valuable for realistic and complex testing. In other words, your developers can build features, test changes and fix bugs using realistic datasets while, at the same time, making sure they comply with data protection requirements.
Gearset lets you turn masking on or off for individual fields and gives you some useful toggles if you want to mask all fields of a particular type. For custom fields, you can decide on the type or format of the placeholder data used to disguise the real data, such as random text and integers, fake phone numbers or simple Boolean values. This helps make sure you’re able to test your code with realistic datasets.
Absolutely. With Gearset, you can migrate and deploy Salesforce data and CPQ or Vlocity configuration between any of your connected orgs.
Gearset enables you to deploy up to 100,000 records between two Salesforce orgs in a single deployment. But bulk loading data from a file such as a CSV isn’t supported. If you’re looking to import Salesforce data from a file, there are native Salesforce data deployment tools available (such as Data Loader, Salesforce DX Data Move Utility and the CLI).
Org data for sandbox seeding purposes is never permanently stored by Gearset, but it does pass through our servers to allow us to run data deployments. After a data deployment completes, the data is automatically disposed of by the service. As with metadata, it is encrypted at all times when in transit or at rest. Learn more on our security page.
When creating a Gearset account, users choose a data storage location — either the US, EU or Australia. All user data, including metadata and any organization data is then handled solely by an AWS data center in the relevant region — either Oregon (US West 2), Ireland (EU West 1) or Australia (AP Southeast 2). This includes any backups taken as part of our disaster recovery program.
Gearset is a UK company, and we have our headquarters in Cambridge, UK. We don’t outsource any of our development — all of which is handled in-house by our expert team in the UK. Support is provided by our expert teams in the UK and US.
For more information on our security standards see our security page.
Yes. Data governance policies often mean personal data can’t leave the production environment — Gearset’s data masking obfuscates your data during sandbox seeding, so you have representative data in your testing environment without compromising data privacy.
If there are data deployments you need to do regularly or repeat to multiple different orgs, you can save data deployment templates to easily replicate the deployment setup. So you can run the same deployment to a different org in just a few clicks.
Yes. Gearset automatically keeps a full audit trail of your data deployment history in the app. This gives you details of who ran the deployment and when, as well as the source and target orgs. Download a file of which records were deployed successfully and which weren’t.