6 More Tips For Avoiding Data Migration Disasters

Data Migration

The complexity of data-migration jobs often results in cost overruns and delays. Whether you’re changing ERP, CRM, or other central applications, transferring data between systems is never a simple task. Not only is there a high likelihood of errors, but each mistake can cause a significant negative impact to the business such as costly downtime, diminished end-user productivity, and the loss of important data.

You can avoid some of the most common data migration disasters by doing the necessary preparation work and fully thinking through the process. Here are six tips to keep your data migration project on track:

1. Clean Up The Data

Things may have started out perfect, but it’s more than likely that data inconsistencies and data duplication were introduced over time with multiple users. So it’s important to sanitise the data before the moving the data over. Make sure you de-duplicate data and fix any data integrity problems before the problems are replicated in your new system.

2. Update Business Rules

Your company’s business and validation rules may have changed since the legacy system was first built. Now is the time to make sure that the businesses rules are current and any questions or disputed processes are ironed out. Also it is advisable to see if there are any data fields that need to be changed or added, and that the necessary validations are included in the new database.

3. Check Cross-Object Dependencies

Cross-object dependencies often are not discovered until very late in the migration process. A complex project can have dozens of different data fields coming in from different applications. Discovering new sources of data or connectivity late in the process can throw off your migration timeline. It’s better to identify external sources of data upfront and make sure that the necessary connections are in place for the new system.

4. Automate Where You Can

Many projects suffer from costs overruns due to human error and system downtime. While traditional ETL tools may seem appealing at the outset, they won’t allow you to maximise uptime and maintain interconnected business processes, such as the automatic update of customer address data in your ERP based on changes recorded in your CRM. Instead, look for an integration platform that supports process-based integration. In addition, an integration platform that has prebuilt connectors to the systems you are migrating can save a lot of time and help you avoid errors. It can also let you keep both new and old systems live and updated, without risk of downtime or transaction loss, until you are ready to do the full switch. System integration platforms can provide an effective solution that will not only accelerate your data migration project, but can be useful for other system integration projects in the future, providing a high return on investment.

5. Get Started Early

There is so much work to do on the data quality and business rules, so there is no reason to wait for the target to be ready or even chosen. You may have a lot of data to clean up front; it may be too late to hit the deadline if you wait too long.

6. Test Early & Often

Don’t save this step for the end. You really need to make sure that you’re validating and testing throughout the process. Having business users validate that the data is complete and accurate is important. The people who sign off on the data should be the ultimate consumers of the data.

Having a project plan that includes enough time to analyse the risk and complexities is the best way to prevent data migration disasters. When taking the right precautions, data migrations present an opportunity to improve data integrity. Taking the time upfront to analyse current data and processes is well worth it.

Stephan Romeder

Stephan Romeder is General Manager of Magic Software Europe.