How to Prepare Legacy Data for a Conversion

Last week, we covered how to handle different kinds of data ahead of a conversion. Data conversions for CloudSuite are an extremely complex process and it's important to know what you can do to improve this process. One of the main reasons they are so complicated is because data is structured differently in the cloud than it is in legacy systems. CloudSuite has a lot of data integrity rules in place to ensure that business objects are complete, accurate, and can relate to the master data and other necessary transactions. At the time the data was brought into the legacy system, these restrictions were not in place, meaning the quality might not be as valuable once it is moved onto the cloud.

To avoid moving unnecessary data over during a conversion, let's discuss what you can do before a project starts. Our first recommendation is to start by cleaning up the master data in your system. We've talked to a lot of clients whose objective is to move onto CloudSuite with a clean, pristine house. They’ve had data structures kicking around in Lawson for years now and cleaning up that data has always been on the back burner. Migrating to the cloud is the perfect opportunity restructure the data and clean everything up during that transformation process.

Although this may sound like a brilliant plan, in reality it is a lot of work. If you didn't have the time to do the data clean up over the past few years when you weren't going through a major implementation, how are you going to fit it into this packed project schedule? The best time to start taking care of that legacy data is before the project takes off, that way you can ease the transition when you need to convert it. A lot of organizations know what the current state of their data is - they've just been putting it off because it is a huge cost and effort.

It's not realistic to bring all the transactional data you've accumulated over the years onto a new system, especially when all that data needs to be remapped and transformed for new master data structures, new chart of accounts, etc. We have found that the less transactional data we can bring forward, the smoother the conversion process goes. It makes it a lot easier for the project team to test, validate data, and build out legacy structures to handle prerequisites.

Next week, we'll continue our conversation about CloudSuite by discussing how updates impact end users.

Learn More about RPI Consultants

Back to Blog

Related Articles

The Road to the Infor Cloud

Is your organization looking down the road at a CloudSuite project? At noon on Wednesday December...

Change Management: Getting Ahead in your CloudSuite Journey

When your organization is preparing to embark on a CloudSuite migration, change management should...

Capturing Documents Going Forward

Over the past several weeks, we have covered how to handle the historical data process using the ...