A structured and comprehensive data conversion process to ensure a smooth transition from your old legacy system to the new ERP system.

1. Private & Confidential
ENTERPRISE APPLICATIONS
Bring Simplification and Agility to
Business Applications
MS Dynamics AX 2012 R3
Legacy Data Migration
A robust data migration process is central and
critical to every successful ERP implementation

2. Private & Confidential
Data Migration Objectives & Approach
• Plan the Data Migration Strategy
• Assess the data (Heterogeneous Data)
• Check Quality of Data
• Develop Extract and Transformation Rules
• Develop the Load Mechanism
• Export the data
• Read the data
• Cleanse the data
• Convert the data
• Load the data
• Verify the data
• Prepare Final Data Quality Assessment Report
Getting your conversions right is one of the
most important parts of any implementation.
A structured and comprehensive conversion process will ensure a smooth transition from your
old system to the new ERP system.
• Data Migration Scope Assessment
• Data Migration Planning
• Data Mapping considerations (complexity in
mapping, Quality of data and transformation
from base source to AX)
• Analyze the Data Conversion Scenario
• Identify & Quantify the data is to be converted
and moved to new ERP System
• Decide on the Migration Strategy – Big Bang or in
stagerred phases
• Decide on the Level of Data Cleansing needed
• Identify & Mitigate major complications & risks in
the conversion process

3. Private & Confidential
EXAMPLE of Data Migration Scope
Existing data related to all Masters, Open & Ongoing Projects, Open Transactions & Opening
Balances will be migrated from current legacy system, Excel worksheets & MS Project to AX
2012 R3 database
Masters Open Balances & Open
Transactions
GL Master Vendor Open Balance
Bank Master Open PO
Fixed Assets Master Bank Balance
Vendor Group Open Projects
Vendor Master Funder Balance
Funder Master Open GL Balance
Item Master
AX Modules in Scope
• Finance & Accounts
• Procurement & Sourcing
• Inventory Management
• Project & Resource
Management

4. Private & Confidential
DATA
MIGRATION
APPROACH

5. Private & Confidential
Data Migration Approach

6. Private & Confidential
Data Migration Process
Data
Migration
Scope
Assessment
Data
Migration
Planning
Data
Mapping
considerat
ions
Data
Extract
and / or
Data
Gathering
Data
Transform
ation
Data
Load
Legacy
Dynamics
AX
XLS
Mapping &
Conversion Rules
Develop Data Extract &
Load Programs
Rules
adaptation
Extract & Load – Testing
& Data Validation
Acceptance System full load
Pre Production System full load
Pre Production System Signoff
Production Load & Signoff
Data Purging & Cleansing

7. Private & Confidential
Acceptance System full load
Pre Production System full load
Pre Production System Signoff
Production Load & Signoff
Mapping & Conversion Rules
Develop Extract and Load Programs
Data and Rules adaptation
Data Purging
& Cleansing
Extract & Load – Full Size Testing and Data
Validation
Load Unit
Testing
Steps of Data Migration

8. Private & Confidential
Data Migration Plan
Existing data related to all Masters, Open & Ongoing Projects, Open Transactions & Opening Balances will be migrated
from current legacy system, Excel worksheets & MS Project to AX 2012 R3 database. No historical data will be migrated.
Synoverge team will prepare a data migration plan after detail discussion with client’s Core team.
Synoverge team will prepare and provide all the data collection/migration templates based on the requirements
discussion.
Synoverge team will develop all the data upload programs.
It is responsibility of client’s core team to provide clean validated data in the prescribed format with in expected time
lines. Synoverge team will upload the data provided by client in test environments.
Client business users will validate the quality of data uploaded in test environments and identify any kind of required
modification in data. Synoverge will carry out the required modification in case the changes are related to data
template or upload program. In case, it is related to data value client business will perform necessary changes.
Synoverge team will upload the approved data in production instance after data validation in quality environment is
carried out by client. Client’s core team has to revalidate the data in production before go-live.

9. Private & Confidential
No Key Activity Detail Synoverge Client
1 Legacy Data Preparation Legacy Data Analysis R
2 Legacy Data Preparation Data Cleansing and Standardization R
3 Legacy Data Preparation Data Transformation to AX templates S R
5 Data Upload Program Tool
Development and testing of data upload tool to load master
and transaction data into AX.
R -
6 Data Loading for UAT Data Loading into AX before UAT R -
7 Mock Data Load Mock Data Load with Actual Production Data R -
8 Reconcile Data in AX Reconcile and Validate the Data in AX after Loading S R
Responsibility Matrix for Data Conversion
· R = Responsible (Doer)
· S = Support

