Data Migration Strategy

[ Gregory Ezeoke
Selecta 29-04-2016]

City: Kirchberg, Date16-03-2016

 Background

• Following the need for a new ERP solution, after couple of inquiries,
Selecta management selected the following tools for the project.

- Vega: ERP solutions (Vega/Oracle Technologies)

- Microsoft Dynamics AX : ERP Solutions (Microsoft Technology)

- Talend: ETL tool (Java Technology)

 Objectives

• Migrate business master data components as follows:

- From legacy ERP (Movex , IBM I-series, and *other sources)

- To new ERPs (Vega oracle database and Dynamics AX sql server database)
In accordance with related change agents.

• Prepare base data for cross-platform exchange (Vega and Dynamics AX)

* Other sources: Refer to slide no.7 (data extraction arch.) for information
Scope

• Prepare and maintain necessary hardware and software appliances (within Selecta domain)
throughout migration period

• Assist change agents in gathering master data requirements

• Selecta CH only (at the time of this documentation)

• Migrate required data entities, from legacy to target ERP environments (Vega and MS AX)
(data entity list incomplete at this time)

?
Customers / Locations
Machines / POS
Contracts
Pricing / Discounts (direct sales)
Articles
Machine Configuration
Suppliers
Planograms
Layout
Tour Plans
Financial Accounts
Cost Centers
Fixed Assets

• Arrange required connection protocols between interface systems (TCP IP ecc.)

• Master data preparation

• Master data cleansing

• Master data entities aggregation (within Selecta domain)

* Data Entity: Relational database term to define database components or processes

Out of Scope

• New ERP systems data exchange (BizTalk area of concern)

• Data governance decision making (data ownership, data destination, AX or Vega etc. )

• Legacy ERP lifecycle, post-migration

• Other Selecta organizations (will be treated separately)

 Migration Technical Components

Source Systems Target Systems

• Movex DB2 * • Vega (Oracle DB)*

• MYSQL* • Dynamics AX (MS SQL)

*
• MS SQL

• MS EXCEL

• MS ACCESS

• MS SQL

• Talend Data Preparation tool

* Already confirmed components

 DESTINATION1 ORACLE VEGA (hosted)

Final integration fixes

SELECTA (on-premise) (where required)

SOURCES TARGET
SYSTEMS STAGING DB
ERP DB
1st Level
MS SQL Transformation Executables

MYSQL POSSIBLY,
Jobs INCREMENTAL LOAD
Modules AT SOME POINT BIZTALK
EXCEL ETL Tool ecc. (before go-live)
DESTINATION2 MS SQL MS AX (hosted)

ACCESS
STAGING

DB TARGET
DB
Final integration fixes
(where required)

Transformation
- Data filter
- Data cleansing
- Data deduplication
- Test cycles
- Naming conventions
- Data Merge
Migration Architecture
- Normalization/denormalization
Master Data Entity Requirements

• Customer Data

• -----

• -----

•
•
-----

-----

?
No complete list at the moment*
 Pre-Data Mapping Assessment Processes

• Data quality check

• Data volume
• Data history
AS IS - PHASE • Data source

• Data extract specifications (defined by Change

Agents)
TO BE - PHASE

• Documentation
DOCUMENTATION PHASE

www.selecta.com IT Department
Data Migration Process Work Flow
 Responsibilities
Task Responsible Group Notes

General data mapping requirements Change Agents Any changes after first sign-off,
definition(cleaning) must be forwarded back to the
and sign-off. responsible change agent for
acceptance, before
implementation.
Legacy ERP (Movex) data mapping design, Michael Jungo
management and documentation

Other sources (non ERP) data mapping and Michael Jungo

documentation Gregory Ezeoke

Design, planning and managing data migration Gregory Ezeoke

processes

Data profiling, dedupe, cleansing, exception Gregory Ezeoke

reporting Michael Jungo

Hardware/Software Gregory Ezeoke

management

Suppliers relationship Gregory Ezeoke

Communication Gregory Ezeoke

Michael Jungo

Risk
Migration data entity
requirements
Absence of data governance
policies (or structures)
Lack of Collaboration
Source/legacy system data
Inconsistency
Neglecting to review
redefined business rules with
responsible agents, before
migrating
Go live in one big upload at
the end
Dynamics AX delay
Cross-object dependencies
Inability to reuse migration
modules
Risks and Mitigation
Description Importance Mitigation
No exhaustive list till date Medium Treat as we go
This is a problem with our current
ERP. We must change the trend. Document what should goes to Vega (or AX)?
High
Clearly establish governance Who is accountable? Etc.
structure and policies are required
Working together can be difficult at
times and when things go wrong, Strong team mindset required, no department
collaborative approach to solve Low boundaries (any failure is everyone’s)
problems is the best path forward.
Many unknowns Medium Case by case thorough testing required
Make sure data mapping rules from a legacy
Modifying data without related
High system to a new system has been reviewed
change agent involvement
and validated by agents
Low
Was not possible to test before kick
Low We just need to catch up (agility)
off.
Cross object dependencies and
discovering a whole new
Low We are try to anticipate, planning in advance
dependency late in the migration
life cycle poses risk
Scalable and repetitive data
migration framework is a must for
effective technical execution of the
project. This will help in multiple
Already planned for. A prerequisite for the
Low
reruns of the extract/transform/load/
migration
validation processes.
Components Relationship and Responsibilities
 Go-live Strategy

CUTOVER OPTIONS

1. SEQUENTIAL LOAD

• Move data components to target environments consecutively

• Typically need a sufficient time box to successfully move the data to

the target

• Typically involves downtime to the business

2. INCREMENTAL LOAD

• Migrate only missing data, after first full load

• Very limited business downtime (if any)

*We will decide on which option to go for, soon as we are able to quantify involved data volume
 Timeline (not having a complete migration data entity list, this slide will be completed later)

March April May

Activities/Topics

Customer Master Data

Preparation
Migration 03.05
Testing
End 26.05
--------
xxxxxx

-----
xxxxx

--------
xxxxxxxx
00.00
----------
xxxxxxxxxxx

-----------
xxxxxxxxx
00.00

-----------
xxxxx

xxxxxxx

00.00

End
After go-live

Legacy ERP lifecycle

?
Thank You!