How to Achieve a SAP S/4HANA Implementation in 5 Months?

Setting: Why did the SAP ECC system need to be replaced?

The client worked with a highly customized SAP ECC system that was End of Life after years. For a Swiss SME with an established landscape, this meant: the existing solution could not simply be continued; it had to be strategically rebuilt. The setting is typical for companies that have long relied on adaptations and now must move to a clear standard.

The Bern region and the project period from January to July 2025 show how tightly speed and implementation discipline are linked in such endeavors. Especially for an ERP switch of this kind, technology alone is not enough because processes, roles, and data must be reorganized at the same time.

Which solution was chosen and why?

SAP Cloud ERP Public was chosen, formerly SAP S/4HANA Cloud Public Edition. For TeamWork Schweiz, the central aim was not to accommodate as many old edge cases as possible, but to align the solution consistently with the Cloud standard and to adapt only where it clearly supported the customer's USP. This precise focus makes the project relevant for other companies.

The days of huge, complex, costly, and never-ending SAP projects are definitely over.— Stefan Weiss, Sales Director, TeamWork Schweiz AG

ComponentRole in the projectWhy it matteredSAP Activate or Grow FastMethodologyGave the project speed and a clear sequenceDigital Discovery AssessmentPre-selection and system startReplaced the classic specification with a focused process viewFit-to-Standard WorkshopsTechnical clarificationHelped trim processes to standardCloudALMProject controlBundled documents, release management, and implementationData migration and interface designTechnical preparationEnsured a stable transition from the old system

How did the implementation unfold at TeamWork Schweiz concretely?

The implementation followed a standard approach with SAP Activate or Grow Fast, supplemented by the Digital Discovery Assessment. The starter system was available from day 1 and helped run fit-to-standard workshops not in abstract form but directly in the system. Parallel, TeamWork Schweiz built CloudALM so that project management, documents, and release management could be centrally managed.

In our projects, it repeatedly becomes clear that the main work often lies elsewhere than expected: in change management, early data migration, and training of key users and end users. This was confirmed here, all the more so because the key users had less time than planned due to strong order books.

Data preparation was planned early and clearly the responsibility of the client to avoid bottlenecks only becoming visible shortly before go-live.
Key people got to know the system early and were continually involved in working with the new solution.
The change-request process was established from the start and implemented consistently.
Historical data were not simply carried over, but addressed via an archival system.

Which data and processes were migrated?

The migration covered LOB areas Finance, Sales, Manufacturing, Sourcing & Procurement, Supply Chain Management, and IT Management. It included 15,000 material master records, 1,230 business partners, 2,780 bill of materials, 12,700 purchase info records, 12,500 purchase books, and 60 running production orders. This breadth shows it was not a small system switch but a real platform renewal.

5 MonateProjektlaufzeit von Januar bis Juli 2025

TeamWork Schweiz AG

What results did the SAP S/4HANA migration bring?

The result was not just a new system, but noticeably more order in daily operations. Administrative processes became about 20 percent more efficient, purchasing gained clearer structures, order processing became faster and more traceable, and the finance department gained clarity and reliability. At the same time, acceptance grew because the interface was easier for employees to use.

BT-Hydraulik is now more agile with SAP Cloud ERP, more competitive, and has laid the foundation to develop further, technologically and as a company. Contrary to the common belief that cloud migration primarily adds complexity, the opposite was shown here: with a standard focus and consistent support the project became manageable.

What is the key learning for Swiss SMEs?

The project shows that an ERP implementation is not just an IT project but a business transformation project. If you only look at the technology, you underestimate the shift in organization, responsibility, and ways of working. For Swiss SMEs with an established SAP landscape, the ability to focus early and steer cleanly is more decisive than a perfect pre-project.

From our practice we take away three points: allow enough time for fit-to-standard workshops, clearly prioritize the business benefits, and involve business owners early in the project. If these foundations are in place, a switch from SAP ECC to SAP Cloud ERP can be achieved in a short time.

Frequently asked questions

Why was a classic specification not the best start here?

Because the project was designed from the start for speed of implementation and standard alignment. A long specification would have consumed time without increasing substantive value. More important was to review relevant processes early in the system and make decisions quickly.

What was the most challenging aspect of the data migration?

The volume alone was not the only point, but the clean preparation of data and the question of what history belongs in the new system and what to archive. Especially with grown ERP landscapes, this demarcation is often more challenging than the technical migration itself. That’s why the archival system was planned in parallel.

How heavy was the workload for the key users in the project?

Key users had less time than planned during the project because operations ran well. This is a realistic risk in such initiatives, as day-to-day business and ERP implementation directly compete for attention. Therefore early involvement is particularly important.

Who is SAP Cloud ERP particularly suitable for?

Especially suitable for SMEs that want lean processes, a clear standard, and fast execution. If you want to keep many special cases, you must carefully assess whether the target image fits. If you want to modernize and reduce complexity at the same time, this provides a good starting point.

For TeamWork Schweiz, this project was a good example of how quickly a robust switch is possible when focus and discipline come together. For companies with an aging SAP ECC landscape, this means: now is the right time to strategically organize your ERP future and stop delaying.

Planen Sie Ihre SAP S/4HANA- oder Cloud-ERP-ProjektTeamWork Schweiz AG, Bern