When you’re making a move, you usually have to take some stuff with you. It’s no different when you decide to move to a new ERP system- you likely need to take your data with you. In the first half of this article we talked about how to decide if you truly to need all that old data, or if you can make a clean break and start fresh in the new system. We discussed factors such as how to decide if your old data is actually as valuable as you think it is, how much it needs to be cleaned up before it can be moved, and situations where manual data entry may be more beneficial than actual data migration.
In most cases data migration will be necessary, but there are a few more important questions to ask yourself as you make your final decisions and prep for the change.
As you work with your ERP consulting or technology partner, be sure to ask them specific questions such as, “What is your migration process?” This is a loaded question and their answer should be very lengthy. The conversation should touch on a number of points including overall migration methodology and processes, preservation of data, data security, speed, etc. Another important question to ask in relation to this conversation is, “What potential problems or issues might we face and how can they be overcome?”
Related Reading: ERP Project Planning: Don’t Make These Two Common Mistakes
Proper planning is a must and your ERP partner will help you answer planning question such as:
When will data be migrated?
Coming up with a time frame and set of milestones is important to ensure everyone remains on the same page. In some cases you may be able to migrate critical data first and then work your way down the list, but in other situations there may be interdependent pieces that will dictate what is moved when.
Where will it go?
Deciding where the data goes in the new system is of course very important to ensure the current data is translated from current fields into the files in the new system. In other words, taking the data “as is” today to how it “will be” in the new system.
How will it get there?
We’ve discussed “when” and “where”, but now it’s time to talk about “how.” What are the tools and technologies involved in moving the data from one system to the next? Is there a conversation utility available or will one need to be built? This can impact the cost of your migration. What does your organization need to do to be ready? What about changes to processes and training? etc.
Related Reading: The 6 Deciding Factors of ERP Implementation Cost
Documenting all of these questions and their detailed answers is crucial to the success of your data migration and overall ERP implementation project. Put one person in charge of keeping all documentation up to date and made available to the entire project team 24/7.
Not having a plan in place is one of the many mistakes companies make during an ERP data migration or ERP implementation that can easily be avoided. Learn more in the white paper below to learn how to avoid making them for a more successful project.