Data Migration to Salesforce

Data migration is a key element to consider when adopting any new system, either through purchase or new development. One would think that any two systems that maintain the same sort of data must have performed similar tasks. Therefore, information from one system should map to the other with ease. However, this is rarely the case.

Although migrating data can be a fairly time-consuming process, the benefits can be worth the cost for those that “live and die” by trends in data. Additionally, old applications need not be maintained

What is data migration?

Some key terms in understanding data migration are:

Legacy data is the recorded information that exists in your current storage system, and can include database records, spreadsheets, text files, scanned images and paper documents. All these data formats can be migrated to a new system.

Data migration is the process of importing legacy data to a new system. This can involve entering the data manually, moving disk files from one folder (or computer) to another, database insert queries, developing custom software, or other methods. The specific method used for any particular system depends entirely on the systems involved and the nature and state of the data being migrated.

Data cleansing is the process of preparing legacy data for migration to a new system. Because the architecture and storage method of new or updated systems are usually quite different, legacy data often does not meet the criteria set by the new system, and must be modified prior to migration. For example, the legacy system may have allowed data to be entered in a way that is incompatible with the new system. Architecture differences, design flaws in the legacy system, or other factors can also render the data unfit for migration in its present state. The data cleansing process manipulates, or cleans, the legacy data so it conforms to the new system’s requirements.

How do we migrate data to Salesforce?

  1. Analyse the data
  2. Best solution
  3. Migration Design
  4. Execution
  5. Testing
  6. Go live