The data migration plan
The planning period is your chance to determine the roadmap for your migration and to choose the course that will be most effective in terms of your desired outcome, timeline, and budget. As with most planning, it is important to have the end in mind. A data migration is not as simple as just moving information from point A to point B. You need to define what success will look like in the target system. What is necessary to ensure the new system operates optimally? What degree of data quality do you expect in the new system? How can you be certain that you achieve the required level of data quality? How much data needs to migrate to the new system? What data can you filter out from the old system? Asking these questions can help you determine a more detailed scope for the migration. The more questions and variables you consider at the outset, the better.
After you’ve defined what the end should look like, it’s important to know where you are now. Defining your current state of data quality can help you get a sense of what a realistic goal is for the target system. If your current state of data quality is poor and you hope to have a high degree of data quality in the new system, you can build in the time and budget to improve your data quality as part of the migration. You also will want to analyze your data sources and compare what the source data looks like—in terms of organization, formatting, grouping, etc.—to how the data will look in the target system. If, for example, you currently have customer information on one platform and business performance information on another, and you plan to host both types of data in a new system, the way the data is organized and grouped may look different.
Another very important thing to keep in mind is that with a data migration, less really is more.
Another very important thing to keep in mind is that with a data migration, less really is more. The less data you transfer from the existing system, the less it will cost, the shorter time it will take to complete, and the less complicated the process will be for the teams involved in the migration—so it’s important to keep this in mind from the get-go. Ask yourself, “can we archive some of this information instead of migrating it?” and even more importantly, “can we consolidate some of these records?” This can help you to reduce the overall record count and achieve a single source of truth.
Sources
1. “Risks and Challenges in Data Migrations and Conversions.” Gartner. 25 Feb 2009.. 16 March 2017. Web.
2. Mistry, Dhrien. “Big Bang vs Phased – the ideal migration approach.” Xceed. 21 Nov 2014. 17 March 2017. Web. < http://www.xceedgroup.com/xceed-blog/big-bang-vs- phased-the-ideal-migration-approach>