The eBook recently published by Strategic Systems Group (SSG) is a FAQ resource. It provides in-depth answers to “12 Frequently Asked Questions about Enterprise Resource Planning Systems” for manufacturers. Chapter 3 is a deep dive into:
Everything You Need to Know about Data Migration from Your Old ERP System to Your New One
You might wonder how we can dedicate 7 pages of our eBook to data migration. Isn’t it a fairly simple matter of exporting data from the old system and importing that data into the new one? The answer is emphatically NO. While the data migration process does involve an export > import process, executing that process correctly is the key to successfully implementing your new ERP (Enterprise Resource Planning) solution.
Just consider how disastrous it would be to go live on a new ERP system only to find out that years of data haven’t moved over properly.
You can download a complimentary copy of our eBook now, or just read on.
Here’s a brief look at just one of the critical issues to consider before, during, and after data migration.
If you were under the impression that all of your data is going to migrate over, you would be wrong. That’s typically not the case.
One tactic that may be appropriate is to load summary data without the corresponding detail. This commonly occurs with GL data, which has a large number of component transactions. What companies sometimes do is carry the summary data at the GL summary level, including the balance for each account by month, and move them over to the new ERP application rather than trying to load in all the underlying detail. This is particularly helpful if the value of the detail data is in question.
Data migration can be classified into 3 segments; the static master data being the simplest of them all. This includes the bills of material, routings, and data that pertain to customers and vendors. The second category includes open data: open sales orders, open purchase orders, open production orders and the like, all of which are easy to migrate.
The third category, the one that poses the greatest challenge during the migration process is historical data such as transaction by transaction sales history and similar information that goes back in time.
Where possible, instead of migrating historical data, clients should consider an archive or a data warehouse solution rather than migrating all historical transactions into the new ERP application.
And that’s just a synopsis of a single issue! To learn more…
Download a complimentary copy of our eBook now.