Lesson 2 of 6
The SAP toolbox and the ECC deadline
10 min
Listen to this lesson
SAP gives an M&A program several routes, and they are often confused because their names overlap. Some are software you run, some are services SAP delivers, and some are both. This lesson sorts them by what they actually move, then shows how the SAP ECC maintenance dates change the order in which you do things. Product scope and commercial terms change; confirm each one with SAP for your release and contract before you plan on it.
Six routes and what they move
| Route | What it is | Typical M&A use | Watch out for |
|---|---|---|---|
| DMLT services (built on SAP Landscape Transformation) | SAP's Data Management and Landscape Transformation group, formerly SLO; services with software | Company code clone, deletion or carve-out, merge, split and transfer; controlling area merge and split; plant merge and reallocation | Company codes to be merged must sit in the same client; delivery model is a service, so agree it with SAP |
| SAP Business Transformation Center (BTC) | A tool reached through SAP Cloud ALM; analysis apps plus lean selective data transition | Lean SDT from SAP ECC to SAP S/4HANA with time-slice or company code filtering | SAP's 2025 posts say projects can currently be created only for SDT from ECC to S/4HANA |
| Selective data transition engagement | SAP and partner experts using SDT tooling (shell conversion, mix and match) | Merging or splitting systems, CoA harmonization, S/4HANA-to-S/4HANA carve-outs | Targets are private cloud or on-premise, not public edition |
| Central Finance | Replication of financial postings from SAP and non-SAP sources into a central SAP S/4HANA | Day 1 financial integration while operations stay put | Finance only; mappings must be maintained for every source |
| Migration Cockpit (Migrate Your Data, F3473) | SAP's load tool: files, staging tables or direct transfer | Loading an acquired company as new company codes | Direct transfer needs an SAP ERP source; non-SAP targets use files or staging tables |
| Greenfield or two-tier | A new SAP S/4HANA, often public edition (GROW with SAP) | NewCo after a spin-off; subsidiaries with standard processes | For a public edition target, SAP's approach finder offers only new implementation |
The main SAP routes in M&A, as described by SAP in 2025 and 2026. Group Reporting sits beside all of them as the consolidation path.
DMLT is the oldest and broadest. SAP's support site lists its sell, buy and restructure services, covering SAP ECC, SAP S/4HANA and cloud solutions from design through cutover. SAP Help states the key constraint for a company code merge: the company codes must be in the same client. A merge across two systems therefore takes two steps: first a client transfer or migration that puts both company codes in one client, then the merge itself. SAP LT's older master guide (2018) also lists chart of accounts conversion, which allows rename and n:1 merge but no splitting, and a client transfer that explicitly does not merge clients or harmonize business data. Treat that list as dated and check current SAP Notes for scope.
BTC is a newer framework that runs on SAP Cloud ALM. Its Find Transformation Approach app weighs Readiness Check data and a questionnaire and recommends new implementation, selective data transition or system conversion with a percentage fit. Its execution scenario is lean selective data transition from SAP ECC to SAP S/4HANA. No SAP source found in October 2026 shows company code merges or carve-outs as BTC self-service scenarios, so do not plan on that without SAP's confirmation.
For Contoso the source settled it. Alternadores runs a non-SAP legacy ERP, so there was nothing for SDT tooling or direct transfer to select from. Its business partners, products, open items and balances are loaded with the Migration Cockpit using staging tables into company code 1910 in Contoso's system, in W2 Mock 1 to 3 and a W2 dress rehearsal between October 2026 and January 2027. Central Finance had already been evaluated and rejected during Contoso's conversion strategy, and nothing about the acquisition changed that: a finance-only bridge for five months would have cost more than a monthly upload into Group Reporting.
The ECC calendar
If either party runs SAP ECC, the maintenance calendar is part of the deal. SAP's published dates: mainstream maintenance for SAP Business Suite 7 ends at the end of 2027; optional extended maintenance runs to the end of 2030 for a premium of two percentage points; SAP S/4HANA is committed to 2040. Separately, the SAP ERP, private edition, transition option, announced in 2025 for 2031 to 2033, was extended by SAP on October 13, 2026 so that subscriptions may run to December 31, 2035, with prerequisites (see SAP Note 3591251). Systems must be on SAP ERP, private edition, on SAP HANA before the end of 2030. It is a transition vehicle, not a reason to plan an acquisition onto ECC.
Five ways to sequence merge and conversion
| Option | Fits when | Risk | Test cycles |
|---|---|---|---|
| A. Merge on ECC with DMLT, then convert once | Both on ECC; merge urgent; conversion planned inside the window | Two projects; ECC work is technical debt | Two full reconciliation and regression cycles |
| B. Convert the leading ECC, then migrate the target in | Buyer's conversion already under way | Target waits; dual running cost | Conversion cycle, then a migration cycle |
| C. Merge and convert in one SDT program | Both on ECC; CoA and org harmonization wanted | Highest single-event complexity; needs SDT experts | Fewer, larger mock cycles |
| D. Target onto the buyer's existing SAP S/4HANA | Buyer already on S/4HANA | Harmonization inside a live system | Migration mocks plus regression of the buyer's live company codes |
| E. Keep the target on ECC, sunset by 2030 | Low synergy; possible resale | Maintenance cliff; extended maintenance premium | ECC regression for every legal change until sunset |
Contoso is on option D: the buyer's conversion is done, so the target lands in a live SAP S/4HANA. That makes regression of the live company codes 1710 and 1810 as important as reconciling 1910. Option B describes Contoso's calendar too: conversion first in August 2026, then the target in February 2027.
What would you do?
A partner proposes using SAP Business Transformation Center to carve Alternadores' data out of its legacy ERP into company code 1910, "because BTC handles M&A". What is the right response from Contoso's solution architect?
- DMLT services cover company code and controlling area merges, splits, transfers and carve-outs; a merge needs both company codes in one client.
- BTC runs on SAP Cloud ALM and executes lean SDT from ECC to S/4HANA; don't assume more without SAP confirmation.
- The source system narrows the route: non-SAP targets go through the Migration Cockpit, as Alternadores does.
- ECC mainstream maintenance ends in 2027 and extended maintenance in 2030; each extra hop in the sequence adds a test cycle.
Check your understanding · not graded
Lesson check
1. Two company codes in two different SAP ECC systems are to be merged with DMLT. What must happen first?
2. Why does Contoso load Alternadores with the Migration Cockpit rather than SDT tooling?
3. What does a chart of accounts conversion in SAP LT not allow, per SAP's master guide?
4. When does optional extended maintenance for SAP ECC end?
5. Contoso lands the target in its live SAP S/4HANA (option D). Which test need does that add?