Data migration is a key element of every ERP implementation. As such, Curogens embeds this key requirement in the overall project methodology for D365 F&O implementation projects.
We gathered valuable experience in the successful realization of ERP implementation and related data migration projects in the past and can offer you a very robust and at the same time flexible approach to make your ERP implementation or upgrade project a full success!
Our designed tool for the management of the Data Migration Project is DevOps, which includes for each Data entity. 3 dimensions of information:
If the data migration process includes more than 1 legal entity to include in a joint GoLive, the above mentioned structure is replicated for each in a unique migration project.
If the Golives are scaled, separate projects plan with their own iterations (sprints) can be made available.
During the Design phase of our ERP implementation projects we perform an in-depth analysis of each single business process in our customer’s organization. Besides categorizing the processes and identifying their dependencies in the global process landscape, we also put our efforts in working out the interested data entities for data migration purpose.
The accuracy in this phase of IDENTIFYING all relevant Data Entities for Data migration is CRUCIAL for the success of the entire implementation project.
The deployment phase marks the final phase of the implementation project and requires a sophisticated orchestration of the single activities. All team members must be prepared for all potential issues as there are a lot of variables and the nerves of the employees may be on the edge! CuroGens is experienced in guiding you through this delicate phase, also with regard to the data migration!
CuroGens prepares a detailed and bullet-proof Data migration task list, both on the extraction and on the loading side, measuring the times required to deliver and to import the single data entities, and fixing a precise and not changeable LOADING ORDER for each single piece of data.
This final Cut-over from the old to the new system must be anticipated (e.g. with a mock-up Go-live) and nothing should be left to chance. The quality of the planning and testing activities throughout the project phases, the better the outcome for the Go-live. Request a free consultation.
While some organizations aim to deploy all the modules of D365 and all the legal entities concurrently, others opt for a multi-phased roll-out, focusing first on a pilot with the high priority processes and add other processes/modules or other legal entities in later stages.
It is recommended to support such scenarios with a dedicated “Configuration plan” to make sure each phase starts with the optimum set of data to support the business processes.
For the first Go Live the simple restore of the Golden Configuration environment is a good option, but in a multi-phased roll-out this option is not available anymore.
For successive Go lives (other legal entities, business units, or environments) there must be an accurate plan for the required variations of the configurations for each phase.
Configuration plans are a structured plan of all the configuration and master data changes required by each phase of the multi-phase rollout, and it reflects also the dependencies between the single data entities (e.g. Sales Orders need Customers first, Projects need accounts first etc.).
The plan differentiates the Setups that must be imported only once as they are shared across the organization. On the other side, there are setups per legal entity that must be imported for each phase. Another strategy that the configuration plan can establish is the data-sharing feature to copy configurations from one legal entity to the other.
The configuration plan is a configuration cookbook, it defines the scope, the dependencies, the tools and data redundancy, and it can help to track the progress of enabling the full scope of the solution in terms of configurations and master data.