EN
Service

Data migration with quantities and values reconciled after every run.

Mapping, cleansing, and test migrations (mock migrations) for your data migration to SAP S/4HANA. We lead the migration. On request, we also work hands-on in the system, with the SAP S/4HANA Migration Cockpit and, in ECC systems, with LSMW and BAPIs. If a migration has already gone wrong, we manage the correction on request.

Tools
  • SAP S/4HANA Migration Cockpit
  • LSMW and BAPIs for legacy ECC systems
  • Reconciliation reports for quantities and values

Typical situations

Test migrations keep failing.

The error lists get longer with every run instead of shorter, and nobody knows which data belongs to whom. The date for the dress rehearsal is at risk.

Inventory does not match after go-live.

Quantities or values are off, and accounting cannot close the month. Every week of troubleshooting ties up the business and IT.

Data comes from several sources.

Legacy systems, Excel lists, and standalone tools need to flow into one clean target system. Without clear rules, duplicates simply get carried over.

What we take on

From the first mapping to the production load during cutover.

  • List of migration objects with sequence and dependencies
  • Field and value mapping with the business
  • Cleansing rules and owners for each data area
  • On request, hands-on migration in the system, with the SAP S/4HANA Migration Cockpit or, in ECC systems, with LSMW and BAPIs
  • Test migrations with reconciliation of quantities and values
  • Dress rehearsal with timing for the cutover
  • Correction of incorrectly migrated master data and assets

Migration objects and their pitfalls

Most errors in test migrations have known causes. If you address them before the first run, you save weeks of troubleshooting.

ObjectTypical pitfallWhat helps
Suppliers and customers (business partners)Duplicates, plus incomplete addresses and bank detailsDuplicate checks and cleansing rules before the first test migration
Material masterOutdated MRP and purchasing data, inconsistent units of measureOwners for each field in the business, rules for mandatory fields
Purchasing info records and source listsMissing sources of supply, expired pricesComparison with actual purchase orders from recent months
InventoryQuantities and values do not match after migrationReconciliation by plant, storage location, and valuation class, with a reconciliation report
Open purchase ordersPartial deliveries and invoices do not line upA clear cut-off rule, with only the open remaining quantities migrated
Fixed assets (FI-AA)Wrong asset classes, differences in acquisition values and depreciationReconciliation with asset accounting, correction by retirement and re-creation
WBS elements (work breakdown structure, PS)Hierarchies and assignments breakMigration in a defined sequence, structure check after every run

From our project work

Industrial company

Test migrations and cutover in an S/4HANA implementation

Leading the overall project on an interim basis, we were also responsible for cutover management, including the test migrations. In this project, around 70,000 fixed assets and 7,000 material masters were migrated to SAP S/4HANA.

Our role: Cutover management as part of overall project leadership

More project examples

Data migration step by step

Every run ends with a reconciliation report. We move on only when the numbers match.

  1. Objects and rules

    Define the migration objects and work out mapping and cleansing rules with the business.

  2. Test migrations

    Several full runs into a test system, with error analysis and reconciliation after each run.

  3. Dress rehearsal

    One run under cutover conditions, with measured run times.

  4. Production load

    Migration during cutover according to the runbook, with reconciliation before the go/no-go decision.

Starting point

Analysis of the migration objects

If test migrations are coming up or keep failing, the analysis shows what has to happen before the next run and who is responsible. In the initial call, we agree on which objects we look at.

What you get
A report with the object list, sequence and owners, open cleansing rules, and the pitfalls before the next run. After a go-live, it lists the deviations found for each object and proposes a way to correct them.
What we look at
Migration objects with sequence and dependencies, mapping, cleansing rules, and the error logs of recent runs. After a go-live, also the deviations for each object, for example in inventory or fixed assets.
What we need from you
Access to the test system or extracts of the error logs, the existing object list with mapping, and meetings with the business data owners.
How it works
First, we review the object list, mapping, rules, and the logs of previous runs. Then we spot-check the objects in the system, reconcile quantities and values, and talk to the data owners. We discuss the findings in order of priority with the project lead and the business.

What you take away

  • Object list and mappingAll migration objects with sequence, field mapping, and owners.
  • Cleansing rulesWhat gets corrected before migration, by whom, and by when.
  • Reconciliation reportsQuantities and values for each run, documented for the business and auditors.
  • Run-time planMeasured duration of each step from the dress rehearsal, as the basis for the cutover.

Questions about this service

Why not just use LSMW like before?

In SAP S/4HANA, the Migration Cockpit is SAP's designated tool for new implementations. LSMW still fits in ECC systems, for data loads and mass changes. BAPIs, SAP's programming interfaces, help where the Migration Cockpit has no suitable object. LSMW and Migration Cockpit compared

How many test or mock migrations does it take?

Plan for several full runs, until the migration runs error-free and reproducibly. The exact number depends on your data and the scope of objects. The dress rehearsal under cutover conditions is an additional run.

Which data should we cleanse before the migration?

Above all, the master data: duplicate suppliers and customers (both become business partners in S/4HANA), incomplete material masters, outdated purchasing info records, and assets in the wrong classes. Master data cleansing starts in the legacy system, before the first test migration.

Who cleans up the data, you or us?

We work out the rules with the business, and responsibility for the data stays with your data owners. If you want, we also handle the technical side of mass changes together with you, for example with LSMW in ECC systems.

Can you help after a go-live that went wrong?

Yes. We analyze the deviations and design a correction concept, for example retirement and re-creation for incorrectly migrated assets. If you want, we also manage its implementation.

Do you also handle data migrations in other ERP systems?

Yes. Outside SAP and Microsoft Dynamics as well, we manage the data migration in a project leadership role.

Related articles

Initial call: 30 minutes, free of charge.

Tell us about your system landscape and timeline. We will tell you where we see risks and whether we are the right fit.

Initial call Call