This lesson focuses on developing the data migration approach and plan during the Prepare phase. The plan defines what will be migrated, how it will be governed, who is responsible, and when key milestones occur. The actual execution of data migration activities — profiling, mapping, mock loads, and cutover — takes place in the Explore, Realize, and Deploy phases, and is covered in later units.
Data Migration Approach Planning
Developing the data migration approach and plan is a critical planning activity that occurs during the SAP Activate Prepare phase. This early planning is essential to prevent the migration from becoming a project bottleneck, as data-related issues are a leading cause of implementation delays.
Note
During the Prepare phase, the focus is on planning artifacts — the approach, plan, scope, roles, and tooling selection. The actual hands-on migration work (profiling, mapping, mock loads, reconciliation) begins in the Explore phase and continues through Realize and Deploy.
Purpose
The purpose of this task is to develop the data migration approach and plan.
Procedure
Create the data migration approach and plan to cover the following:
Key milestones for data delivery
Scope of required data sets and their source systems
Resource needs, including defined roles and responsibilities
Estimated volumes for each data set
Required tools (e.g., legacy data extraction, data cleansing, migration cockpit, etc.)
Data migration testing activities
Data validation procedures
Data cleansing efforts
Productive system load and post-load support
Reporting and tracking mechanisms
|
Accelerator(s)
Now that you have reviewed the comprehensive process for developing the data migration plan, let’s distill that information into the executive summary.

Executive Summary
Executive summary provides a clear, high-level overview of the project’s core purpose and guiding principles, anchoring the conversation for executives and sponsors.
Executive summary essentially tells executives what is being done (migration objective), how success is measured (success target), and how the work will be governed (delivery model).
Migration Objective
Move core HR and supporting talent data from legacy platforms into SuccessFactors using a controlled, phased migration approach.
Success Target
- Achieve ﹥99.5% field-level accuracy.
- Migrate 100% of critical employee and organization records.
- Complete cutover without unplanned business downtime.
Delivery Model
The migration will be governed by three core practices:
- Use iterative mock loads.
- Establish formal reconciliation checkpoints.
- Obtain business sign-off.
While the high-level targets in executive summary define what we will achieve, it’s important to understand why they matter to the business. This breakdown clarifies the relationship between the strategic goals of the project and the measurable criteria used to ensure its success.

Business Objectives and Success Criteria
Business Objectives (The "Why")
Following are the high-level strategic goals the business aims to achieve with this migration. They answer the question, "What business value will this project deliver?"
- Establish a single source of truth for HR data across the enterprise.
- Enable cleaner analytics, reporting, and downstream process automation.
- Support global standardization of core HR processes and governance.
Cutover Principles (The "Rules of Engagement")
Following are the fundamental rules that guide the go-live process to ensure safety and minimize business disruption.
- Protect payroll, reporting, and employee transactions during go-live.
- Use freeze windows and rollback decision points to manage risk.
Migration KPIs (The "Measurable Targets")
Following are the specific, measurable Key Performance Indicators that define a technically successful migration. They answer the question, "How will we know we did it right?"
- ﹥99.5% field-level accuracy
- 100% migration of critical records
- Zero unplanned downtime during cutover
- ﹥90% user satisfaction with migrated data quality
Governance Outcomes (The "Proof and Control")
Following are the process-driven outcomes that ensure quality and accountability throughout the project and immediately after go-live.
- Formal sign-off at each mock-load cycle
- Operational monitoring during hypercare
With our objectives and success criteria established, let’s define the project’s scope.

Modules in Scope
The following module list determines the data dependencies, transformation logic, and sequence of migration loads. Note that the Employee Central is the anchor for all downstream objects.
- Employee Central (EC): foundational HR master data, job information, organizational assignments, and effective-dated employment history.
- Performance & Goals: historical goal and performance data as needed for continuity and reporting.
- Succession & Development: talent profiles, readiness indicators, and succession-relevant attributes where implemented.
- Compensation Management: compensation structures, pay elements, and reference values required for planning and administration.
- Recruiting Management (if applicable): candidate and requisition-related data depending on deployment scope and retention decisions.

