UUltraTechGermany

ERP & CRM · remote, across Germany

SAP Data Migration — Proven by Reconciliation, Not by Promise

We migrate master and transaction data from legacy systems into SAP — through the Migrate Your Data Fiori app with staging tables, and through migration objects we model ourselves (LTMOM) where the standard ones do not fit. Every object comes with a reconciliation report: record counts, control totals and field-level differences, signed off before go-live.

In a migration the real question is not whether the data arrives, but whether anyone can demonstrate that it arrived completely and correctly. So we work to a reconciliation you counter-sign: record counts per object, control totals over the value-bearing fields, a field-level sample. Where differences remain they are in the report, with a reason. That is worth more than an assurance nobody can check.

  • Reply the same working day
  • Written quote
  • Anywhere in Germany
  • Payment after handover
Tools
Migrate Your Data, LTMOM
Check
Reconciliation report before go-live
Archive
GoBD, Z3 access
Way of working
Remote
Service area
Anywhere in Germany
Reply
The same working day
Payment
After handover

Use cases

Typical jobs

Usually one of these:

  • Move to S/4HANA

    Take over master data and open items.

  • Replace a legacy system

    Bring data from other systems into SAP.

  • Data clean-up

    Remove duplicates and old records before the move.

  • Archiving

    Keep old data accessible as GoBD requires.

Services

What we take on

  • Extraction from legacy systems: database, CSV export, interface files or direct access
  • Migration built in the Migrate Your Data Fiori app — staging tables or direct transfer
  • Custom migration objects modelled in the Migration Object Modeler (LTMOM) where the standard objects do not fit
  • Mapping and transformation rules per field, documented and versioned
  • Cleansing before load: duplicates, format errors, missing mandatory fields, invalid keys
  • A reconciliation report per migration object: record counts, control totals, field differences, open items
  • Repeated test loads until the reconciliation is clean
  • An archiving concept for the legacy system, aligned to the GoBD access types Z1 to Z3
  • Analysis and tuning of slow reporting: execution plan, indexes, access paths, database statistics

Cost

What does a data migration cost?

A defined analysis comes before the work; then a written quote.

ItemHow it is charged
Inventory of data objectsFixed price in the quote
Migration and test runsTime and materials, estimated in the quote
Working time for analysis and deliveryTime and materials, amount stated in the quote
BillingAt least 1 hour, then in full hours
PaymentAfter the work and handover: SEPA bank transfer, invoice or PayPal

What drives the price

  • Number of migration objects
  • Data quality in the old system
  • Number of test runs

Extra work that only shows up on site is agreed with you first – nothing is charged without your consent.

  • SEPATransfer
  • Invoice
  • PayPal

For your purchasing department

  • Quote

    In writing, up front: labour, material and travel are stated before any work starts.

  • Payment

    After the work and handover: SEPA bank transfer, invoice or PayPal. No prepayment.

  • Contact

    We reply the same working day, in English or German.

  • Supplier details

    UltraTech Germany · Leipziger Straße 40, 10117 Berlin, Germany · VAT ID DE463530263 · Legal notice

Quote

For an accurate quote

A few facts are enough.

  • Source and target system
  • Data objects involved
  • Planned go-live
  • Archiving requirements

Process

How a job runs

  1. 1

    Agree objects and scope

    Which objects come across, which do not, and as at what cut-off date. "Does not come across" is the most consequential decision in the project — and the one that requires an archiving concept.

  2. 2

    Mapping and rules

    One written rule per field: source, target, re-coding, treatment of blanks. That table is later the basis of the reconciliation, and it is the document your business owners can actually review.

  3. 3

    Test loads and reconciliation

    Several test migrations, a reconciliation report after each. We repeat until the differences are either zero or explained and accepted by you.

  4. 4

    Load and sign-off

    The production load follows the sequence that proved itself in test. You get the reconciliation report from the production run for sign-off, plus the documented fallback.

FAQ

Frequently asked questions

Will the migration run with zero downtime?

No, and we do not promise it. Any transaction data load has a cut-off after which the legacy system must not be posted to. What can be planned is how long that window is and whether it falls on a weekend. Anyone promising zero downtime either means something else by it or has not looked at the cut-off yet.

Can we switch the legacy system off after the migration?

Not without an archiving concept. Tax-relevant data is subject to the ten-year retention period, and the tax authority must be given access types Z1 to Z3. The GoBD do allow a relaxation: under the German Federal Ministry of Finance circular of 28 November 2019, margin no. 164, from the sixth year after a system migration Z3 access to that data is sufficient. What that means in your case is a question for your tax adviser — we supply the technical side: extraction, media, and a description of the structures.

Do you still use LSMW?

Not for migrations into S/4HANA. LSMW is on the simplification list and restricted in that context. Transaction LTMC is retired too — deprecated with S/4HANA 2020 and read-only from 2021. The current tool is the Migrate Your Data Fiori app, extended with objects modelled in LTMOM where needed.

Will you be working with our live data?

Where it cannot be avoided, yes — and then under a data processing agreement pursuant to Art. 28 GDPR, either yours or one we provide. Where the work can be done without personal data, we use reduced or anonymised extracts. Whether your processing is lawful overall is not ours to assess; that is your legal determination. We create the technical conditions for it and document them.

We have no migration, just slow reports. Does that count?

Yes, that is a service in its own right. We look at the actual queries — execution plan, indexes, access paths, statistics — and tell you what is causing the runtime. Often it is a missing index, or a report doing its selection in the program instead of in the database.

Sources

Standards and sources

Where a standard or a law gives a number, this page states it with its source. Where sources disagree, we give no number – your specification decides.

Show sources
  1. [1]German Federal Ministry of Finance, letter of 28 Nov 2019 (GoBD), para. 164 – Z3 access from the sixth year after a migration (German)
  2. [2]§ 147 German Fiscal Code (AO) – retention of records (German)

Enquiry about SAP Data Migration and Database Optimisation

  • Free initial consultation
  • Reply the same working day
  • Work by appointment
  • across Germany
Request a quote+49 30 50930365

For an accurate quote

  • Source and target system
  • Data objects involved
  • Planned go-live
  • Archiving requirements
  • SEPATransfer
  • Invoice
  • PayPal