Warning: count(): Parameter must be an array or an object that implements Countable in /home/futurec5/public_html/wp-content/plugins/shinetheme-core/libs/metabox1.2/init.php on line 610
Migration to Salesforce – Future Covenant

Migration to Salesforce

You want to move to the World’s #1 CRM, but you have a years-old business already with lots of legacy data recorded over the years and workflows your staff is accustomed to. How can you move to Salesforce as friction-free as possible without losing all those precious accomplishments?

Correct data migration is crucial especially when migrating millions of records – you will never know if anything was lost or missed during the procedure until late after the project is complete and after puzzling the entire staff over numbers that don’t add up.

This is where Future Covenant can help you.

Having transformed several companies into Salesforce, we can tell you from experience what needs to be done.

Plan Ahead

What do you want to transfer, and what can be left out? Discarding unimportant trash data can have a significant part in easing the migration procedure

Creating a Process for Import

Migration can be an exhaustive task. Often you are faced with importing loads of data and discovering that parts of it failed, which would force you to reimport it after resolving the issue.

As such, it is crucial to build an automated process that can repeat the import (and preferably data-formatting) with the click of a button. It pays off to create a sandbox and try the migration there where you can easily remove the data and retry the import before working on the actual instance.

Format Your Data

Not everything can be migrated to Salesforce as it is. Date fields and picklist values need special attention. Date values must match the format of the target columns, while picklists should match the values on the list. You might even need to apply rules for transforming the values into their SF equivalents

Audit Fields

Created by, Modified by, Created data and Modified date – these fields can be tricky to address especially as they are not available for editing in all Salesforce objects

Import Order

Especially on dependent objects with relationships, you must adhere to a specific order or the data will be in chaos. At times we have even faced cases where we needed to import a table twice; once for adding and later on for updating. The most important factor is to know what to import and when

Process Builder, Workflows and Validation Rules

These can turn into obstacles if not handled correctly, not to mention that your entire staff could get annoyed by the tons of emails the system sends for some active workflow. Be sure to turn them off but don’t forget to restore them once you are done!

Data Mapping

Probably one of the most important aspects of data migration is to retain the correct mappings. Who was the Sales rep for this customer? What purchases has she made? What products were in that order? Owners, contacts, users… all should be mapped properly to their Salesforce counterparts.

It makes sense in some cases to store the foreign key of the legacy data in a custom field in the corresponding Salesforce object, so that it can be used for proper mapping after the equivalent records are created

Sounds Daunting? Fear Not!

Let Future Covenant take care of your data migration. Leave the task to us and enjoy a smooth transition to Salesforce