SAP Implementation

SAP S/4HANA implementation without blowing the deadline or the budget

We run SAP projects from blueprint to go-live using SAP Activate. From the proposal onwards you know which approach fits your case — Greenfield, Brownfield or selective transition — and what each one costs in time and money.

Talk to a specialist WhatsApp

What's included

Readiness assessment before signing the contract
Scope and milestones defined per SAP Activate phase
Senior team assigned, no trainees on the client
Cutover planned with a rollback plan

Is the 2027 deadline on your radar yet?

SAP ends mainstream maintenance for Business Suite 7 — which includes ECC 6.0 — on 31 December 2027. There is a paid extended maintenance window until 2030, but it costs more and does not solve the underlying problem: your ERP freezes while the market moves.

In practice, companies still running ECC need to choose a migration route now. A mid-sized S/4HANA project takes 9 to 18 months. Whoever leaves the decision to 2027 will hire consultancy at peak demand, at peak demand prices.

Our work starts before the project: we run an assessment that shows the real size of your technical debt — customisations, incompatible add-ons, master data quality — and turns it into three migration scenarios with timeline and cost.

Greenfield, Brownfield or selective transition?

All three routes lead to S/4HANA. What changes is what you carry along — and what that costs in time, risk and money.

	Greenfield	Brownfield	Selective Data Transition
What it is	A new implementation, processes redesigned from scratch	Technical conversion of the current system, keeping customisations and history	Selective migration: brings only the companies, processes or years of data that matter
Right when	Current processes are the bottleneck, or there is no SAP today	Processes work and the goal is to modernise the platform	There is plenty worth keeping and plenty worth leaving behind
Typical timeline	12 to 24 months	8 to 14 months	10 to 18 months
Main risk	Resistance to change and rewriting processes	Inheriting customisation and bad data nobody wanted to clean	Complexity of the data selection rules
Impact on operations	High: almost everything changes for the end user	Low to medium: the screen changes, the process usually does not	Medium: varies by area depending on the selection

How we run the project

We follow SAP Activate. Each phase ends with a reviewed deliverable and formal sign-off — you are never left wondering where the project stands.

Discover — readiness assessment

We inventory customisations, add-ons and integrations, run the SAP Readiness Check and measure master data quality. Output: a report with the three possible routes, timeline and investment range.

Prepare — project foundation

Team, governance, environments and project plan. We define who decides what and how fast — the biggest cause of delay in SAP projects is a decision waiting for approval.

Explore — fit-to-standard

Workshops per process comparing your operation to the S/4HANA standard. Every gap becomes a backlog item with an explicit decision: adopt the standard, configure or develop. Customisation only goes in with a business justification.

Realize — build and test

Configuration, ABAP/Fiori development, data migration and integrated test cycles. We run at least two full test cycles and one acceptance test with key users.

Deploy — cutover and go-live

A timed cutover rehearsal, a documented rollback plan and a switchover window agreed with operations. Nobody flips a system in the dark.

Run — stabilisation and handover to AMS

Hypercare with the same project team, then a structured handover to support — ours or your internal team, with documentation delivered.

What we deliver beyond a system that runs

An SAP project that ends with nothing but a working system leaves debt behind.

Living documentation

Process designs, role matrix, functional and technical specifications for everything built. Delivered in editable format, not as a dead PDF.

Your team trained

Key users trained during the project, not in a rushed session the week of go-live. Whoever operates it needs to understand it before the switch.

Segregation of duties from day one

An SoD matrix designed together with the roles, avoiding the classic rework of discovering access conflicts at the first audit.

Adoption metrics

We measure real usage per transaction after go-live. A system nobody uses is a failed project, even if it landed on time.

Frequently asked questions

How much does an SAP S/4HANA implementation cost?

The investment varies mainly with the number of modules, the number of users, the volume of customisations to migrate and the route chosen. A controlled-scope Brownfield costs far less than a multi-country Greenfield. That is why our proposal always comes after the assessment: pricing SAP without knowing the legacy is guesswork. The assessment itself is quick and produces numbers you can defend to your board.

How long does an SAP implementation project take?

A single-scope Brownfield usually lands between 8 and 14 months. A mid-sized Greenfield, between 12 and 24 months. A roll-out to an additional site, with the template ready, can take 3 to 5 months. The factor that moves these numbers most is not technical: it is how fast the client decides in the fit-to-standard workshops.

Do I have to move to the cloud along with S/4HANA?

Not necessarily. S/4HANA runs on-premise, in private cloud (including RISE with SAP) and in public cloud. The choice depends on your appetite for customisation, the regulatory requirements of your sector and the cost model your company prefers. We assess this without infrastructure-vendor bias.

What happens to the customisations we have in ECC today?

They go through triage. On average, a meaningful share of the customisations in an old ECC either is no longer used or has become standard functionality in S/4HANA. The assessment inventory classifies each object as keep, adapt, replace with standard or discard — and that usually reduces migration effort significantly.

Do you take on a project that already started and stalled?

Yes, and it is not rare. In those cases we first make an independent assessment of the real state of the project: what is genuinely done, what is done on paper and what has to be redone. Only then do we discuss a recovery plan and timeline.

Find out which migration route fits your SAP

A readiness assessment returns three scenarios with timeline and investment range. No commitment to hire the project.

Solicitar diagnóstico gratuito Chat on WhatsApp