When you are converting the data or the Meta data from one system to the other, user mapping is a very essential function. You must have a clear concept about the user Ids in respect to the user names. As the user mapping process is difficult to ensure the accuracy of the record ownership, you must remember the following things before the migration:
Possess Licenses: If you are planning for data migration from one instance to the other instance of the Salesforce, then try to possess some eligible licenses. After the migration process, if there are issues, the old instances will resolve issues by investigating.
Appexchange App: You may try re-checking all the applications through the Appexchange. Though most of the instances remain active for many years, many apps remain unused for a long time. When the data migration process starts, you can identify all the unused apps and can uninstall them.
Existing Profiles of the Organization: When you are involved in a data migration with huge records, you may consider revisiting the existing profiles of the organization. It is very critical that the foundations are to be set up accurately with proper security system.
Migration of Codes: When you are continuing the migration of the codes, you must be extra cautious. Ensure that all the apex classes are properly placed in the sequential order. If there is anything wrong in the order, the final outcome may lead to an incorrect sequence of the Apex Programs.
Watch Your Space: As you are including additional data into the instances of Salesforce, make sure that you have enough space. If you are close to your permitted limits, you may call a representative of Salesforce for buying some additional space. To know more about the additional space of data migration, just visit http://www.flosum.com/salesforce-data-migrator/.
Chalk Out Proper Plan: When you are using data for migration, it is required that you chalk out a full proof plan. The information, including the possible issues and the cutoff date, should reach the users well in advance. You can also test the migration ideas to some pilot users and then can finally decide a huge data migration.
From Perspective of Developer: Try to look at the process from the perspective of the developer. You should provide enough testing time for data migration before you start displaying the instances to the users. After the performance of the data loader, you must not get relieved that the entire process of migration is complete. The developer console can be used for performing basic queries like the total number of accounts without the contacts, type of the records, number of accounts owned by the users.
Sanity Testing: Sanity testing can be done in various ways through Salesforce. You can login to the Salesforce accounts as different users and can observe the records of various objects.
Active Workflows and Triggers: You must check the triggers and the active workflows before completing the migration process of Salesforce. You can revisit the workflows before running the tool similar to the data loader.
Use Time Zones: When the data loader is inserting units in the date fields, the time zones can be used. The time zone settings must be properly arranged and the user Ids can be used for inserting the records.
You must take care of the order when you are inserting the data through the migration process. For instance, the names or the Ids should be inserted at first and then the contacts. This can clearly display the relationship between the two instances. Ensure that you possess a back up of the entire existing data before you initiate the process of data migration.
Author Bio: Michael Roger is a well known Salesforce consultant. In this article, he talks about the important things required to be considered before the data migration of Salesforce. To learn more, just visit http://www.flosum.com/salesforce-data-migrator/.