Seen a few comments like this. Goal is for clients who often need to split out of their current org or have a badly broken org, want to get to a minimal state and migrate to a new production environment. Another use case is staging data and combining from multiple orgs. All of this requires >10K records and ability to target production. Also trial accounts - isn't that considered production? Only way to create a clean NPSP is through trialforce - can't do it in dev environment. Why do you even have a restriction?

We've begun work on adding data migration support to Gearset.

You can read more about what we've decided to do from our blog post: https://gearset.com/blog/migrate-salesforce-data-gearset-update

This feature would be very definitely opt-in. We will like put it behind another pricing tier as well to make 100% sure that users know what they are signing up for, and that the correct security and compliance audits have been completed.

As always, security is our top concern!

Kevin
CEO, Gearset

This is a concern for us. We have strict security policies regarding the data in our org. When we submitted our purchase request we skipped part of the security review because Gearset did not access our data. This may require a new security review and may result in Gearset being rejected.

I just want to warn that there should be some sort of configuration setting or some mechanism (maybe managed by Gearset support) to turn this on/off.

If Gearset starts accessing our data, we could be forced to stop using it and it's been such a life saver for us :(

What I'm looking for is a tool to migrate data between 2 Salesforce-orgs. For testing and demo purposes.
This would include lots of custom objects and lots of relationships between these objects.
So the tool would have to keep that in mind while migrating the data (preferably without using External Id's).
It would also include 100K+ records over these several objects (probably 50-80+ objects).
Similar to a full copy sandbox, without requiring that license :). And also being able to migrate the data between any 2 org's, which aren't connected such as sandbox/production.

This would be awesome I have a few applications in SF where we use data objects for configuration - we can't use custom metadata types because we need all the facilities of a custom object. But, then we need to deploy that data between orgs and it's a pain. If gearset could handle that, it would be outstanding.

Even comparing custom settings would be a big win. In my mind, SF should have made them metadata in the first place and we're stuck with a bunch of legacy orgs where we can't just migrate to custom metadata types.

This would be a game changing feature if you guys did it well!