How can an SAP S/4HANA rollout succeed in a few months?

5 min read
MaxQ editorial team
Independent guide · editorially reviewed
Last checked: September 25, 2026

Why ECC customers need to decide now

Many Swiss SMEs have run SAP ECC for years, enriching it over time with custom developments and special logic. According to the maintenance roadmap communicated by SAP, mainstream maintenance for SAP ECC 6.0 ends at the end of 2027, with paid extended maintenance available until the end of 2030. Check the terms that apply to your contract directly with SAP or your partner.

The question is therefore no longer whether to switch, but how. The main options are a technical conversion of the existing system, a fresh implementation in a private environment, or a move to the public cloud with a strict standard. The latter promises the shortest project times but demands a willingness to give up familiar workarounds.

An ERP rollout is a transformation project for the whole company, not merely an IT project.

A documented example from the Bern region

A project documented by the integration partner TeamWork Schweiz AG shows what such a switch can look like in practice. Between January and July 2025, an industrial SME from the Bern region replaced its heavily customised ECC system with SAP Cloud ERP Public, formerly SAP S/4HANA Cloud Public Edition. The guiding principle was to use the cloud standard consistently and to adapt only where it supported a clear differentiator of the business.

Data migrated according to the project reportVolume
Material master records15'000
Business partners1'230
Bills of materials2'780
Purchasing info records12'700
Source list entries12'500
Open production orders60

The scope covered finance, sales, manufacturing, procurement, supply chain and IT management. According to the project report, administrative processes became around 20 percent more efficient, purchasing gained clearer structures and order processing became easier to trace. Such figures come from a single project and cannot simply be transferred to other companies.

The building blocks of a fast approach

Building blockFunctionBenefit for speed
SAP Activate and the GROW offeringStandardised methodologyClear phases, proven sequence
Digital Discovery AssessmentStructured upfront analysisReplaces a lengthy specification with a focused process view
Starter system from day oneWorking environment for workshopsDiscussions on the real system instead of slides
Fit-to-standard workshopsMatching processes to the standardEarly decisions, few special requests
SAP Cloud ALMProject managementDocuments, tests and releases in one place

The key lever is less the method than the mindset: every deviation from the standard must be justified. Carrying old exceptions over unexamined wastes the time advantage of the public cloud and imports complexity into the new system.

Where the real work lies

The experience from this project matches many similar ones: the main burden is not the technology but change management, data preparation and training key users and end users. In the case described, key users had less time than planned because business was good, a realistic risk you should plan for from the outset.

  • Start data preparation early and assign clear ownership to the business, so bottlenecks do not surface just before go-live.
  • Do not simply migrate historical data; handle it through an archiving system and transfer only what is needed.
  • Let key users work on the system early and repeatedly, and relieve them specifically in their daily work.
  • Establish a binding change request process from the start and apply it consistently.
  • Design and test interfaces to third-party systems early.

Typical mistake

Daily business and the rollout compete for the same people. Without formal release from duties or deputies, testing and data cleansing slip, and that is exactly where delays arise.

Is the public cloud right for your company?

A switch within a few months is not a promise but the result of favourable conditions. Assess honestly how many of the following points apply to your company.

  • Executive management actively supports standardisation and decides quickly.
  • Your core processes largely follow common industry practice.
  • You can name the few specifics that truly differentiate your business.
  • Business owners join the project early and with a time budget.
  • You accept regular release cycles controlled by the vendor.

If several points do not apply, for instance because highly individual manufacturing or pricing logic is indispensable, a private cloud or a conversion may be the better fit despite a longer timeline. Seek several independent assessments and ask to see reference projects of comparable size.

Frequently asked questions

Is a traditional requirements specification unnecessary?
In a cloud project close to standard, a lengthy specification often ties up time without adding much value. It is more effective to test the relevant processes on the system early and document the deviations. Interface and compliance requirements should still be recorded in writing.
What is the hardest part of data migration?
Less the volume than the quality and the scoping: which data belongs in the new system and which in the archive? In grown landscapes, this decision is often more demanding than the technical transfer.
How much time do key users need to set aside?
It depends on scope and role. Plan their involvement concretely for the whole project, including workshops, testing and training, and agree binding relief from their daily duties.
Who is SAP Cloud ERP Public best suited for?
SMEs looking for lean processes, a clear standard and fast implementation. Companies that must keep many special cases should examine the target design carefully before choosing the public cloud.
Is a 20 percent efficiency gain realistic?
The figure comes from a single project report. The benefit in your company depends on your starting point, process discipline and employee acceptance. Define your own measurable targets before the project starts.

Focusing early, involving business owners and allowing enough time for fit-to-standard workshops creates the best conditions for a fast and stable switch.