Data Migration Plan

<<Customer Name>>
 Data Migration Plan

The contents of this document are for informational purposes

only and are subject to change without notice. Epicor Software
Corporation makes no guarantee, representations or warranties
with regard to the enclosed information and specifically
disclaims, to the full extent of the law, any applicable implied
warranties, such as fitness for a particular purpose,
merchantability, satisfactory quality or reasonable skill and care.
This document and its contents, including the viewpoints, dates
and functional content expressed herein are believed to be
accurate as of its date of publication. The usage of any Epicor
software shall be pursuant to the applicable end user license
agreement and the performance of any consulting services by
Epicor personnel shall be pursuant to applicable standard
services terms and conditions. Usage of the solutions(s)
described in this document with other Epicor software or third
party products may require the purchase of licenses for such
other products. Epicor, the Epicor logo, and any other applicable
Epicor tradename(s) are trademarks of Epicor Software
Corporation, registered in the United States and other countries.
All other marks are owned by their respective owners. Copyright
© 2012 Epicor Software Corporation. All rights reserved.

Prepared by Epicor Professional Services Page 1 of 5

 Data Migration Plan

Data Migration Plan

1.0 Introduction
This plan details how data migration will be managed for XXX Project and includes the migration
of static data and final balances, when key milestones should take place and who is responsible.
Epicor are here to provide assistance only during the data migration process.

2.0 Roles and Responsibilities

DMT Role Description Assigned to:
Project Responsible for scheduling data conversion steps X
Manager Assigns responsibilities
Monitor progress against the plan

Data Works with data owners and consultants to determine the source of X
required data and the method for extraction of data
Extractor
Maps the source data to the required format whilst considering elements
such as field lengths, translations, reporting and data types

Data Import data into destination system X

Importer Documents run times, number of instances of import tool used, errors
encountered, corrective actions required
A role often combined with that of data extractor

Data Owners A subject matter expert (SME) or has access to SMEs for the area of X
responsibility
Works with data extractor to define rules for extracting data
Responsible for data cleaning, and data validation

Consultants To assist in the field level detail when defining the data to be imported X
To offer advice on validation such as transactions to use, reports for
balances

Prepared by Epicor Professional Services Page 2 of 5

 Data Migration Plan

3.0 Data Conversion Tools:

3.1 DMT Plan
DMT plan document assigns roles and sets milestones which should be followed during this
implementation Project.

3.2 Control Document

The Control Document lists all files for all companies, data owner. This is a dynamic document which will
continuously be updated during the project.

3.3 Data Extraction Rules

<<Add any data extraction rules i.e who has permissions to access data, cleanse data etc…>>

3.4 Data Conversion Feedback

The feedback document is a dynamic document which will contain feedback from all imports. <<Add
details of who should update this document and when>>
3.5 Data Extract/Import tool
The following methods will be used to extract and import data:
 DMT tool (Data Migration Tool)
 Excel
<<Add additional tools and explain how and when they will be used>>

4.0 Data Migration Milestones:

Stage Description Signature Completion
Stage date:
DMT Training on the planning of data migration and use of DMT Plan
Training tool.

Design Define what will be extracted, imported, number of Plan

iterations, data owners, validation rules, and relevant
methods

Extract and Define and document rules for extraction field mapping, Plan
Transform transformations, defaults, extraction time, sequence for
each entity and conversion. Produce export validation
reports and update data migration control document.

1st Import Define, follow and emend the import sequence as Design
appropriate, whilst documenting import times, document
and correct errors.

Prepared by Epicor Professional Services Page 3 of 5

 Data Migration Plan

Test Validate reports and import reports balance, validate that Design
data in the new system forms displays correctly, if all data
is correct then sign off the data.

Feedback Review feedback from testing and update for next iteration. Design
Update schedule based on more accurate timings.

2nd Import Define, follow and emend the import sequence as Validate
appropriate, whilst documenting import times, document
and correct errors.

Test Validate reports and import reports balance, validate that Validate
data in the new system forms displays correctly, if all data
is correct then sign off the data.

Feedback Review feedback from testing and update for next iteration. Validate
Update schedule based on more accurate timings.

Go live Review times taken for import and input this into planning Deploy
planning for go live. Review if further iterations are required.
review
Final Using feedback from other imports complete final data Deploy
import import ready for go live.

5.0 Import sessions

5.1 Import 1
<<Example - Import 1 will be performed before the proof of concept and will include an import
of a sample of static data. >>
5.2 Import 2
<<Example Import 2 will be performed before the UAT and will include an import of all static
data and an import of sample balances as a trial before go live. >>
5.3 Import 3
<<Example The final import will be performed prior to go live as part of the go live process. At
this point static data will be imported if the first import was not successful and all final balances
will be imported. >>

Prepared by Epicor Professional Services Page 4 of 5