The Data Migration process

Chris Horroll
Chris Horroll
  • Updated

wcbfti All users who are moving to Alto from any crm other than Jupix.png

When onboarding with Alto, as standard, your Data Migration will follow the process laid out in the Data Migration stages section below.

However, if you require a complex or bespoke migration, your Onboarding Coordinator may organise the Test Migration Review journey instead.

What Data is imported

For a guide as to what is imported (if available in your existing CRM) during the migration process to Alto from all systems, please see this document.

Data Migration stages

We understand the importance of your data accuracy and will work with you to make the transition over to Alto as smooth as possible. Whilst this requires a lot of time and resource on our end, it also requires engagement from you: in order to make sure we have got everything correct, we will need your expertise and input, as you know your data best.

Initial Data Grab & Test Migration

To map your data into Alto, we will carry out a test migration to check the accuracy of the data mapping before loading into a live database.

On the agreed date, we'll take a copy of your data from your existing CRM to undertake the test migration. Depending upon your current system, we can either log in to grab the data, or you may need to request it from your CRM provider. Your Onboarding Coordinator will provide this information to you.

 Note

If you're migrating from a software that we don’t regularly migrate from, we ask that on the morning of your data grab, you complete the Pre Test Migration Checklist in your assigned Google Drive

Your Onboarding Coordinator will advise if this is required.

If it is required, more information on Completing the Pre Test Migration Checklist can be found here.

Data Testing and Reviewing your Data Validation Reports

Your Onboarding Coordinator will advise when the test migration is complete.

We recommend carrying out the data testing as soon as possible, as the data will be up-to-date and therefore easier to compare with your source CRM system.

Reviewing your Data Validation Reports

  1. Log into your source CRM system and Google Drive. Familiarise yourself with the reports and the Migration Queries Document
  2. Your reports consist of a series of .pdf reports (1 page per record). The reports detail the core information for a number of active records (chosen at random and limited to 5 records per status). Go through each report, checking all the information and comparing it to your source CRM system. Bear in mind any changes made since we grabbed the data
  3. Should you find any discrepancies or errors, raise them on the Migration Queries Document. It’s important to add a screenshot from your source CRM system so that we can compare this with Alto. Queries are resolved at the source, so if you find the same error multiple times, it can be raised under 1 query with a couple of examples added. We can then review any required changes to the data mapping.
    (This is a live document so any changes are saved automatically providing you are connected to the internet)

 Note

If we are migrating data into an existing branch in Alto, after you've completed your data testing we'll migrate your existing Alto data and your data from your source CRM system into a trial Alto database for final testing. Within the database, you can check how your 2 data sets look together - general set up, branches, that data is in the correct branches and that records are merged and/or duplicated as expected. Any discrepancies can be raised via the Migrations Queries Document

Resolving your Data Queries

 Note

If no data queries are raised, this step can be skipped

The Migrations team will look into and respond to any data queries raised on the Migration Queries Document. Your Onboarding Coordinator will advise when to refer back to your Migration Queries Document to see these responses.

If required, please answer the query with any questions below the Migration Analysts response. It’s best to use a different coloured text to differentiate the two. Alternatively, if you are happy with the response, tick the sign off for each query.

Data Sign Off

Before we carry out your live migration, we will require your sign off. This lets us know that you have adequately reviewed the Data Validation Reports and have raised all required queries, and that these queries have been resolved to your satisfaction.

If you don't find any discrepancies in the data, you can sign off.

If you do find discrepancies, please wait until these are resolved to sign off the data.

Complete this form to sign off the migration.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request