As of: 19 June 2026 · Reading time: 4 min
Key takeaways
- The introduction of a new ERP system (Enterprise Resource Planning) is a marathon, not a sprint.
- Many companies focus intensively on the selection and implementation of the software, ...
The introduction of a new ERP system (Enterprise Resource Planning) is a marathon, not a sprint. Many companies focus intensively on the selection and implementation of the software, ...
“Good software is not an accident—it comes from a structured development process with clear quality standards.”
– Björn Groenewold, Managing Director, Groenewold IT Solutions
The introduction of a new ERP system (Enterprise Resource Planning) is a marathon, not a sprint. Many companies focus intensively on the selection and rollout of the software.
However, the true success is only shown in the stage of the Go Live and subsequent follow-up.
These critical sections decide whether the theoretical benefits of the system are also realized in practice.
In this post, we will focus on what goes on with the Go-Live and why professional follow-up is essential for the long-term success of your ERP introduction in the middle class.
The Go Live Phase: The decisive moment
The introduction of a new ERP system (Enterprise Resource Planning) is a marathon, not a sprint.
When planning ERP introduction: Go-Live and follow-up from idea to delivery, API & Integration Projects, Cost Calculator: API Development, Solution: Integration Chaos sowie RPA vs. API Integration offer practical next steps on our site.
The Go-Live is the moment when the new ERP system merges into productive operation and replaces the old systems.
It is the highlight of months-long planning, configuration and training. Careful preparation is the key here to minimise malfunctions in the operation and to ensure acceptance by employees.
What does go live mean?
"Go-Live" means the commissioning of a new IT system.
In the context of an ERP introduction, this means that all business processes that were previously handled in old systems or manually now run over the new ERP system.
Data are migrated, user accounts are active and employees begin to perform their daily tasks in the new system.
This transition is often associated with a certain tension, since here the theory meets the practice.
The last mile: Important steps before start
To ensure a smooth transition, a detailed checklist is essential for the days and hours before the go level.
This "cutover planning" ensures that no critical tasks are overlooked.
- Task
- Responsible
- Status
- Final data migration and verification.
- IT team / DB admin.
- ☐
- Deactivation of old systems
- IT team
- ☐
- Activation of all user accounts and permissions.
- System administrator
- ☐
- Final system tests and function checks.
- Key users / project team.
- ☐
- Establishing a support and escalation plan.
- Project management / IT management.
- ☐
- Communication to all employees and stakeholders.
- Internal communication
- ☐
This list serves as an example and needs to be individually adapted to the respective project.
A thorough planning of these last steps minimizes the risk of unloved surprises on the day of the Go Live.
After the Go-Live is before the Go-Live: The follow-up phase
Short: Many projects consider the Go-Live to be the completion of the ERP introduction.
Many projects consider the Go-Live to be the completion of the ERP introduction. That's a truggle. The actual work often begins only now. The post-care or stabilization phase.
This typically comprises the first 30 to 90 days after the start, is crucial for the sustainable anchoring of the system in the company.
Why follow-up so
References and further reading
The following separate references complement the topics in this article:
- Bitkom – German digital industry association.
- German Federal Office for Information Security (BSI).
- European Commission – Digital strategy.
- MDN Web Docs (Mozilla)
- W3C – World Wide Web Consortium.
"DevOps is less about tools and more about shared ownership of quality and release discipline."
— Björn Groenewold, Managing Director, Groenewold IT Solutions
Frequently Asked Questions (FAQ)
What is this article about: “ERP introduction: Go-Live and follow-up”?
Here we cover ERP introduction: Go-Live and follow-up — focused on architecture, process, and business outcomes. In short.
The introduction of a new ERP system (Enterprise Resource Planning) is a marathon, not a sprint.
Many companies focus intensively on the selection and rollout of the software, ...
Who benefits most from the content described here?
Typical readers are business and IT leaders in Software development who want to secure quality, security, and ease of upkeep over the long term.
How does this topic fit into an IT or digital strategy?
In a digital strategy, prioritize stable core processes first, then extensions. See also professional software development and consulting.
For multi-system landscapes, IT consulting and architecture helps align vendors and internal teams.
What are sensible next steps if we need support?
If you need support with design, delivery, or modernization: schedule an appointment or outline your project via contact.
About the author

Managing Director of Groenewold IT Solutions GmbH and Hyperspace GmbH
Since 2009 Björn Groenewold has been developing software solutions for the mid-market. He is Managing Director of Groenewold IT Solutions GmbH (founded 2010) and Hyperspace GmbH. As founder of Groenewold IT Solutions he has successfully supported more than 250 projects – from legacy modernisation to AI integration.
Blog recommendations
Related articles
These posts might also interest you.

How to connect your company systems for sustainable success
In today's business world marked by digital transformation, data is the undisputed elixir of life of every company. They are the basis for innovation, efficiency and sound...

Venture Capital for Software Development: Opportunities and Risks
In the dynamic world of software development, access to capital is often the decisive factor that decides on the success or failure of an innovative start-up. One of the famous...

Software funding in the middle class: practical examples and success factors
Digitization poses major challenges to small and medium-sized enterprises (SMEs), but also offers immense opportunities. One of the central hurdles is often Software Financing. How...
Free download
Checklist: 10 questions before software development
Key points before you start: budget, timeline, and requirements.
Get the checklist in a consultationRelevant next steps
Related services & solutions
Based on this article's topic, these pages are often the most useful next steps.
Related services
Related solutions
Related comparison
Practical next steps after ERP introduction: Go-Live and follow-up
ERP introduction: Go-Live and follow-up addresses a practical choice for product and IT teams. Start with one clear goal: select and adapt an ERP setup around real workflows instead of generic feature lists.
Check the current process, the data involved, and the result users need. Then record the main risks and define a small first step. This keeps the decision easy to review and gives your team a shared basis.
For implementation support, our Odoo ERP consulting and development connects the article's guidance with architecture, delivery, and stable operations. Engineering and project ownership stay with our team in Leer, Germany.
This post belongs to Software development. Browse the related Software development articles or use the English software blog for other topics.
When budget is the next question, the software cost calculators provide planning ranges. The IT glossary explains key terms, while in-depth technology guides cover wider decisions.
If the topic affects a live project, book a technical consultation or send the context through our project contact form. We usually reply within one working day.