Scope: Data Entities and Indicative Volumes
With the migration scope defined across these five modules, it is important to move from what will be migrated to how much and how ready that data actually is.
Following table provides a high-level overview of the data we are migrating, including its volume, current quality, and priority.
| Data Category | Typical Content | Indicative Volume | Quality Score | Priority |
| Employee master | Personal Info, job, contact, hire history | 10,000+ records | 85% | High |
| Organizational data | Business units, departments, positions, cost centers | 500+ positions | 90% | High |
| Compensation data | Salary, pay grade, pay components, history | 3 years history | 80% | Medium |
| Performance data | Goals, ratings, review history | 2 years history | 75% | Medium |
Observe that while foundational data like Employee Master and Organization data has high quality scores (85-90%), other domains such as Compensation and Performance are lower (75-80%). These lower scores indicate more inconsistencies and errors, which will require significant cleansing and remediation effort.
By identifying these gaps now, we can proactively plan the work to prevent data issues from becoming a bottleneck during migration cycles.

Activate Alignment for Data Migration
SAP Activate data migration activities are staged across the full methodology to reduce delivery risk and increase business readiness. The type of work performed in each phase differs significantly — planning happens early, execution happens later.

This image illustrates how our data migration workstream aligns with the SAP Activate methodology to reduce risk through a phased approach:
- Discover: Define the high-level Strategy, Scope, and Approach.
- Prepare: Develop the detailed Plan — scope of data sets, source systems, resource needs, roles, tooling, cleansing strategy, and key milestones.
- Realize: Set up migration environments, source connectivity, security, and initial extraction tests. Complete profiling of high-priority objects, define the first cleansing backlog, develop field mappings, build ETL or load files, run initial mock cycles, and validate integration touchpoints.
- Deploy: Execute the final Cutover, manage the Go-live, and provide intensive Hypercare support.

Current-State Assessment and Source Analysis
Note
Full current-state assessment and source analysis is typically initiated in Prepare (at a high level to inform the plan) and completed in Explore (through detailed profiling of high-priority objects).
Before mapping can begin and mock loads can be executed, the team must first understand the current state of the source data. This assessment aligns both business and technical teams on what we have, what we need, and what risks must be addressed before the migration work begins.
Assessment Focus Areas
- Source system extraction capability and access method
- Data-quality profiling and cleansing requirements
- Downstream and upstream integration touchpoints
Technical Questions
- Can historical records be extracted with effective dates intact?
- What performance constraints exist for full extracts?
Business Questions
- Which data objects are legally or operationally required at go-live?
- Which history can be archived instead of migrated?
Output of Assessment
- Extraction inventory
- Cleansing backlog
- Interface dependency list
- Initial risk register
Migration Strategy and Progressive Load Cycles
With a clear picture of our source data and its quality, we can now define how we will migrate it.
The migration plan uses progressive loads so that structure, people data, and dependent transactions are proven in sequence before production cutover.

The figure illustrates that the team proves the migration in layers. Organization and foundation data must stabilize first, then employee master data, and then dependent transactions before the final production load.

Technical Architecture and Tooling
With our load sequence defined, the next step is to select the right tools to execute it. The choice of tooling depends on the complexity of the source data and the level of transformation required. Standard templates are usually sufficient for simpler loads, while Data Services is useful for heavy cleansing or derivations.
Primary Tools
- SAP Info-porter for SAP ERP HCM to Employee Central migrations where applicable
- SuccessFactors import templates for standard batch loads
- SAP Data Services for complex ETL and data quality transformations
- Integration Center for controlled delta synchronization and post-go-live needs
Selection Criteria
- Support full and incremental loads
- Built-in validation and error handling
- Auditable logs and monitoring
- Extensibility for custom mappings and derived fields
Architecture Principle
Separate extract, transform, load, and validation steps so issues can be isolated quickly.
Now that we have identified the tools, let’s look at how data actually moves through the migration pipeline.

