Companies migrating from SAP ECC to S/4HANA spend weeks building spreadsheets, chasing the wrong file format, and discovering data errors on go-live night. SAP Migrator gives your team a structured workspace to prepare, validate, and execute every migration object — from GL Accounts to Material Masters.
It generates the exact MS Excel XML Spreadsheet 2003 files the SAP Migration Cockpit requires. It runs simulations that catch every error before cut-over. It stores your value mappings so nothing gets lost.
Free to start · No credit card · No SAP login required to use the platform
These are the four things that kill migration projects. We built SAP Migrator to eliminate each one.
Teams discover data errors on cut-over night because they never validated records against SAP rules. Our simulation run catches every error days before.
SAP Migration Cockpit only accepts MS Excel XML Spreadsheet 2003. Not .xlsx, not .csv. Teams waste hours reformatting. We generate it correctly in one click.
Teams maintain separate mapping spreadsheets that get out of sync. We give every object its own mapping store, visible to the whole team, version-controlled with each run.
Consultants work in SAP transactions that PMs can't access. Our dashboard shows readiness %, object status, run history, and error counts — no SAP login needed.
Five steps from your first legacy data extract to a clean production load in SAP S/4HANA. Each step maps directly to the SAP Activate methodology phases.
Browse a catalog of 20+ real SAP migration objects organised by module — Finance, Controlling, Master Data, Logistics, Inventory, HR, and Basis. Tick the ones your project needs. The platform filters automatically based on whether you chose Staging Tables or Direct Transfer.
Objects include their SAP table names, all required and optional fields, technical field names, and example values — no need to look these up.
Every legacy system uses different codes. A currency called "US Dollar" in your old system must become "USD" in SAP. Company code "Company A" must become "1000". The mapping studio lets you define these translations field-by-field per object.
Mappings persist across runs. Add, edit, and delete them at any time. The correction file download uses your mappings to pre-fill fixes after failed records.
Click once to download an MS Excel XML Spreadsheet 2003 file for each object. This is the exact format required by the SAP S/4HANA Migration Cockpit staging table approach. Row 1 is field labels, Row 2 is technical names, Rows 3+ are your data.
Each template includes a second "Field Guide" worksheet with field descriptions, required flags, max lengths, and examples. Open in Excel — do NOT save as .xlsx.
Populate the template with your legacy data, then upload it back. The platform records the file, row count, and validation status. Common pitfalls are caught early: NUMC fields need leading zeros, dates must be YYYY-MM-DD, paste as Values Only not Ctrl+V.
Files up to 100 MB are supported. Compress to ZIP for larger extracts (up to 160 MB). Each object has its own template — you can upload them in any order.
Run a Simulation first — this validates every record against SAP's rules without writing a single byte to the database. The result shows you exactly which records succeed, which have errors, and which have warnings. Fix errors, re-run until clean. Then execute the real Migration run.
Simulation is equivalent to SAP's TESTRUN API parameter. Error records can be exported as a CSV correction file, fixed, and re-uploaded. The run history is preserved for audit.
20+
SAP Migration Objects
2
Migration Approaches
100%
Cockpit-Compatible XML
0
SAP Licences Required
Every object is defined with its SAP table name, all field definitions, required vs optional flags, technical names, and example values. Select exactly the objects your project needs.
GL Account Master
SKA1/SKB1
FinanceOpen Items AR
BSID
FinanceOpen Items AP
BSIK
FinanceAsset Master
ANLA/ANLB
FinanceExchange Rates
TCURR
FinanceCost Center
CSKS
ControllingProfit Center
CEPC
ControllingInternal Order
AUFK
ControllingBusiness Partner
BUT000
Master DataCustomer Master
KNA1/KNB1
Master DataVendor Master
LFA1/LFB1
Master DataMaterial Master
MARA/MARC
Master DataBank Master Data
BNKA
Master DataPurchasing Info Record
EINA/EINE
LogisticsPricing Conditions
KONV
LogisticsInitial Stock Upload
MARD
InventoryBatch Master
MCH1
InventoryEmployee Basic Pay
PA0008
HRPayment Terms
T052
BasisHouse Bank
T012
BasisEnterprise plan includes custom migration objects for client-specific requirements
SAP supports two migration approaches. You choose when creating a project and the platform adjusts the available objects, templates, and run options accordingly.
Data is loaded via MS Excel XML Spreadsheet 2003 files or by filling SAP HANA staging tables (/1LT/DS*) directly using ABAP, ETL tools, or SAP HANA Studio.
Data is transferred live from a source SAP system to the target S/4HANA via RFC connection. No file export or ETL tool needed — the cockpit reads directly from the source.
Run multiple concurrent migration projects across client landscapes. Each client gets their own isolated workspace. Reuse your value mapping templates across similar clients.
Your IT team is running the S/4HANA migration themselves. You need a structured tool that tracks what's done, what's mapped, and what errored — without building it in Excel.
You're embedded at a client, working on the migration workstream. You need the right file format, the right field names, and a way to show the PM progress without giving them SAP access.
Start free. Upgrade when you need more objects or projects.
For small migrations or exploring the platform
Yes. SAP Migrator prepares your data — it generates the correctly-formatted XML templates, manages your value mappings, tracks runs, and handles error correction. You still upload the final XML into the SAP Migration Cockpit or fill staging tables directly. We make the preparation phase dramatically faster and less error-prone.
Staging Tables means you prepare data in XML files (or fill /1LT/DS* tables directly) and the cockpit posts them to SAP. It works for 184+ objects and supports S/4HANA Cloud. Direct Transfer uses an RFC connection between a source SAP system and the target S/4HANA — no file export needed — and supports 255+ objects but only on-premise. You choose your approach when creating a project.
All content is based on SAP S/4HANA 2021 / 2022. The migration objects, field names, and staging table structures match the SAP S/4HANA Migration Cockpit 2nd edition documentation. Custom object support is available on Enterprise plans.
Simulation validates every record — checking required fields, value mapping completeness, field lengths, date formats, and SAP master data references — without committing anything to the database. It is equivalent to running the SAP BAPI with TESTRUN = "X". Fix all errors shown in the simulation before executing the real Migration run.
Yes. Every user you invite shares the same project workspace. They can see migration objects, add value mappings, upload templates, and view run results. Role-based access (Admin, Migrator, Viewer) controls what each person can do.
Your data lives in an isolated PostgreSQL database per organisation. We never share data between customers. Secrets (database credentials, auth tokens) are encrypted at rest. The platform runs on DigitalOcean's SOC 2 certified infrastructure.