Selective Data Transition
A hybrid approach that combines elements of greenfield and brownfield—migrate selected data and configuration while leaving behind what you don't need.
months typical duration
scope and approach
what data to migrate
of both approaches
What is Selective Data Transition?
Selective Data Transition (SDT) is an umbrella term for hybrid migration approaches that let you choose what to bring forward to S/4HANA. Unlike brownfield (bring everything) or greenfield (bring nothing), SDT gives you granular control.
You might migrate master data and open items but leave historical transactions behind. You might convert configuration and customisations but cleanse data quality issues along the way. You might consolidate multiple source systems into one S/4HANA instance.
This flexibility comes with complexity. SDT requires careful planning of what moves, what stays, and how to maintain continuity. It typically involves specialized migration tools and often requires parallel operations during transition.
Key Characteristics
- New S/4HANA shell
- Selected data migrated
- Config can be transferred
- System consolidation possible
Last Updated
January 15, 2026
Sources
- •SAP SDT Guide
- •SAP Landscape Transformation
Information based on publicly available SAP documentation and industry sources. For the latest details, consult SAP official materials or qualified partners.
SDT Variants
Shell Conversion
Convert configuration, migrate selected data
Start with a brownfield conversion to create a "shell" with your configuration, then selectively migrate data. Useful when config is valuable but data needs cleansing.
Best for:
- • Complex configuration you want to preserve
- • Data quality issues in source system
- • Regulatory need to start fresh on some data
Landscape Transformation
Consolidate multiple systems into one
Merge multiple ECC systems into a single S/4HANA instance. Each source system contributes data according to defined rules. Often used post-M&A.
Best for:
- • Multiple ECC instances to consolidate
- • Post-merger integration scenarios
- • Harmonising across business units
Mix & Match
Greenfield shell with targeted data migration
Start with a greenfield implementation (new processes), but use migration tools to bring forward selected historical data for reporting or continuity.
Best for:
- • Process transformation + data continuity
- • Regulatory data retention requirements
- • Hybrid business change appetite
When SDT Fits
Good Fit Indicators
- 1
Multiple systems to consolidate
SDT tools support merging data from multiple sources into one target
- 2
Data quality issues
Want to cleanse or leave behind problematic data during migration
- 3
Partial history requirements
Need some historical data but not everything—e.g., last 3 years only
- 4
Configuration investment
Years of configuration you want to preserve but with fresh data
- 5
Carve-out or spin-off
Need to separate a business unit with its data into a new S/4HANA
Warning Signs
- !
Simple single-system scenario
If you have one ECC and need all data, brownfield is simpler
- !
Limited tooling budget
SDT typically requires SAP or third-party migration tools with licensing costs
- !
Unclear data requirements
SDT requires precise decisions about what migrates—ambiguity causes problems
- !
Compressed timeline
SDT adds complexity—may not be faster than a clean greenfield
Data Migration Strategy
Decisions to make before starting SDT
1Master Data
- • Customers / Business Partners
- • Vendors / Suppliers
- • Materials / Products
- • GL Accounts / Cost Centers
- • Employees / Personnel
Decision: Migrate all, migrate active only, or cleanse and migrate?
2Open Items
- • Open sales orders
- • Open purchase orders
- • Open AR/AP items
- • Work in progress
- • Incomplete deliveries
Decision: Migrate open items or complete/close in source first?
3Historical Data
- • Closed sales orders
- • Historical invoices
- • Prior year financials
- • Archived documents
- • Audit trail data
Decision: How many years? Aggregate or detail? Archive access?
Common Patterns
Conservative
All master data + open items + 3-5 years history. Source archived for compliance.
Aggressive
Active master data + open items only. History accessed via source archive.
SDT Tools Landscape
SAP Native Tools
SAP S/4HANA Migration Cockpit
Standard tool for data migration with pre-built templates
SAP Landscape Transformation (SLT)
Real-time replication and transformation for larger migrations
SAP Data Services
ETL capabilities for complex transformations
Partner/Third-Party Tools
SNP (formerly Bluefield)
CrystalBridge for selective data transition and carve-outs
Syniti
Enterprise data management and migration platform
Natuvion
Data transformation and harmonization tools
Note: Tool selection depends on your specific scenario. Consolidation, carve-out, and shell conversion each have different tooling requirements. Engage early with vendors to validate fit.
Typical Timeline
Discovery & Planning
2-4 monthsTarget System Setup
2-4 monthsMigration Development
3-6 monthsTesting
3-4 monthsCutover
1-2 weeksHypercare
2-3 monthsNote: SDT timelines vary significantly based on variant chosen, data volume, number of source systems, and complexity of transformation rules.