Data Flow Architecture

The figure illustrates exactly how each step connects, and importantly, why validation is not a final afterthought. It is embedded after every load step and drives defect resolution between mock conversions.
Controls embedded in the flow: source-to-target reconciliation, data-quality exception logging, business-rule validation, and formal sign-off before production migration.
Now that we understand how data moves through the pipeline, let’s look at how it is transformed along the way.

Data Mapping Principles
Field mapping is not just a one-to-one exercise. The target SAP SuccessFactors model often requires re-structuring relationships, effective dates, or code values to support standard processes.
SAP SuccessFactors Employee Central Core Fields
- Personal information: names, addresses, phone, email
- Employment data: hire dates, positions, managers, event reasons
- Organizational assignments: department, location, cost center, business unit
Transformation Rules
- Standardize dates to YYYY-MM-DD
- Map currencies and normalize pay frequencies
- Restructure or flatten hierarchies where the target model differs
- Derive custom fields based on agreed business rules

Data Mapping Examples and Validation Rules
Now let’s see these mapping principles in practice. The following examples illustrate how transformation rules and validation criteria are documented, and why business teams must own the confirmation of these rules and the resolution of any exceptions.
| Source field | Target field | Rule / transformation | Validation |
| Employee ID | Personal ID External | Trim spaces; retain unique key | Unique and non-null |
| Hire Date | Start date | Format to YYYY-MM-DD | Valid date and ﹤﹦current date |
| Legacy Cost Center | Cost center | Crosswalk to target code list | Exists in target foundation data |
| Currency Code | Pay component currency | Map to ISO code | Allowed value list |
In this example, the source system stores the hire date as Hire Date, which must be renamed to Start Date in SAP SuccessFactors and reformatted from a day-first format to the standard YYYY-MM-DD format. Once loaded, the system validates that the value is a real date and does not fall in the future.

Execution Detail: Prepare and Explore
With our mapping rules and validation criteria defined, let’s look at how this work is executed in practice. The Prepare and Explore phases translate our strategy into action, moving from team setup and risk discovery through to building, testing, and stabilizing the migration files.
Prepare Phase
- Form the migration team, assign workstream roles, and confirm governance and sign-off model.
- Set up migration environments, source connectivity, security, and initial extraction tests.
- Complete profiling of high-priority objects and define the first cleansing backlog.
Explore Phase
- Develop field mappings, build ETL or load files, and unit test load sequences.
- Validate individual load templates and transformation logic at a small, controlled scale.

Execution Detail: Realize and Deploy
With mappings stabilized and mock loads tested in the Explore phase, we move into the final two phases where the business confirms the migration is ready for production during the Realize phase and the approved plan is executed within a tightly governed cutover window during the Deploy phase.
Realize Phase
- Run mock conversion cycles using progressively larger data volumes.
- Reconcile defects, validate integration touchpoints, confirm end-to-end business scenarios.
- Rehearse the full cutover plan in preparation for Deploy.
Deploy Phase
- Perform final extraction, production load, reconciliation, and release decision checkpoints.
- Launch hypercare with daily monitoring, defect triage, and business support.

Quality Assurance and Validation Framework
Executing the migration phases is only part of the story. Let’s look at the quality assurance framework that runs throughout every phase to ensure that a technically clean load also becomes a reliable, business-ready operational dataset.
Quality Dimensions
- Completeness: all required records and fields loaded
- Accuracy: values match approved source records
- Consistency: referential integrity across related objects
- Business rules: target validations pass without unresolved defects
Control Activities
- Record-count reconciliation
- Field-level spot checks and exception analysis
- Business process testing with migrated data
- Defect tracking and remediation between cycles

