1 min readUpdated: Category: Migration
1. Inventory
Record every interface used in production, including source, target, frequency, business unit, and contact person. Anything that has not processed a message in twelve months is a candidate for decommissioning — experience shows this applies to 15 to 30 percent.
2. Mapping Assessment
Categorize into three groups: technically transferable, requires rework, rebuild. Graphical mappings and simple value mappings are usually transferable, while extensive Java or XSLT logic rarely is.
3. Define Reusability
Define a reference flow for each integration pattern (IDoc, File, SOAP, REST, B2B). Every subsequent interface for that pattern follows this template — this is the biggest lever for reducing overall effort.
4. Test Coverage
For every interface: test case, test data, business sign-off owner. Without a designated business owner, the cutover will be delayed, not the testing.
5. Connectivity and Permissions
Request Cloud Connector, certificates, firewall approvals, and technical users early — this is consistently the most underestimated critical path.
6. Cutover
Sequence by business unit, not by technology. Plan for parallel operation per wave, document rollback procedures, and establish monitoring before go-live.
7. Post-Migration Operations
Define alerting, responsibilities, and escalation paths before the first wave goes live. Otherwise, project mode will become a permanent state.
More articles
— AMS & support
In-House Team or Outsourced AMS? Decision Matrix for SAP Support
— AMS & support
How to Calculate SAP AMS Costs
— Shoring
SAP Shoring or Nearshore? Model and Cost Comparison