What's data got to do with it? RPI's Pre-Planning approach to conversions

The conversion scope and strategy that we decide on during pre-planning has a pretty big impact on the structure of the overall transition project, as does the work effort and direct cost for this implementation. Let's discuss how and what we focus on during this important phase in the pre-planning project, as well as what it means for your overall implementation.

There are three different kinds of data that we can talk about in terms of conversion: master data, transactional data, and historical data. Master data concerns vendors, items, HR organizational structures, and the chartered accounts, all of which obviously needs to be converted in the CloudSuite. We can exclude inactive or obsolete master data, with the exception of any older master data that's still necessary because of the dependent historical data conversion. Ideally, you want to use the CloudSuite implementation as an opportunity to clean up and reorganize this master data, while also keeping in mind that all of it will need to be mapped back to the legacy system. As part of the project, we establish a crosswalk to identify the transformation component.

When it comes to master data, clients usually want to know the projected length of the design phase since financial structure master data in v10 is so different from CloudSuite.

Let’s provide some context around the design during these migrations. This phase is pretty similar to a net-new implementation in that there's some current-state analysis and some super-user training to help educate the power users on the functionality of the systems. After this step, we have a series of design workshops to create a future state design document. Typically, we see these as ten-to-fourteen week periods, although sometimes they can be scaled down more aggressively if there's a very simple footprint. However, if the organization is more complex or if you're bringing in multiple business units and the like, these workshops can be extended. Next week, we will get into how we handle transactional and historical data during a pre-planning engagement.

Learn About Pre-Planning

Back to Blog

Related Articles

The Project Scope & Approach for an RPI Pre-Planning Event

Today we’re going to discuss the project scoping and approach. We begin with some as-is discovery...

The RPI Pre-Planning Assessment Executive Summary

All of the work we do in our pre-planning engagement, everything that we've been discussing so far...

RPI's Pre-Planning Assessment & Beyond

Over the course of the last fourteen weeks, Keith and I have walked you through a high-level...