SAP BYD Data Migration steps

1. Introduction to Data Migration
for the SAP Cloud Solution
Customer

2. © 2013 SAP AG. All rights reserved. 2Ramp-Up Knowledge Transfer Customer
Legal Disclaimer
This presentation outlines our general product direction and should not be
relied on in making a purchase decision. This presentation is not subject to
your license agreement or any other agreement with SAP. SAP has no
obligation to pursue any course of business outlined in this presentation or to
develop or release any functionality mentioned in this presentation. This
presentation and SAP's strategy and possible future developments are subject
to change and may be changed by SAP at any time for any reason without
notice. This document is provided without a warranty of any kind, either
express or implied, including but not limited to, the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement. SAP
assumes no responsibility for errors or omissions in this document, except if
such damages were caused by SAP intentionally or grossly negligent.

3. What is Data Migration?

4. © 2013 SAP AG. All rights reserved. 4Ramp-Up Knowledge Transfer Customer
Data Migration Defined
Data Migration is the process of transferring data between the source
system and a new target system.
The successful migration of data is a critical task for every SAP Cloud Solution
implementation project. Incomplete or inaccurate migration of data can lead
to:
 Decreased end user productivity
 Mishandling of open transactions impacting cash flow and operations
 Delays in financial close activities

5. © 2013 SAP AG. All rights reserved. 5Ramp-Up Knowledge Transfer Customer
Schedule
Cleanse
Extract Source Data
Populate Migration Templates
Test Migration
Verify
Cutover Migration
Data Migration Steps

6. © 2013 SAP AG. All rights reserved. 6Ramp-Up Knowledge Transfer Customer
Step 1: Schedule
Schedule activities are performed using the Project Schedule for Data
Migration tool. Using the tool, the project team:
 Selects the scope that is relevant to the implementation project
 Assigns the person who is responsible for each data object
 Identifies the source system for each data object
 Decides which format to use when migrating each data object (i.e. manual,
.txt file, etc.)
 Defines due dates and sequence for the migration of each data object into a test
system
 Defines due dates and sequence for the migration of each data object into a production
system
Create a precise project plan for all tasks related to migration.

7. © 2013 SAP AG. All rights reserved. 7Ramp-Up Knowledge Transfer Customer
Step 2: Cleanse
Cleansing activities include:
 Deleting duplicate records
 Removing obsolete records and any associated transactions
 Checking for values in wrong fields
 Validating address data is complete
 Confirming the format of contact data such as e-mail addresses, postal codes,
phone numbers, etc.
Cleanse the data prior to entering it into the SAP Cloud Solution in
order to avoid technical errors during migration or usability issues.

8. © 2013 SAP AG. All rights reserved. 8Ramp-Up Knowledge Transfer Customer
Step 3: Extract Source Data
Activities:
 Review the format required for entering the data into the new target system in
order to export the data in a similar structure (such as order of columns and
grouping of details)
 Extract the data using a report or database query into a .xls, .csv, .txt or other
flat file format
Export the data from the source system(s)
Note that this step may be performed prior to the Cleanse step, in which case the data is cleansed
within the extracted files and not directly within the source system

9. © 2013 SAP AG. All rights reserved. 9Ramp-Up Knowledge Transfer Customer
Step 4: Populate Migration Template
If the data is scheduled to be imported into the SAP Cloud Solution,
then copy the data from step 3 into the migration templates provided by
SAP.
Activities:
 Download required migration templates directly from the SAP
Cloud Solution
 Copy extracted, unformatted data into the templates

10. © 2013 SAP AG. All rights reserved. 10Ramp-Up Knowledge Transfer Customer
Step 5: Test Migration
Activities:
 Import or manually enter data into the SAP Cloud Solution test
system, in the order identified within the Project Schedule for
Data Migration
 Accurately map the values within the source data to the SAP
Cloud Solution, using the tool (for example, US = United States)
Test the migration of the source data into the SAP Cloud Solution to
ensure a successful cutover into the production system.

11. © 2013 SAP AG. All rights reserved. 11Ramp-Up Knowledge Transfer Customer
Step 6: Verify
Activities:
Confirm the number of migrated records is as expected
 Perform spot checks
 Run reconciliation reports in the system
 Run end-to-end business scenarios within the SAP Cloud
Solution using the migrated data
Verify the migrated data is reflected in the SAP Cloud Solution as
expected.

12. © 2013 SAP AG. All rights reserved. 12Ramp-Up Knowledge Transfer Customer
Step 7: Cutover Migration
Activities:
 If the values were correctly mapped in the test system, then export the value
conversion files and import them into the SAP Cloud Solution production
system via the data migration tool
 Import or manually enter data into the SAP Cloud Solution production
system, in the order identified within the Project Schedule for Data
Migration
 Verify that all data was imported successfully
Perform the final entry of source data into the SAP Cloud Solution
production system.

13. Data Migration Misconceptions

14. © 2013 SAP AG. All rights reserved. 14Ramp-Up Knowledge Transfer Customer
Common Misconception #1
Data migration is
a job for IT
Wrong! Your IT department may be
involved to extract the data, but business
users are also engaged since they
understand the business context of the
data.

15. © 2013 SAP AG. All rights reserved. 15Ramp-Up Knowledge Transfer Customer
Common Misconception #2
We can always
change migrated
data after we go
live
This cannot be assumed! Some data
items, such as a customer’s address, can
be changed after migration is completed;
whereas other records, such as financial
data, cannot be changed.

16. © 2013 SAP AG. All rights reserved. 16Ramp-Up Knowledge Transfer Customer
Common Misconception #3
It’ll be easy to
cleanse my data
Probably not! Most companies find data
cleansing to be very time consuming.

17. © 2013 SAP AG. All rights reserved. 17Ramp-Up Knowledge Transfer Customer
Common Misconception #4
I don’t have to
perform data
migration – this is
done by SAP or one
of its partners
Are you sure? The standard SAP Cloud
Launch service assumes all data
migration tasks are executed by the
customer. An optional data migration
service can be purchased for SAP or a
partner to perform some of the data
migration activities, but customer
involvement is always needed.

18. Data Migration in the
SAP Cloud Implementation Methodology

19. © 2013 SAP AG. All rights reserved. 19Ramp-Up Knowledge Transfer Customer
VERIFYPREPARE REALIZE LAUNCH
Production Systems Setup
Solution Testing
Cutover Planning
Solution Walkthrough
Data Migration
Cutover Execution
Business Process Confirmation
Key User Enablement
SAP Cloud Implementation Methodology
Scope
Verification
Project Management
Change Management and End User Training Go-Live
Solution Configuration
Solution
Acceptance
Readiness
Acceptance
Custom Content Specifications
Custom Content Development
Integration Readiness
Cloud Integration
Data migration activities
span all phases of the
implementation project
Data migration activities
span all phases of the
implementation project

20. © 2013 SAP AG. All rights reserved. 20Ramp-Up Knowledge Transfer Customer
Leading the Way
Depending on the SAP Cloud Launch
service chosen by your company, a
data migration workshop may be
delivered to jump start your data
migration activities.
With that said, it’s never too early to
start cleansing data!

21. © 2013 SAP AG. All rights reserved. 21Ramp-Up Knowledge Transfer Customer
Data Migration Information
Migration Tool Help
Help Center
Documentation
in Go-Live Activity List
More information is available in the SAP Business Center…
www.sme.sap.com
Data Migration Wiki
… and in your SAP Cloud Solution

22. © 2013 SAP AG. All rights reserved. 22Ramp-Up Knowledge Transfer Customer
© 2013 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or
warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing
herein should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in
Germany and other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.