Reconciliation and Sign-Off Model
With our quality dimensions and control activities defined, let’s look at how we formally close each migration cycle. The reconciliation and sign-off model ensures that both technical evidence and business confirmation are in place before the team is approved to proceed to the next load.
Pre-Load Reconciliation
Validate source extracts, reference data availability, and known cleansing actions before each load.
Post-Load Reconciliation
Compare source-to-target record counts, validate key fields, and review load error logs and rejected records.
Business Validation
Business owners confirm that migrated data supports process execution, reporting, and security visibility.
Formal Sign-Off
Approve progression to the next migration cycle only after technical and business exceptions are resolved or explicitly accepted.

RACI for the Migration Workstream
With the sign-off process defined, it’s equally important to clarify who is responsible for each step. Let’s look at the RACI chart, which establishes clear ownership across the migration workstream to avoid confusion and ensure accountability at every stage.
As can be observed, the migration lead remains accountable for delivery, while business SMEs own validation and technical teams own file execution.
| Activity | Migration Lead | Data Expert | Business SME | Tech Team |
| Source profiling | A | R | C | C |
| Field mapping | A | R | C | C |
| ETL / file build | C | A | I | R |
| Validation & UAT | C | R | A | I |
| Cutover execution | A | R | C | R |
R = Responsible | A = Accountable | C = Consulted | I = Informed

Illustrative Cutover Weekend Timeline
With roles and ownership clearly defined, let’s walk through how the team executes the go-live. This timeline illustrates the cutover weekend sequence, highlighting where business stakeholders are needed for validation and where the rollback decision point sits.
Illustrative weekend cutover plan designed to minimize business interruption and keep rollback options available.

Rollback decision point is retained until production validation completes. Stakeholder communications, security checks, and support-team hand-off occur throughout the weekend.
Watch the video to explore how a structured cutover weekend is executed — from freezing the source system on Friday through to go-live and hypercare on Monday.
| Key Points from Video |
|---|
|

Resource and Infrastructure Requirements
Executing the cutover weekend successfully depends on having the right people, tools, and infrastructure in place well before go-live. Let’s look at the resource and operational readiness requirements that underpin the entire migration.
Security, access, and lower-environment controls are essential because HR data is highly sensitive.
Core Team
- Data migration lead / architect
- Business process expert(s)
- Technical consultants / ETL developers
- Business SMEs for validation and decision-making
Extended Support
- Project lead
- Security/admin support
- Change management
- Service desk readiness
Infrastructure Needs
- Development and test staging environments
- Secure network connectivity between source and target systems
- Backup / recovery controls and audit logs
- Monitoring and alerting for load execution
Security Controls
- PII masking in lower environments
- Controlled role-based access

Post-Migration Hypercare and Governance
With the right team and infrastructure in place, our final responsibility is to ensure the migration delivers lasting value. Hypercare is not a separate support activity — it is the final phase of the migration itself, closing the loop between go-live defects, ongoing governance, and long-term data stewardship.
Immediate Hypercare (First 4 Weeks)
- 24/7 monitoring of system performance and critical data integrity checkpoints.
- Rapid issue resolution and controlled data-correction procedures with auditable approvals.
- Daily data-quality reports, trend analysis, and escalation management.
Ongoing Governance
- Weekly quality assessments, monthly reconciliation reporting, and quarterly governance reviews.
- Continuous improvement actions for process, mapping, and control optimization.
Knowledge Transfer and Deliverables
Sustaining the gains made through hypercare depends on one final, critical deliverable: knowledge transfer. Ensuring that support teams and business owners are fully equipped with the right documentation and training is what allows the organization to maintain data quality and govern the system long after the project team has moved on.
Core Documentation
- Field mapping workbook, transformation rules, load sequence documentation, and reconciliation evidence.
- ETL or file-generation instructions, error-handling playbooks, and maintenance procedures.
Enablement
- Technical training for support teams on tools, interfaces, and troubleshooting.
- Business training on new data structures, governance roles, and defect-reporting procedures.



