This content and service to the Salesforce community are essential to us here at CapStorm. When it comes to helping maximize your data, we feel a sense of duty to help others solve some of the most common and complex challenges related to their Salesforce data. Join us on LinkedIn, Youtube, Twitter, or CapStorm.com!
In last week’s episode of Data Unleashed, Drew gave you part one of the tale of a company with just six days to divest its Salesforce org from its parent company. In Episode 17, part two takes a deeper dive into the methods the company’s Salesforce admin and software engineer used to complete that monumental task.
While it might seem daunting, there are ways to pull a carbon copy of Salesforce down into a local SQL environment that you can control. It will remain behind your firewall and with its referential integrity intact, even as CapStorm’s tools push the data to the new target. The software engineer, introduced in our previous episode, had never even used Salesforce before, but the steps they took allowed them to be successful in their data migration endeavor.
How did they do it? They were able to build metadata configurations, migrate them, and build the data configurations, which were tested in a partial-copy sandbox on the way to the target Salesforce org. This allowed them to validate that their data was moved correctly.
With CapStorm’s tools, you no longer have to worry about pesky spreadsheets bogging you down. Just as this company discovered, there are ways to move massive hierarchies of data – hundreds or even thousands of objects deep in your data model – in just one operation. Whether it’s data loading, sandbox seeding, or an org migration/merger/split, there is a way to successfully complete the task in a timely manner.
Tune in each Tuesday for more episodes of Data Unleashed, and discover all the tips and tricks to help you get more value from your investment in Salesforce. We would love to hear from you if you are looking for a fast, easy, and highly secure way to protect your Salesforce data & metadata! Reach out to an SFDC data expert or send us a message on LinkedIn!
My name is Drew Niermann, and this is Data Unleashed, the video blog series dedicated to helping you get more out of your investment in Salesforce.
There are ways to pull a carbon copy of Salesforce down to a local SQL environment that you control, it’s going to be behind your firewall, and it will preserve all the referential integrity. And oh, by the way, when you segment or segregate this data and get ready to migrate it to the target, the tooling that you’re going to use will actually preserve all of the referential integrity of the data model as it pushes to the target.
So the two folks that I had the pleasure of working with, one of them was a Salesforce admin and the other was a software engineer that had never even touched Salesforce before. Long story short, they built a couple of metadata configs, migrated the metadata, they built the data configs, and tested them in a partial copy sandbox on the way to the target org to validate that the data actually got moved appropriately. They saves their business and 80 sale people got to keep their jobs because they migrated the data so quickly, in such a short amount of time.
So what I want you to know here is that there are ways to migrate data and metadata between different orgs. You don’t have to use spreadsheets, there are ways to move massive hierarchies of data, hundreds or even 1000s of objects deep into your data model as a single operation.
So if you’ve ever been in the situation where you’ve had to data load for sandbox seating, or if it’s an org migration, merger or split, this is something that I would love to talk to you about. Drop me a DM on LinkedIn if you’d like to chat.
And thank you so much for watching Data Unleashed. My name is Drew Niermann, have a great day.