The eBook recently published by Strategic Systems Group (SSG) is an FAQ resource. It provides in-depth answers to “12 Frequently Asked Questions about Enterprise Resource Planning Systems” for manufacturers. In Chapter 7, we dive into how to handle the data in your old system when migrating to a new ERP solution. Decisions, Decisions!

Deep Dive into ERP Data Migration and Management: Out with the Old, In with the New?  

Not so fast! When migrating to a new ERP system, as a general rule, you do not want to migrate all of your data. And of course, you do not want to scrap all of your old data. So how do you decide how much to migrate over and how to manage the rest?

Here are a few pointers to help with that decision-making process.

You can download a complimentary copy of our eBook now, or just read on.

Budget considerations always come into play. But more importantly, what you want to think about are these two questions: 

  1. What do you expect to use this data for in the future?
  2. For how long will this data need to be available?

For example, if the data is only required for reporting purposes, a data warehouse might be best. If there are regulatory requirements (FDA, HIPAA, etc.), a working read-only version of the old system might be the most sensible solution.

Data is not like wine. It doesn’t get better with age. Over time, say a year or two later, the data from your old ERP system is probably not going to have a whole lot of value. That’s one reason why it could make sense to store certain types of data in a data warehouse, as opposed to porting it all over to your new ERP platform.

Data Warehousing

A data warehouse is simply a database that stores information from the old system in a user-friendly format. This serves two purposes: 1) storage of historical information and 2) a valuable reporting tool.

Timeframes and Regulatory Requirements

The timeframe for maintaining accessibility to data varies by industry and regulatory requirements. Much like the IRS requirements for saving your tax return documents, different agencies impose varying timeframes on ERP data availability. While much of your data will be beyond its usefulness in a year or two, there are industry-specific and regulatory exceptions:

  • The FDA requires pharmaceutical companies or food and beverage manufacturers to maintain their data for 10 years. This applies to record keeping on manufactured parts, keeping track of all manufactured components used down to the raw materials level, with traceability for all of those items.
  • HIPAA also has one of the longest retention requirements, up to seven years.

To learn more about your data migration, maintenance, and retention options …

You can download a complimentary copy of our eBook now, or just read on.

Or contact Strategic Systems Group, your one-stop shop for manufacturing ERP. Call 310.539.4645 or email us at info@ssgnet.com.

Related Posts

As we move into the second half of our eBook, you may want to look back at what we’ve covered in the first 6 chapters.
1: New eBook Answers 12 Frequently Asked Questions about Enterprise Resource Planning (ERP) Systems for Manufacturers
2: How Much Does It Cost to Implement a New Manufacturing ERP System? And How Long Does It Take?
3: Everything You Need to Know about Data Migration from Your Old ERP System to Your New One
4: Successful ERP Implementations Include these Top 9 Activities and Milestones
5: Successful ERP Implementations Avoid these 8 Common Pitfalls 
6: ERP Implementations: The PROs and CONs of Doing It Yourself (DIY)