The purpose is to support two distinct data management activities for an SAP implementation: legacy data migration and data archiving.

The purpose is to define the processes for fully simulated data loads to production and production loads.

The purpose is to establish the data archiving strategy, procedures and test plans as defined in the business blueprint and the IT data archiving standards, to keep the volume of system data under long term control.

The purpose is to perform one of the cutover tasks, namely the loading of production data from legacy system into the production environment.

The purpose is to develop, implement and test the data migration programs and processes defined in the Business Blueprint phase.

The Data Quality Assessment Report produced during the Blueprint and updated during the Realisation phase.

The Automated Data Migration Design specifications created during the Blueprint phase.

The Data Migration Test Results generated or captured during the Realisation phase.

The Data Audit Findings Report produced during the Project Preparation phase.

The Data Security Design created during the Blueprint phase.

The Data Management team only includes consulting resources; the consulting team does not depend on or require customer involvement.

The legacy data and business rules are not important, since the SAP application will establish new business processes.

The data migration effort requires customer resources knowledgeable on the legacy systems along with SAP technical and functional implementation experts.

The data migration tasks should be executed as a separate project since there are no dependencies between the data migration activities and the main SAP implementation project.

The data migration effort is a pure technical activity, so no assistance is required from functional or business experts.

The purpose of the workshop is to educate the customer on SAP's approach on data migrations and to understand the customer's legacy data systems, business priorities and technical infrastructure.

Perform hands-on training sessions with the customer on tools that can support the migration effort.

Since SAP does not offer tools to support automated data migration, third party software solutions are demonstrated as part of the workshop.

The expected outcome of the workshop includes a clear picture of entire migration process, an understanding of the potential problem areas and their effect on the success of the migration and a realistic migration plan that meets business needs and manages the potential risks.

A Findings report that includes the results of the legacy data analysis and includes quality measures for criteria such as completeness, accuracy, consistency and uniqueness.

The customer's statutory and legal requirements.

The record count, there is a fixed limit on the number of records that can be stored in an SAP application table.

The customer's business process requirements.

The age of the record, any record older than three years is no longer required to be stored in the SAP application.

The customer's requirements for a clean desk policy.

Completeness of data migration requirements.

Selection of migration tools.

Definition of the organisational structure and communication processes.

Data migration activity schedule.