Site   Web

March 3, 2016

Things Not to Miss When Carrying Out a Salesforce Data Migration Project

There is never a data migration that is too small or too big to be planned out. It is always important to plan out your data migration efforts so you are able to get the best returns from it. When data migration is done incorrectly, there will be problems — huge problems. You do not need anyone to tell you that. It is especially challenging if you are dealing with big data. The volume of this data is going to cause a lot of drama. It is better to spend most of the money on the planning than on correcting mistakes that come with data migration errors.

When starting out the process 

If you would like to start a Salesforce data migration effort, then there are several things to keep in mind. Mapping of the data from one system into the new one should be done in its entirety, beginning with user mapping. It is important to have a clear understanding of how the user IDs that are on the existing system will map onto the new user ids. This information is crucial when it comes to ensuring that the record ownership ends up being set correctly in the new system.

Secondly, you need to consider the security of your migration. This is especially so if you are doing one of those ‘big bang’ data migration projects. It is vital to revisit the Organization Wide Defaults and the existing profiles. These are usually the foundation of the security of all Salesforce Instances and if they are not set up correctly in the new system, security could be compromised.

Thirdly, you should get a good data migration tool such as the one available at http://www.flosum.com/salesforce-data-migrator/. This data migration tool has been praised for its efficiency and user-friendliness. It makes large data migration efforts appear like they are very simple. It is one of the finest migration tools available in the market and especially for Salesforce developers. Moving test data from a Full Sandbox to a Developer Sandbox cannot be easier than when you are using the Flosum data migrator.

It is also necessary to have a number of licenses from the old Salesforce Instance (when you are moving from one Instance to another) for a while after the cut over data. This ensures you will be able to investigate issues with ease. In case there are migration issues, the old instance will be extremely useful in investigating issues.

Finally, plan and plan some more. This is a step that many people tend to skip when they are carrying out the data migration. It does not matter whether you have the best Salesforce data migrator, you will always need to do the planning. This involves getting in touch with Salesforce consultants who will help you to assess the migration process that you have ahead of you. They will be instrumental in determining errors that are likely to occur and assist in preparing a plan to counteract them.


avatar

Florence White is a Salesforce architect with years of experience in the field. When it comes to data migration she is the person to consult with. She recommends tools like http://www.flosum.com/salesforce-data-migrator/ for data migration especially for Salesforce developers.

css.php