Sandbox seeding
Building features and debugging issues without realistic test data is unreliable. But creating your perfect test data is easy with the right Salesforce sandbox seeding solution. Gearset plans and executes complex data deployments for you — just pick the records you want to deploy, and we’ll handle the rest.
Users rate Gearset’s data deployment solution 10/10
Giving credit where due: I had to move data from production to a developer org this week. The relationships were plenty and I couldn’t fathom doing it manually 1 file at a time. Thanks to Gearset the data migration was easy breezy including anonymizing sensitive data!
Technical Product & Delivery Architect, CRMified
Obfuscate commercially sensitive data or personally identifiable information (PII) for full confidentiality and compliance with the CCPA or GDPR.
Maintain a complete audit trail of data migrations between environments, with an automatically generated data deployment history.
Testing features with real-world data in sandboxes takes the stress out of deploying to production. And with Gearset, you can manage the whole process on one platform.
Gearset instances and storage are hosted on Amazon Web Services (AWS), the same data centers trusted by Salesforce and Heroku.
Secure OAuth authentication ensures that user passwords are never stored on our servers so you can connect safely to all of your Salesforce orgs.
Gearset ensures that data is encrypted both at rest, using AES 256, and in transit, using the latest SSL standards (SSL Report).
Org data 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, Canada, 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), Canada (CA Central 1), 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 do not outsource any of our development — all of which is handled in-house in the UK. Support is provided by our expert teams in the UK and US.
Gearset’s service architecture and policies are designed to be in full compliance with GDPR. For more information on this, see our GDPR compliance statement.
Absolutely. With Gearset, you can migrate and deploy your Salesforce data between any two organizations. Seed data from production, another sandbox, or from a backup, with support for Developer, Developer Pro, Partial Copy, and Full Copy sandboxes, as well as SFDX scratch orgs.
Gearset’s data deployments are intended for sandbox seeding, with optional masking of sensitive data to ensure compliance. It’s possible to deploy config data for managed packages, such as Field Service Lightning. Gearset supports deploying CPQ and Salesforce Industries (Vlocity) like metadata.
You can deploy the following binary data types: File Attachments, ContentDocument/ContentVersion files, Documents, Static Resources, and Custom settings data.
A developer sandbox can be refreshed once a day, and is intended for development and testing in an isolated environment. This sandbox type only includes a copy of your production org’s metadata.
If you want to populate sandbox environments with a complete copy of your production org, including all data and metadata, then a full sandbox is needed. A full sandbox is mainly used as a testing environment and is the only sandbox type to support performance testing, load testing, and staging. This sandbox can only be refreshed once every 29 days.
Sandbox refresh is a great way to ensure the metadata between your sandbox and production is aligned. Depending on the type of orgs you use, a refresh may also include some data seeding too. However, there are restrictions on how often a sandbox can be refreshed, so sandbox seeding is the best way to keep your sandbox populated with realistic test data between refreshes.
For sandboxes that aren’t populated with data during the refresh process, sandbox seeding is a quick and easy way to get test data into these environments.
Gearset can migrate 100,000 records in a single data deployment and there are no limits on the number of data deployments you can run to and from your orgs. However, you may be limited by the storage capacity of the org you have.
Developer sandbox: These normally have a limited amount of file and data storage of 200MB, but keep in mind this is usually still plenty for most development tests and tasks.
Developer Pro sandbox: This sandbox is similar to the Developer sandbox, but has a storage capacity of 1GB.
Partial Copy sandbox: The storage capacity on these sandboxes is 5GB.
Full Copy sandbox: This sandbox has a storage capacity that matches your production org.
Arrange a tailored demo with our DevOps experts. Kick off the process with a 15-minute call to discuss your requirements.
Choose an upcoming live demo to attend and see Gearset in action with the option to ask live questions.
Talk to an expert in minutes with a 4.9/5 customer happiness rating.
