What Tool Should You Use For Your Data Migration?

This post is part two of an ongoing series about Data Migration. This guide can be used to implement solutions for salesforce.org data migrations, Apttus CPQ data migrations, as well as Salesforce CPQ data migrations. This will also give you some ideas about legacy data from other CRM or ERP systems. For part one of the series, click here.


Welcome Back!

Welcome back to part two of our Data Migration series! Here we will explore the tools you will need for your data migration.

What to Consider:

When considering a tool for data migration (especially when migrating data periodically from ERP systems), you will need to use the tool that has scheduling capability and SFTP support. You will also need to make sure to apply mapping and transformation in the tool you have selected and build the process from there. So, let’s begin!

Which Tool Should I be Using?

With numerous tools out there for data migration, it can be challenging to know which one is the right one for your project. There are numerous tools to choose from in AppExchange and we sifted through them all to highlight some of the best. Here are some tools to consider for different types of migrations:

  • Org merge data migrations: Salesforce Data Loader, Dell Boomi, Jitterbit Data Loader.
  • Sandbox data migration for Salesforce: Salesforce Data Loader, Dell Boomi, Jitterbit Data Loader.
  • Sandbox migration for Apttus: The Apttus Migration App, Xauthor for Excel, Salesforce Data Loader, Dell Boomi, Jitterbit Data Loader.
  • Legacy data from other CPQ or ERP systems: Salesforce Data Loader, Dell Boomi, Jitterbit Data Loader.

Next Steps:

Once you have picked a tool and are finished with both the mapping exercise and the building process, use your developer org to do some testing to make sure everything is working properly. Do this testing with minimal records (50 to 100) and check that the target org comes up with the right data. Now you are ready to capture metrics! First, gather all the data and run it against the full sandbox (QA or UAT). Next, measure the time it takes to load. This will give you an idea of how to handle the cut over plan.

(Helpful Hint: Data Loader will allow you to quickly process 2000 records per transaction for Bulk API functions.)

Once you capture these results, you will be ready to make a plan for Production load. If you have a large amount of data (more than 100K), consider splitting the source csv file and run it in multiple instances in the same object. Finally, load any incremental data and complete your data migration!

Let’s Talk Testing:

Even when the process is complete, testing is still a necessary step in the upkeep and maintenance process. Unit testing with minimal data should be continuously completed because it is the best way to determine that the processed data is correct. If any issues are found on the full data in the QA/UAT org, it can be fixed by loading a few updated processes using the tool that you choose.


That wasn’t so bad, right? Now you are ready to conquer your own data migration process!



About Bala Sadayappan 

Bala is a Technical Architect in Statera’s Salesforce CRM Practice. Bala has Eighteen years of experience in IT as a Technical Lead / Architect and maintains certifications in Salesforce.com (Administrator & Developer), Apttus Configure Price Quote (CPQ) and XAE.