
Bedding House moves from SAP ECC to SAP Cloud ERP: Nightmare or dream?
Bedding House went live in October with SAP S/4HANA Cloud Public Edition after a fourteen-month ERP implementation. The move from the outdated SAP ECC to SAP Cloud ERP went according to plan and within budget, with a limited number of issues that had no impact on the invoice and goods flows. Scheer Nederland was the implementation partner. Below you can read how the project was approached.
Why did Bedding House move from SAP ECC to SAP Cloud ERP?
Bedding House moved because the ECC system was technically outdated and could no longer support its growth plans. The family business designs and distributes bed and bath textiles in more than 30 countries and wants to grow with new customers, international expansion, and more online sales. That requires a platform that works with other sales channels, different pricing agreements, and different delivery forms.
The existing system had a lot of custom code and workarounds. That is a familiar picture at organizations that have run on SAP ECC for years: every change makes the next one harder. A new ERP platform therefore had to do more than take over the current processes; it also had to leave room for innovation. The choice fell on SAP S/4HANA Cloud Public Edition, a standard solution in which processes are set up according to best practices instead of through custom code.
You can read more about the background of this move in our article on the move from SAP ECC to SAP S/4HANA Cloud Public Edition.
How did the ERP implementation go at Bedding House?
The ERP implementation ran in sprints, with design first and the build only afterward. The team went through fourteen months, six sprints, and three migration runs before go-live. The project team consisted of about 25 people, spread over Bedding House, Scheer IDS and Skopos.
Skopos guided Bedding House in sharpening its future vision, defining the processes, and selecting the package and partner. That led to the choice of Scheer IDS as implementation partner. During the implementation, Skopos stayed involved for project guidance and project management.
Together with the key users of Bedding House, Scheer IDS translated the process choices into a setup based on the SAP standard. That is the core of our SAP S/4HANA Cloud implementation: the standard is the starting point, and deviations must prove themselves.
What was the role of the key users?
The key users brought in the knowledge of day-to-day practice. Together with Scheer IDS, they assessed which process choices fit how Bedding House works and which choices better fit the SAP standard. This demanded a lot from these employees, because they carried the project on top of their daily work.
Why was the data migration so intensive?
The data migration turned out to be the heaviest part of the project. Three migration runs made it possible to check and adjust the data step by step before the actual cut-over. For organizations with a long ECC history, this deserves early attention, because the quality of the master data directly affects the first weeks after go-live.
How was the integration landscape renewed?
The integration landscape was renewed completely, with around forty interfaces. These include connections with customers, a WMS (warehouse management system) and a PIM (product information management system). For a company that delivers through different channels in many countries, these interfaces are just as decisive for the result as the ERP system itself.
Do you want to know what options SAP Cloud ERP offers for extension and integration? Then take a look at our page on extension, innovation and integration.
Which choices kept the project manageable?
Three choices helped the team stay on course: clear decisions, a defined first scope, and designing before building. This combination prevents a project from being extended during the build with wishes that were not discussed in the design.
- Clear choices: decisions were taken and recorded, so the team did not have to keep going back to earlier discussions.
- A defined first scope: what belongs in the first go-live and what can come later was clear in advance.
- Design first, then build: the processes were worked out in the SAP standard before the set-up started.
Besides the approach, management involvement, the chemistry between the people, and cohesion within the project team were important success factors. A good Discovery Assessment at the start of a program helps clarify these choices and the scope in advance.
How did the Bedding House go-live go?
The go-live went smoothly, with a limited number of issues that had no impact on the invoice and goods flows. For the transition, the project team came together in a central control room. After three days, the War Room was converted into a Control Room, shifting the focus from the transition to day-to-day steering.
To keep deliveries to customers going, Bedding House agreed to buffer stock in advance and chose a phased start-up. The project was delivered on schedule and within budget. The first successful month-end close followed in early November, an important moment because it showed whether the financial processes close in the new system.
Is the move a nightmare or a dream?
The move is neither a nightmare nor a dream, but a project that stays manageable with good preparation. It demanded a lot from the employees involved, especially during the data migration, and it succeeded thanks to everyone's effort and cooperation. A dream without effort does not exist in a large ERP implementation; it is not a nightmare either when scope, design and planning are in order.
The limits of this example are clear. Every organization has its own processes, data, and degree of customization. Beddinghouse's approach shows which choices help, but it does not replace your own analysis. You can find more examples in our customer references.
What happens after the go-live?
After the go-live, the focus is on further improvement. Bedding House wants to use new SAP functionality and AI, and work with dashboards that show where action is needed. The aim is better decisions and doing more with the same staffing.
With SAP Cloud ERP, new functions become available through release updates, so the system keeps growing after the go-live. How we support organizations with that is described in our managed services for SAP S/4HANA Cloud.
What can you learn from this project for your own move?
Start with a clear scope, design before you build, and plan the data migration as its own workstream. Take into account the load on your employees, because key users carry the project on top of their daily work. Set up the system on the SAP standard so it stays manageable after go-live.
Do you want to map out the whole path from ECC to Cloud ERP? On our page about the transition to SAP Cloud ERP we describe the steps.
Frequently asked questions
+How long did the Beddinghouse program take?
The whole programme took about two years. The implementation itself took fourteen months, spread over six sprints and three migration runs.
+Which SAP solution does Bedding House use now?
Beddinghouse has been running on SAP S/4HANA Cloud Public Edition since October. The previous system was SAP ECC, which was technically outdated and had a lot of custom code and workarounds.
+How many interfaces were realized?
The renewed integration landscape has around forty interfaces, including connections with customers, a WMS and a PIM.
+How did deliveries keep going during the go-live?
Beddinghouse agreed buffer stock in advance and chose a phased start-up. As a result, deliveries to customers kept running.
+What did Scheer IDS do in this project?
Scheer IDS guided Bedding House on its future ERP vision, process design, and best-practice selection. It also stayed involved during the implementation for project guidance and project management.
+What is the next step after the go-live?
Beddinghouse is focusing on making use of new SAP functionality and AI, and on dashboards that show where action is needed.
In short: a well-prepared move from SAP ECC to SAP Cloud ERP is manageable, provided scope, design, and cooperation are in order beforehand.







