Which SAP data migration tools are there?
SAP data migration tools fall into four groups: Excel-based loaders, SAP-native loaders (the SAP S/4HANA Migration Cockpit and LSMW), ETL platforms (SAP Data Services and SAP Advanced Data Migration by Syniti) and replication tools such as SLT. PostNow.ai loads Excel templates through a BAPI or a recorded transaction, validates and simulates every row, and writes SAP's result back beside it.
- Most projects use more than one tool, chosen object by object: the Cockpit for SAP-delivered migration objects, an Excel loader or ETL for the rest.
- LTMC is no longer the cockpit. From S/4HANA 2021 projects are created in the Fiori app Migrate Your Data.
This comparison is for migration leads, SAP functional consultants and IT managers choosing tools for an S/4HANA move or a recurring load: seven tools, two load methods, and how to pick per object. For the full migration process, from load order to cutover, see the SAP data migration guide.
SAP S/4HANA data migration tools compared
PostNow.ai is the Excel-based option in this table: business teams load SAP data from their own spreadsheets through standard SAP interfaces. The others are the classic SAP upload tools (the Migration Cockpit and LSMW), ETL platforms, a replication server and the system conversion tool. Each one answers a different migration question, so read the "best for" column first.
| Tool | Type | Best for | S/4HANA fit | Who runs it |
|---|---|---|---|---|
| PostNow.ai | Excel-based load | Master data and open items kept in Excel, repeated mock loads, objects outside SAP's migration objects, loads after go-live | ECC and S/4HANA; posts through BAPIs or recorded transactions | Business users run published templates; a designer builds each template once |
| SAP S/4HANA Migration Cockpit (Migrate Your Data) | SAP-native loader | Initial load of SAP-delivered migration objects into a new S/4HANA system | S/4HANA only: on-premise, Private Cloud and Public Cloud | Migration consultants; business teams fill the templates |
| LSMW | SAP-native loader (legacy) | Existing ECC loads that already work | Present in S/4HANA on-premise; SAP Note 2287723 does not recommend it for S/4HANA loads | Functional consultants |
| SAP Data Services with Rapid Data Migration content | ETL | Large volumes from many sources that need profiling, cleansing and transformation | Fills the Cockpit's staging tables; Rapid Data Migration content for S/4HANA on-premise | ETL developers |
| SAP Advanced Data Migration and Management by Syniti | ETL and data quality platform | Multi-system migrations run in waves, with data quality reporting and reusable mappings | Positioned for S/4HANA and RISE with SAP; sold by SAP as a solution extension | Data migration specialists |
| SAP Landscape Transformation Replication Server (SLT) | Replication | Continuous, trigger-based replication of tables into SAP HANA and other targets | Replication engine for SAP S/4HANA Central Finance | Basis and technical teams |
| Software Update Manager (SUM) with DMO | System conversion | Converting an existing SAP ERP system to S/4HANA in place, data included | The conversion tool for brownfield moves | Basis teams |
Two load methods sit underneath several of these tools: batch input (BDC) and BAPIs. They are not products, and they are compared further down. If you are retiring an LSMW estate, the LSMW alternative guide maps each LSMW import method to its replacement.
How PostNow.ai loads SAP migration data from Excel
PostNow.ai loads SAP migration data from Excel one object at a time: each template is mapped to a standard BAPI or to a transaction recorded in SHDB. Every row is validated and simulated before it posts, and the SAP document number or error is written beside it, so the template that passed mock load 1 runs unchanged at cutover. Proving each mock load against the source is covered in data migration validation and testing.
- Start from a template. The 75 free SAP Excel upload templates are each mapped to their BAPI, with required fields marked. A designer can also build a template from any BAPI or from a recording.
- Map the legacy extract once. Mapping AI matches the columns of a sample legacy file to the BAPI fields, using only the headers and the BAPI field metadata, and you preview the result before applying it.
- Validate, then Simulate. Validate checks required fields, type, length, date format, allowed values and, optionally, whether the referenced vendor, material or cost centre exists in SAP. Simulate lets SAP check each row: in BAPI mode PostNow.ai rolls the call back instead of committing. The few BAPIs that commit inside SAP, such as billing, are proved on a quality client first.
- Run and read the Run Log. Each row receives its SAP document number or the SAP message. Retry Failed re-posts only the rows that failed, never the posted ones.
- Same template from mock load to cutover. The designer publishes a run-only workbook, and operators run that version in every rehearsal and in the production window.
- Approvals for sensitive loads. An approval policy can hold a template such as GL opening balances until it is approved. The approval is tied to a fingerprint of the data, any later edit invalidates it, and the approver must be someone other than the submitter.
- Reconcile in Excel. Read the loaded records back with the 82 reports of the Report Library, or join tables in the query builder, and compare counts with the source extract.
Designers build and publish templates; operators run them. Each load runs on the operator's own computer under their own SAP login, started by that person, and every run's per-document result is recorded centrally in the admin portal. The migration sequence, the open-items grouping rules and a worked mock load are covered in the SAP data migration guide linked above.
SAP S/4HANA Migration Cockpit (Migrate Your Data)
The SAP S/4HANA Migration Cockpit is SAP's standard tool for the initial load into a new S/4HANA system, and it now runs in the Fiori app Migrate Your Data (F3473). From S/4HANA 2021, transaction LTMC can no longer create migration projects. PostNow.ai works alongside it, posting the objects and loads that sit outside its delivered migration objects.
The cockpit loads migration objects: SAP's definition of one business object, such as a material, a supplier or an open item, with its source structures, target structures and mapping rules. SAP's on-premise documentation describes two approaches SAP Help:
- Migrate data using staging tables. The cockpit generates staging tables per migration object. You fill them from downloadable XML or CSV templates, or with an ETL tool writing into the staging schema.
- Migrate data directly from an SAP system. The cockpit selects the data from a supported SAP source system over RFC, without files.
Either way you prepare, map, simulate and then migrate. Transaction LTMOM, the Migration Object Modeler, adds fields to delivered objects and, on-premise, defines your own objects. SAP's help is explicit about the scope: the cockpit is designed for the initial load in a new implementation and not for keeping systems in sync. SAP Help Migration objects create data; changes to records already in the system go through the normal SAP transactions or a mass-change tool such as PostNow.ai Mass Change. Check the release-specific list of migration objects on SAP Help before you plan, and read our SAP Migration Cockpit guide for templates, simulation and the errors you will meet.
LSMW (Legacy System Migration Workbench)
LSMW (Legacy System Migration Workbench) is the older SAP loader that ECC teams used for years, and it still exists in S/4HANA on-premise. SAP Note 2287723 states that using it to load S/4HANA is not recommended and is at the customer's own risk. SAP Note PostNow.ai is one of the routes teams move recurring LSMW loads to.
LSMW offers four import methods: standard batch or direct input, batch input recording, BAPI and IDoc. The S/4HANA issue is mostly the recordings. Many transactions changed, and the clearest case is vendor and customer master: XK01 and XD01 lead to transaction BP, because the Business Partner is the leading object in S/4HANA, so an ECC recording does not carry over. SAP's note also warns that LSMW can propose interfaces that cannot be used in S/4HANA. Keep LSMW for ECC loads that work today, and plan new S/4HANA work on the Cockpit, a BAPI-based route or an Excel loader. The LSMW guide covers the 14 steps and the status in detail.
SAP Data Services and Rapid Data Migration
SAP Data Services is SAP's ETL product: SAP describes it as one solution for data integration, data quality, data profiling and text data processing, in batch or real time. SAP PostNow.ai and Data Services do different jobs, and a project can use both: Data Services for high-volume pipelines, PostNow.ai for the objects a business team keeps in Excel.
Data Services reads SAP systems through ABAP, IDocs, BAPIs, RFC and SAP extractors, and in S/4HANA projects it is a common way to fill the Migration Cockpit's staging tables. SAP also published Rapid Data Migration to SAP S/4HANA (on-premise edition): pre-built best-practice content for over 40 master and transactional data objects, such as material master, business partner, sales orders and purchase orders. Each object comes with a scenario guide from legacy mapping to upload, and the package covers reconciliation of the loaded data against the source. The solution guide requires SAP Data Services 4.2 SP5 or higher. SAP Support Use Data Services when the work is mostly extraction, cleansing and transformation across many sources, and staff it with ETL developers.
SAP Advanced Data Migration and Management by Syniti
SAP Advanced Data Migration and Management by Syniti is a cloud-based migration platform that SAP sells as a solution extension, on the SAP price list. Syniti PostNow.ai complements platforms of this kind at the business end, where key users load and correct their own objects from Excel.
Syniti describes the product as source- and target-agnostic, with integrated data quality and a self-service interface for fixing escalated errors, dashboards and data quality reports, and mappings that are reused in later migration waves. SAP's product page lists project waves, process areas and migration objects, built-in templates, and data validation with approval workflows. SAP It is positioned for S/4HANA transitions and RISE with SAP. It fits large, multi-system programmes run by a dedicated data migration team, often with partner services.
SLT: replication rather than a migration load
SAP Landscape Transformation Replication Server (SLT) replicates data from SAP or non-SAP sources into SAP HANA and other targets in real time. PostNow.ai and the loaders above create business objects; SLT keeps tables in step between systems, which makes it a different category in a migration plan.
SLT runs an initial load of the selected tables and then captures changes with database triggers on the source tables, recorded in logging tables and replicated in real time, at an interval, at a time of day or on demand. SAP Help SAP positions it as the replication engine for SAP S/4HANA Central Finance. SAP Plan SLT where a target has to follow a source over time. For creating master data and open items through SAP's application logic, use a loader.
SUM and DMO for a system conversion
The Software Update Manager (SUM) converts an existing SAP ERP system to S/4HANA in place, and its database migration option (DMO) also moves a non-HANA database to SAP HANA in the same run. SAP Help PostNow.ai then fits the loads around the conversion: new objects, cleansed master data and corrections after go-live.
In a conversion the data comes with the system, so no migration tool loads master data or open items. You run the Maintenance Planner first, because SUM needs the stack.xml it generates. If the system already runs on SAP HANA, SUM runs without DMO. The choice between a conversion and a new implementation is covered in the ECC to S/4HANA migration guide.
Data migration tools in SAP vs load methods: LSMW, LTMC, BDC and BAPI
PostNow.ai, LSMW and custom ABAP programs all post through the same two SAP load methods: BAPIs, which call a business object's interface, and batch input (BDC), which replays a transaction's screens. LTMC is the name of the old cockpit transaction. Knowing which method a tool uses tells you how it validates and what breaks later.
| Option | How it posts | Checks before posting | Upkeep | S/4HANA status |
|---|---|---|---|---|
| PostNow.ai (BAPI or recorded transaction) | Excel template mapped to a BAPI, or a recording posted by CALL TRANSACTION | Validate on the sheet, then Simulate in SAP; SAP's own checks at Run | The designer adjusts and republishes the template; operators keep running it | ECC and S/4HANA |
| BAPI in a custom program | Calls the business object's interface and commits only after success | The BAPI's own checks, reported in its RETURN messages | An ABAP change and transport for every new field | The first choice wherever a BAPI covers the object |
| BDC (batch input) | Replays the screens of a recorded transaction (SHDB), as a session in SM35 or by CALL TRANSACTION | The same screen checks a user gets | Re-record when the screens change | Works where the transaction is unchanged; XK01 and XD01 recordings move to BP |
| LSMW | A workbench around batch input, direct input, BAPI or IDoc | Those of the method underneath | One project per object, maintained by consultants | Not recommended for S/4HANA loads (SAP Note 2287723) |
| LTMC | The old Web Dynpro Migration Cockpit | Simulation of the migration objects | Projects are rebuilt in the new app | Cannot create projects from S/4HANA 2021; use Migrate Your Data |
The rule most consultants apply: use a BAPI when one exists for the object, and a recording when the field only lives on a screen. The trade-offs are set out in BAPI vs BDC in SAP, and every method, including IDocs and direct input, is compared in SAP data upload methods.
How to choose SAP data migration tools by scenario
PostNow.ai, the Cockpit and the ETL platforms each fit a different shape of work, so choose per object, not per project. Three questions decide most cases: which transition path you are on, whether the load runs once or keeps coming back, and whether business users or IT will run it.
New implementation (greenfield)
A new implementation loads master data and open items into a clean S/4HANA system, so it is the scenario the Migration Cockpit is designed for. Check every object against the release's list of migration objects. Load the covered objects with the Cockpit, through templates or through an ETL tool writing into its staging tables. Load the rest, such as objects outside the list, open items that need grouping rules and Z-fields a BAPI accepts through EXTENSIONIN, with PostNow.ai or a custom program.
Selective data transition
A selective data transition moves chosen data and organisational units into S/4HANA. SAP describes it as an alternative to a system conversion and a new implementation that typically uses specialised tools combined with expert services. SAP Support Ask the provider which objects its tooling carries and which are reloaded. The reloaded objects then follow the greenfield logic above.
System conversion (brownfield)
A system conversion keeps the data: SUM, with DMO when the database moves to HANA, converts the system in place. Loading tools are needed only around it, for new objects, master data cleansed during the project and the corrections after go-live.
One-off or recurring loads
One-off or recurring is the question that changes the answer. A one-off load of a few hundred records needs the simplest safe option. A load that runs every month, or in every mock load, earns a reusable, validated template. The Cockpit creates data for the initial load; recurring loads after go-live go through BAPIs, interfaces or an Excel loader such as PostNow.ai.
Business-user or IT-run
Who runs the load decides how much the tool must protect them. ETL platforms and LSMW are run by specialists. When key users load their own data, look for a tool that checks every row before posting, shows SAP's message per row and separates the person who builds the load from the people who run it.
Best tools for SAP S/4HANA data migration, by scenario
| Scenario | First choice | Add when |
|---|---|---|
| Business team loads its own objects, in every mock load and after go-live | PostNow.ai | The object has a delivered migration object and a large volume: load it in the Cockpit |
| New S/4HANA, standard objects | Migration Cockpit | Volumes or sources need ETL: fill the staging tables with Data Services or Syniti |
| Many legacy systems, heavy cleansing | SAP Data Services or SAP Advanced Data Migration by Syniti | Business-owned objects stay in Excel: PostNow.ai for those |
| ECC target, or an ECC load that works | PostNow.ai or the existing LSMW object | The load moves to S/4HANA: rebuild it on a BAPI |
| Conversion of an existing ERP | SUM with DMO | New objects or cleansed data need loading: Cockpit or PostNow.ai |
| A target must follow a source continuously | SLT | Business objects need creating: a loader |
Selection criteria to weigh
Selection criteria matter when the scenario leaves two candidates. Score each candidate on the six below, weighted for your team.
| Criterion | Ask yourself | How PostNow.ai answers it |
|---|---|---|
| Ease of use | Can the people who own the data run it safely? | Operators run a published, run-only template in Excel |
| Validation | Are errors caught before posting, not after? | Validate on the sheet, then Simulate in SAP |
| Governance | Who may load what, and who approves it? | Designer and operator roles; approvals tied to a data fingerprint |
| Auditability | Is there a record of every load? | Run Log per row, plus a central record of every run in the admin portal |
| Scalability | Will it cope as volume and objects grow? | One template per object, run scope for pilots, Retry Failed for the rest |
| Maintenance | What does it cost to keep it working? | The designer republishes one template; no transport cycle for a mapping change |
Common mistakes when choosing SAP data migration software
Whether or not PostNow.ai is on your shortlist, the same tool-selection mistakes cost projects a mock-load cycle each. Almost every poor tool choice looks fine on the day it is made and shows its cost later, when the load repeats, a screen changes or an auditor asks who loaded what.
- Choosing one tool for the whole project. Coverage differs by object. Check each object against the Cockpit's migration objects and give it its own route.
- Following LTMC tutorials. Blogs written before S/4HANA 2021 describe a cockpit that can no longer create projects. Plan in Migrate Your Data.
- Moving LSMW recordings to S/4HANA unchanged. Vendor and customer maintenance moved to the Business Partner, and SAP Note 2287723 does not recommend LSMW for S/4HANA loads.
- Using a one-off method for a recurring load. The effort repeats every mock load. Build a reusable, validated template once.
- Forgetting the loads after go-live. Migration objects create data. Corrections and new records need a route of their own from day one, as set out in SAP data loads after go-live.
- Treating replication as a load. SLT keeps tables in step; master data and open items are created through a loader.
- Adding governance after the audit question. Decide who builds, who runs and who approves each load before mock load 1, and keep every run's record.
The project-level mistakes behind these, from scope creep to unreconciled tests, are covered in SAP data migration best practices, and the cutover steps are in the SAP migration checklist. Whichever SAP data migration tools you pick, rehearse them in two or three reconciled mock loads before cutover.