Do's & Don'ts Data Migration to Oracle SaaS Cloud applications _ OATUG

1
Do's Don'ts Data Migration to Oracle SaaS
Cloud applications

• Prepared By

• Vijay Kannan, Managing Principal,
• Venkatesh Ravi, Solution Consultant,
• NexInfo Solutions Inc.

2
Host Vijay Kannan, Managing Principal Consulting
experience in CPG, Pharma, IT, Manufacturing,
Planning and Logistics. Expertise in Solution
Design, Process automations, Project Management,
Customer relationship and team management.
Co-Host Venkatesh Ravi, Solution
Consultant Consulting experience in
Manufacturing, Health Care and Life Sciences
Industry with expertise in design, development,
implementation and integration of Oracle ERP
Cloud, Oracle CX Cloud (Right Now), OCWMS
(Logfire), 3PL systems.
3
Who Is NexInfo?
SUMMARY NexInfo Solutions Inc. (NexInfo) is a
leading consulting company, a premier Oracle
partner, founded in 1999 with 20 years of
extensive experience in helping clients,
utilizing our consulting expertise to small,
medium and large enterprises. Whether you are a
fortune 1000 company or a small business or a
start up, NexInfo can help you achieve
Operational Excellence using a blend of Business
Process and Software Consulting Services. Deep
domain expertise, including Enterprise Resource
Planning (ERP), Product Lifecycle Management
(PLM), Integrated Business Planning (IBP/SOP),
Customer Relationship Management (CRM),
Enterprise Performance Management (EPM), Human
Capital Management (HCM), Oracles Cloud Based
Industry Solution for Higher Education (Student
Cloud), Predictive Data Analytics, Security,
Business Transformations. We use our proven
NexGen Methodology for traditional models and
NCAM (NexInfo Cloud Adoption Model) for fast
track Cloud migration projects. Both
methodologies bring a Best Practices based
approach to help you achieve operational goals
and accelerate operational excellence. Recognized
in the industry, including features in Gartner
Reports, The Silicon Review (50 Smartest
Companies of the Year 2016 and 10 Fastest Growing
Oracle Solution Providers 2017), and CIO Review
(100 Most Promising Oracle Solution Providers
2015 and 10 Most Promising ERP Consulting/Services
Companies 2019) PARTNERS CORPORATE INFO HQ
in Orange County, CA with offices in Redmond, WA,
Chicago, IL, Bridgewater, NJ, Dublin, Ireland,
Chennai Bangalore, India Operations across the
United States, Europe (Ireland, UK, Switzerland,
Belgium) India
4
Agenda
5
Importance of Data Migration
6
What is Data Migration Why it is important?

• DONT ASSUME Data migration is technical activity
• Business changes
• Data growth

7
How to migrate data into Oracle SaaS Cloud
applications
8
How to migrate data into Oracle SaaS Cloud
applications
File-Based Import (FBDI)
ADF Desktop Integration (ADFdi)
Import and export management framework
Web Services SOAP/REST API
Manual data entry
Ensure customer team understand these tools to
make good decisions on different data loads and
Interfaces
9
Use the Right Tool for the Data movement

• Enterprise Data in Oracle SaaS applications
• Configuration Data Companies, Ledgers, BU, COA,
  List of values etc.,
• Master Data Employees, Item, Customer,
  Supplier, Work definition, Pricelist, Fixed
  assets etc.,
• Transaction Data Journals, SO, PO, WO, AP AR
  invoices, Open balances, Historical data etc.,
• Analytical Data Pre-built subject areas,
  reports, and dashboards help to support decision
  making.

  File Import File Import File Import Web Services Web Services
Tool Selection Criteria ADFdi Spreadsheet FBDI REST API SOAP API
Object type Standard Objects All available Objects Standard Custom Objects All available Objects All available Objects
Volume (in records) lt 1000 Large Volume gt 1000) Large Volume gt 1000) Low Volume Low Volume
Development NO NO NO YES YES
Complexity Simple Standard Complex Complex Complex
Performance Standard High Standard Low Low
10
Business Use case to select the data load tool

