SAP replacement

Replacing SAP ECC with Odoo

From requirements catalogue to go-live

SAP ECC: maintenance according to SAP

Chart as text

  • SAP Business Suite 7 maintenance dates: Mainstream maintenance: until end of 2027; Optional extended maintenance (premium): 2028 to end of 2030; Transition option (cloud subscription, private edition): 2031 to end of 2035 (subscription). According to SAP there are no changes for on-premise systems after 2030; the transition option requires SAP ERP, private edition.
Sources: SAP News, 04.02.2020: SAP S/4HANA maintenance 2040, SAP Business Suite 7 · SAP News, 02/2025: SAP ERP, private edition, transition option · SAP News, 08/2025: transition option updates (accessed 8 Nov 2026)

At a glance

  1. Requirements catalogue, also for public tenders.

  2. SAP side: nothing is installed on the SAP system, only data extracts (DART/GoBD).

  3. Odoo side: the app “SAP Migration” is your team's workbench; accounting approves every account mapping.

  4. Waves reconciled against the trial balance, parallel run, go-live.

From SAP ECC to OdooParallel run: monthly reconciliationSAP ECCSAP extractsDART/GoBD, no system accessAccount mappingapproved by accountingWavesconfiguration, master data, documentsReconciliationagainst the trial balanceOdoo 18
From SAP ECC to Odoo Data transfer from SAP extracts in waves, loaded into Odoo 18 over JSON-RPC; during the parallel run it is reconciled against the trial balance every month.

Diagram as text

  1. SAP ECC
  2. SAP extracts (DART/GoBD, no system access)
  3. Account mapping (approved by accounting)
  4. Waves (configuration, master data, documents)
  5. Reconciliation (against the trial balance)
  6. Odoo 18

Connections

  • Parallel run: monthly reconciliation: Waves … Odoo 18

What the check looks like in the Odoo app “SAP Migration”

Nothing is installed on the SAP system. The extracts land in the Odoo app “SAP Migration”, your team's workbench: there it sees every delivered table and column before anything is imported.

  1. 1

    Step 1 · SAP extracts

    Inside the Odoo app: the SAP tables of a delivery by area, each with source table and meaning in plain language.

  2. 2

    Step 2 · Mapping and status

    Each table shows its columns with role and meaning and moves through a status: in preparation, ready to import, imported, reconciled or not imported.

  3. 3

    Step 3 · Column check

    Column check: what SAP says about the column, what it means, what it looks like in the last delivery and what it joins in SAP. Then it is marked checked or not needed.

Screenshots from the Odoo app SAP Migration; delivery data is blurred. Tap the numbers for details, click an image to enlarge.

Simplify-ERP replaces SAP ECC with Odoo: a requirements catalogue (including for public tenders), data transfer from SAP extracts in waves reconciled against the trial balance, a parallel run and go-live. The data transfer uses a dedicated migration tool: every account mapping is a proposal an accountant approves, and a reconciliation report sits between the waves.

Details

How the move runs

  • Requirements catalogue

    The requirements for the new ERP are written up as a catalogue, also as the basis for public tenders.

  • Data transfer in waves

    Data from SAP extracts moves in waves: configuration, master data, documents. A reconciliation report sits between the waves.

  • Parallel run

    During the parallel run the SAP data import is reconciled against the trial balance every month.

  • Tests and go-live

    After tests and reconciliation the company continues its work in Odoo.

The migration tool

The data transfer runs on a dedicated migration tool. It works from SAP extracts; no access to the running SAP system is needed.

  • DART/GoBD extracts

    SAP asset register, business partners and DART/GoBD extracts are transferred into Odoo 18 over JSON-RPC; nothing is installed on the SAP system.

  • Approved account mapping

    Every account mapping is a proposal an accountant approves; unapproved mappings block the load.

  • Findings instead of aborts

    Defective rows of an extract are collected as findings instead of stopping the run.

  • One workspace per migration

    Extracts, settings, mapping proposals and reports are kept together in one workspace.

More on the migration tool

Ongoing data from line-of-business systems

  • Payroll journal

    The monthly payroll journal is imported into Odoo from the SAP text export.

  • Terminals and payment providers

    Sales data from ticket terminals and payment-provider settlements are staged and booked in Odoo.

More on interfaces

Key facts

Source system
SAP ECC
Data source
SAP extracts (DART/GoBD)
Order of waves
Configuration, master data, documents
Check
Reconciliation against the trial balance

FAQ

Frequently asked questions

How does the data get from SAP into Odoo?

From SAP extracts, in waves: configuration first, then master data, then documents. A reconciliation report is produced between the waves, and defective rows are collected as findings instead of stopping the run.

Who decides how SAP accounts map to Odoo accounts?

The accounting team. Every account mapping is a proposal that an accountant approves; mappings that are not approved block the load.

How is it checked that the figures match during the parallel run?

The SAP data import is reconciled against the trial balance every month.

Is the approach suitable for public tenders?

Yes. The requirements catalogue at the start of the project can also serve as the basis for a public tender.

Questions about your project?

Talk your starting point through with us.

Free 30 min -- no obligation