Profile the SQL Server source
Inventory approved schemas, legacy keys, customer relationships and source data-quality defects. Use least-privilege read-only discovery before any private extraction worker is authorized.
Define source-to-target mappings
SAP S/4HANA business objects may not match the source table design. Agree how legacy customer IDs, names, contact details, sold-to references and payment terms map, and record every transformation assumption.
Approve the supported SAP interface
For the customer's exact edition and release, confirm the supported SAP migration object, Migration Cockpit or authorized API route, roles and license rights. Never write business application tables directly.
Prove both sides
Compare source, rejected and accepted counts. For a genuine SAP load, independently read back target IDs and critical attributes, review rejects, and retain signed business evidence.
Prepare a safe rehearsal
Limit the first run to approved nonproduction data with cancellation, retry, cost bounds and rollback/compensation decisions. Do not mistake local CSV success for customer-target certification.