10. Private & Confidential
Data Conversion Plan
Business Objects
A Business object is a general category for data that defines a business function like
Examples: material master, vendor master, stocks, orders, purchase requisitions or organizational units.
First step is identifying which business objects are required in your AX implementation.
Data type
Three types of data involved in a AX system: master data, transactional data, and historical data.
Master Data : Application master data tends to be more static once defined. Most master data can be driven
by the legacy applications. Examples include GL masters. vendors, customers, Charts of Accounts and so on.
Transactional Data : Transactional data is current and outstanding transaction data that needs to be
converted from the legacy system and defined to the AX applications for business process completion.
Examples include open purchase orders, open sales orders, back orders, accounting data and so on.

11. Private & Confidential
What goes into Data Conversion Plan
What Which business objects will be converted from the legacy system into AX
Where Where are the data, which Legacy System's are involved for the extraction
How much Estimate the number of records to be ultimately loaded into AX
How There are two aspects to be considered :
 The way data is extracted from the Legacy System
▫ Automatically extracted from the Legacy system without manual intervention.
▫ Manually filled spreadsheet
▫ Combination of an automatic Legacy System extraction + Manual Entry into a spreadsheet
 The way data is injected into AX :
▫ Automatic data transfer from a flat file into AX
▫ Manually entering data with online transactions into AX
▫ Combination of both
Who Who is involved on each Business Object
 Key user, Consultant, Legacy Team

12. Private & Confidential
WBS Estimates
Suggested WBS content for data conversion
Volumes
➢ Quantity of records
➢ Quantity of fields
➢ % Manual fields
Business Objects Mapping & Conversion
➢ Data Purging and Cleansing
➢ Mapping and conversion rules
➢ Extract and Load Programs from rules
➢ Data and Rules Adaptation (adjusting rules and programs following testing)
➢ Load Unit Testing (unitary testing - small volume of manual data)
➢ Extract and Load Full size testing (data test and validation - large volume with real extracted data)
Acceptance load and validation
➢ Full data loading into ACCEPTANCE SYSTEM
➢ Full data loading into PRE PRODUCTION SYSTEM
➢ Validation of converted data and Key User + Business Objects Owner Signoff
➢ Full conversion into PRODUCTION SYSTEM and final Signoff
Total
Total - at best (total in Person/Days of each business object)
Total - most probable (total at best + 20 to 25% buffer) higher for the first time projects

13. Private & Confidential
Data Purging and Cleaning
• Data Purging
Before transferring data from your legacy system, delete all the old and obsolete data.
Example : you may delete all one-time customers or those for which there where no
transaction in the last three years, also delete unused materials.
• Data Cleansing
This process corrects data inconsistencies and ensures the integrity of the existing data during
the migration process.
Example: there are often lots of inconsistencies in Customer and Vendor address fields. You
will quickly find that AX will not let you load any address fields unless you get them clean.
In case these records have different data in two different systems than its all the more
important to clean and unify before conversion.

14. Private & Confidential
Top Issues in Data Migration
• Missing Data – Information that was thought to be comprehensive may now be
incomplete. It can be surprising how “mandatory” fields in the source systems can have
blanks, NULLs, or defaults.
• Mismatched Data – field overuse. Sometimes, different nature of data are found in one field
after its original use became obsolete.
• Data Requirements are not communicated – Business Rules, Data Quality & Transformation
Rules are not adequately documented, while consolidating multiple systems to one target
system.
• Lack of Legacy System knowledge and understanding – support staff unable to provide
system guidance
• Poor Quality Data – Data that was of good quality in the old environment may not meet the
requirements of the new. New and Unknown deficiencies are uncovered after extraction.

15. Private & Confidential
Thank You
Jayanta Sarkar
Director & Head – Enterprise Applications
Synoverge Technologies Pvt. Ltd.
jayanta@synoverge.com
+91 – 98250 24808 Office Locations
Japan
No.6, Kita Suna REISE
HOBBY, 1-18-2 Kita
Suna, Koto-Ku, Tokyo,
Japan 〒136-0073
Ahmedabad
The Summit,
3 Sunrise Park,
Bodakdev,
Ahmedabad - 380054.