• Customer decided to implement ERP cloud from EBS
  application
• Using sales force for CRM
• EBS for ERP
• CRM EBS Legacy interface to handle customers
  and orders

11
Data Migration Challenges
12
Data Migration Challenges
Organizations believe data migration to be a
relatively simple

• INHERENTLY COMPLEX
• Identify Legacy data
• Understood
• Migrated correctly.

• DIFFERENT ARCHITECTURE
• Complex Transformations
• Different architecture and technology

• DOCUMENTATION
• Out-of-date documentation
• In-accurate Initial programming

• KNOWLEDGE GAP
• Less knowledge
• Trial error process to migrate data.

• ADDITIONAL DATA SOURCES
• Unexpected legacy data sources

• POOR DATA QUALITY
• Data quality is worse than expected
• Requiring emergency data cleansing projects.

• DATA CONSTRUCTION
• New data must be invented.
• New system requires data that does not exist in
  the legacy system

• REQUIREMENT CHANGES
• Coding changed for the massive volume of changes.
  
• Costs soar.

13
Data Migration Strategies
14
Data Migration Strategies

• Big Bang
• Migrate in a small defined window
• Significant downtime of core systems
• Migration in shortest possible time

• Trickle or Phased
• Smaller increments until nothing left to move
• Involves parallel running systems
• Migration takes long time

• Popular strategy
• 80-90 project use this strategy
• Disruptions - large and complex business
• Less scope to roll back and test
• Compromise in data quality and process
• Use automation tools wherever possible

• Latest business needs
• For global and 24 X 7 business operations
• Eliminates business interruptions
• Enough scope to roll back
• More time to validate and test
• Temporary procedures

Pros Cons
15
How to determine the right strategy?

• Legacy instance downtime to move data into Oracle
  cloud
• Cutover duration
• Period closure and source data audit duration
• Users availability during cutover
• Simultaneous applications
• Can customer work simultaneously in legacy and
  new instance
• How long they can work in two application
• Data storage in the source system(s)
• Total Number of Attributes
• Volume of Data
• Data Quality problems and issues to fix
• Knowledge/Documentation of Data Quality issues
• User readiness to new systems
• Availability of Subject Matter Experts (SMEs)

• Dont forget to discuss how to handle
  the
• Historical Data
• Reports using historical data

16
NexInfos Migration Approach
17
NexInfos Migration Approach

• Unit test
• Full load test
• Performance test
• Benchmark
• Track Issues results
• Acceptance from user

• Confirm pre-requisites
• Initiate data migration
• Audit data
• Acceptance from business

• System Analysis Data evaluation
• Set the scope
• Identify constraints
• Identify resources

• Best Practices
• Data components
• Data mapping
• Training

• Analyse Data
• Volume
• Characteristics
• Attributes
• Prepare sample
• Identify prerequisites
• Load sequence

18
Data Component list
19
Data mapping document
20
Target field descriptions
21
Track the testing results
Data Imported (Stage ltPODgt) Data Imported (Stage ltPODgt) Data Imported (Stage ltPODgt) Data Imported (Stage ltPODgt) Data Imported (Stage ltPODgt) Data Imported (Stage ltPODgt) Data Imported (Stage ltPODgt) Data Imported (Stage ltPODgt) Data Imported (Stage ltPODgt) Data Imported (Stage ltPODgt) Data Imported (Stage ltPODgt)
Objects Data Import Action(Insert/Update/Delete) Total of Records Validation Test Batch Size Validation Test Run Time (min) Successfully Loaded Complated as of ltDategt Service Request Bug Import Job Notes/Issues
Employee(User/Resource) Insert                  
Accounts Insert                  
Contacts Insert                  
Opportunities Insert                  
Leads Insert                  
Activities Insert                  
                     
