#20260907012_EN1 min readUpdated: Category: Migration
1. Inventory
Record every interface used in production, including source, target, frequency, business department, 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
Sort into three categories: technically transferable, requiring rework, new build. Graphical mappings and simple value mappings are usually transferable, extensive Java or XSLT logic rarely.
3. Define Reusability
Define a reference flow for each integration pattern (IDoc, file, SOAP, REST, B2B). Every additional interface of that pattern follows the template — this is the biggest lever for the overall effort.
4. Test Coverage
For every interface: test case, test data, business sign-off owner. Without a designated sign-off owner, cutover gets delayed, not the testing.
5. Connectivity and Permissions
Request Cloud Connector, certificates, firewall rules, and technical users early — this is consistently the underestimated critical path.
6. Cutover
Sequence by business unit, not by technology. Plan parallel runs per wave, document rollback paths, and set up monitoring before go-live.
7. Post-Migration Operations
Establish alerting, responsibilities, and escalation paths before the first wave goes live. Otherwise, project mode becomes permanent.
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