ECC 6.0 → SAP® S/4HANA · Brownfield

Move to S/4HANA. Keep what works.

A brownfield conversion takes your ECC system — data, history, configuration and processes — to S/4HANA. We run it together with our partner GOLIVE, with QTS and QCC doing the slow parts.

Plan your conversion See the approach
31 Dec 2027
end of ECC 6.0 mainstream maintenance
100%
of your history moves with you
6 phases
SAP® Activate, end to end
2 partners
Quatelio × GOLIVE, one team
01 — Why brownfield

Three ways to S/4HANA. Most of our customers convert.

There is no single right path. If your processes work and your data history matters, a system conversion is usually the fastest and safest way — and you can still improve processes afterwards.

Brownfield

Our focus
What happens
Your ECC system is converted in place to S/4HANA.
History
All transactional data and configuration stay.
Effort
Lowest disruption; processes improved step by step.
Best when
Your processes work and your history matters.

Greenfield

New build
What happens
A new S/4HANA system, processes redesigned from scratch.
History
Open items and master data only; history stays in the old system.
Effort
Highest change for users and IT.
Best when
You want to start over on SAP® standard.

Selective

Mix
What happens
Chosen data and processes move into a new system shell.
History
You pick which years and company codes move.
Effort
Specialist tooling, often with partners like GOLIVE.
Best when
You merge, split or carve out parts of the business.
02 — Partnership

Quatelio × GOLIVE. One team for your conversion.

We bring the analysis, custom code and analytics know-how. GOLIVE brings the scale and depth of an SAP® Gold Partner. You get one plan and one team.

Quatelio

Readiness, custom code and the data side of the move.

  • Readiness and effort from your system with QTS
  • Custom code adapted with QCC — every change reviewed
  • BW, embedded analytics and reporting after the move
  • Clean core guidance for new developments
GOLIVE

SAP® Gold Partner for transformation, implementation and operations.

  • 300+ employees and 1,000+ SAP® projects
  • Technical conversion, finance and logistics experts
  • Own R&D team for tools and add-ons
  • 24/7 application management after go-live
1,000+
SAP® projects at GOLIVE
200+
GOLIVE customers
24/7
support once you're live
1 plan
one team, one point of contact
03 — How we work

Six phases. SAP® Activate, with our tools built in.

We follow SAP® Activate, the standard method for S/4HANA projects — so your team, SAP® and GOLIVE all speak the same language. QTS and QCC take the slow, manual parts out of it.

  1. 01

    Discover

    Find out what the move means for you: business case, scope and a first estimate.

    QTS readinessSAP® Readiness Check
  2. 02

    Prepare

    Plan the project, set up the team and fix the prerequisites — Unicode, Business Partner (CVI), add-ons.

    QTS effort modelProject plan
  3. 03

    Explore

    Go through simplification items and custom code, decide what to retire, adapt or keep.

    QTS custom codeFit-to-standard
  4. 04

    Realize

    Sandbox and test conversions on copies of production. Adapt code, migrate finance data, test.

    QCC fixesSUM · DMO
  5. 05

    Deploy

    Dress rehearsal, cutover plan and the go-live weekend — with a fallback ready.

    Cutover runbookHypercare
  6. 06

    Run

    Stabilise, then improve: Fiori apps, embedded analytics and clean core extensions.

    GOLIVE AMSEIS analytics
04 — Workstreams

Everything a conversion touches.

Custom code

Find what is used, retire what is not, adapt the rest to the S/4HANA data model.

Simplification items

Every relevant SAP® simplification item checked against your system and turned into a task.

Business Partner (CVI)

Customers and vendors converted to Business Partners before the move — the most common blocker.

Finance data

Universal Journal, new asset accounting and material ledger — migrated and reconciled.

Technical conversion

SUM with DMO: database move to SAP® HANA and conversion in one step, with downtime planned.

Testing & cutover

Test conversions, regression tests and a cutover runbook rehearsed before go-live.

05 — Our tools

Less guessing, less manual work.

QTS Quatelio Transformation Suite Readiness, simplification items, custom code decisions and effort — read from your ECC system, in one view. Explore QTS → QCC Quatelio Clean Code Fixes for ATC findings proposed, explained and applied only after a person approves them. Explore QCC →
FAQ

Good questions to start with

How long does a conversion take?

For most mid-sized systems, 9 to 18 months from first assessment to go-live. QTS gives you an estimate for your system in the first weeks, based on your custom code and simplification items.

What has to be done before the conversion?

Your system must be on Unicode, customers and vendors must be converted to Business Partners (CVI), and add-ons must be checked for S/4HANA compatibility. If you are not yet on SAP® HANA, SUM with DMO moves the database in the same step.

What happens to our custom code?

Usually a large share is no longer used and can be retired. The rest is adapted to the S/4HANA data model. QTS shows which is which; QCC proposes the fixes, and nothing is changed without approval.

Who does what — Quatelio or GOLIVE?

You get one project plan. Quatelio leads readiness, custom code and analytics; GOLIVE brings technical conversion, functional experts and operations after go-live. We agree the exact split with you at the start.

What if we cannot finish before 2027?

Your system keeps running. SAP® offers extended maintenance until 2030 at extra cost, and the Private Edition transition option until 2033. Planning early keeps those options open — and cheaper.

Let's plan your move to S/4HANA.

Start with a readiness check of your ECC system — you get scope, effort and a timeline.

Book a readiness checkContact us