Data Imported (Production ltPODgt) Data Imported (Production ltPODgt) Data Imported (Production ltPODgt) Data Imported (Production ltPODgt) Data Imported (Production ltPODgt) Data Imported (Production ltPODgt) Data Imported (Production ltPODgt) Data Imported (Production ltPODgt) Data Imported (Production ltPODgt) Data Imported (Production ltPODgt) Data Imported (Production ltPODgt)
Objects Data Import Action(Insert/Update/Delete) Total of Records Validation Test Batch Size Validation Test Run Time (min) Successfully Loaded Complated as of ltDategt Service Request Bug Import Job Notes/Issues
Employee(User/Resource) Insert                  
22
Donts Dos - Oracle SaaS Data Migration
23
Donts in Data Migration to Oracle SaaS Cloud
applications

• Dont assume data migration is easy
• Complex, tedious and time-consuming activity
• Dont plan data migration only with technical
  team
• Need to involve team members from Business,
  Interfaces, Infra
• Dont start the data migration activities too
  late in a project 
• Often starts only after the target system design
  is complete or nearly complete
•  Good time to start the migration planning is
  after initial design or prototype
• Dont migrate all data
• Clean the data wherever possible
• Cost associated to move data (Mapping,
  validation, storage, maintenance)
• Utilize migration tools wherever possible
• Dont migrate partial data in test instance
• Identification of issues until after the
  production migration 
• Important to run a full production document
  migration in the test environment

24
Dos in Data Migration to Oracle SaaS Cloud
applications

• Prioritize Planning
• Understand business priorities and start with
  quick wins
• Need to be separate section in the project
• Measure the complexity of data migration
  initiative
• Understand your technology and application
  requirements.
• Estimate migration effort.
• Determine the full set of capabilities
• Focus on the Areas of High Complexity
• Technology capabilities
• Data Quality issues Fix them early
• Build a metadata-driven solution
• Provides more information about data
• Easier for users to understand the meaning of
  data and to understand the lineage of data across
  the environment

25
Dos in Data Migration to Oracle SaaS Cloud
applications

• Use standards to reduce complexity
• Use of open and common standards related to data,
  integration and infrastructure
• Take a diligent approach to testing
• Data migrations are complex
• High user expectations in new system.
• A systematic testing process should be followed,
  from initial functional testing to final user
  acceptance
• Document the whole process
• Vital to document the entire process
• Data undergoes degradation after a point of time,
  making it unreliable.
• Helps in process improvement and to automate the
  functions
• Continuous business engagement
• Communicate continuously about the strategy and
  progress
• Give business users more access to data

26
NexInfo's Data Migrator
27
NexInfo's Data Migrator

• Login Page

28
NexInfo's Data Migrator

• PIM User Home page

29
NexInfo's Data Migrator

• Item Creation

30
NexInfo's Data Migrator

• Item Creation To Fusion From EBS

31
Item Creation To Fusion From EBS
32
Item Creation To Fusion From EBS
33
NexInfo's Data Migrator

• Item Creation To Fusion Through File Upload

34
NexInfo's Data Migrator

• Item Creation To Fusion Through File Upload

35
NexInfo's Data Migrator

• Item Creation To Fusion Through File Upload

36
NexInfo's Data Migrator

• Job Details

37
NexInfo's Data Migrator

• Log file

38
NexInfo's Data Migrator

• Item created in fusion

39
NexInfo's Data Migrator

• Item Extraction From EBS

40
NexInfo's Data Migrator

• Item Extraction From EBS

41
NexInfo's Data Migrator

• Error handling

42
Contact Us
Dublin, Ireland
Bellevue, WA
Bridgewater, NJ
Orange, CA Santa Ana, CA
Chicago, IL
Bangalore, India
Chennai, India
43
Thank you for joining us today.
Questions?