ERP Rollout Planning

The rollout strategy for an ERP implementation determines the project's risk profile, duration, change-management burden and ultimate business outcome. For mid-market and enterprise organisations — especially multi-entity, multi-country groups — rollout planning is one of the highest-leverage decisions in the implementation. The fundamental choice is between big bang (everything goes live simultaneously) and phased rollout (sequential deployment by module, entity, geography or process area).

Big-bang rollout

Big-bang deployment goes live with all modules and all entities simultaneously. Advantages: single go-live event, no extended parallel operation, faster time to consolidated benefits, no integration between old and new systems during transition. Disadvantages: extreme risk concentration — one bad weekend impacts everything; difficult to back out if problems emerge; very heavy change-management load all at once; testing requires comprehensive coverage of every business process; weekend cutover effort can be massive. When big bang fits: small organisations with limited entity count and clean operations; situations where running parallel systems is impossible (e.g., central HR system used by all entities); strong executive sponsorship willing to commit to single decisive transition.

Phased rollout

Phased rollout deploys the ERP incrementally. By module: financials first, then operations, then HR. By entity: pilot entity first, then progressive rollout to remaining entities. By geography: home country first, then international rollout by region. By process area: order-to-cash first, then procure-to-pay, then production. Advantages: lower per-phase risk, learning from earlier phases improves later phases, change-management burden distributed across time, ability to course-correct between phases. Disadvantages: longer total duration, sustained parallel operation between old and new systems, integration effort between systems during transition, slower realisation of consolidated benefits. When phased fits: larger organisations with multiple entities or geographies; transformational projects where learning matters; risk-averse cultures.

Country-rollout patterns

Multi-country DACH groups face specific rollout decisions. (1) Home-country first: deploy Germany first (typically the largest entity), then expand to Austria, Switzerland, and beyond. Suits groups where DACH operations dominate revenue. (2) Smallest country first as pilot: deploy a small country (e.g., 30-employee Swiss subsidiary) first to learn before tackling the German core. Suits groups using the rollout for transformation; the German rollout becomes the 'mature' deployment incorporating learnings. (3) Geographic clusters: rollout by geographic region with shared regulatory and language needs. (4) Two-tier strategy: large entities on full-scope ERP, smaller entities on lighter ERP under two-tier ERP pattern. Each pattern has trade-offs; the right choice depends on operational similarity across entities and the value of consolidation versus local autonomy.

Hybrid rollout patterns

Most real-world ERP rollouts use hybrid patterns. (1) Big-bang within entity, phased across entities: each entity goes live big-bang on all modules but the entities sequence across time. Common pattern for multi-entity groups. (2) Phased within entity, simultaneous across entities: all entities go live on financials simultaneously, then all entities go live on operations later, then HR. Maintains consolidated reporting throughout but spreads risk across phases. (3) Module-first then entity-rollout: pilot entity goes live on full scope, learns lessons, then remaining entities rollout one-by-one. Common for complex industrial manufacturers. The choice should reflect the organisation's risk tolerance, change-management capacity and entity-similarity profile.

Practical considerations

Five rollout-planning patterns from successful implementations. (1) Plan from the cutover weekend backwards: the cutover is the highest-risk single event. Plan its detailed hour-by-hour runbook first, then work backwards to identify prerequisite milestones. (2) Build in dress rehearsals: minimum three full cutover rehearsals with realistic data volumes and timing. Each rehearsal reveals issues that would otherwise surface during production cutover. (3) Define and protect the rollout sequence: scope additions or sequence changes mid-project produce compounding delays. Once the rollout plan is approved, change-control should be rigorous. (4) Budget hyper-care: the first 2-4 weeks after go-live require concentrated support from implementation team and key users. Plan for 50-100% over-staffing during hyper-care. (5) Don't underestimate parallel operation cost: phased rollouts that maintain old and new systems in parallel for 6-12 months absorb significant IT effort. Plan and budget explicitly.

Also consider:SAP Business One · Microsoft Dynamics 365 Business Central

Häufig gestellte Fragen

Is the template effort worthwhile with only three sites?

A template pays off above all when the sites share similar business models, processes and data structures, because the one-off configuration effort is then amortised across every additional site. With only three very different units — say manufacturing, trade and services — a more decentralised approach with site-specific configurations can be more economical, since maintaining the template is itself a permanent project in its own right. As a rough guide: the higher the process similarity and the larger the planned number of sites, the sooner the template approach pays off. What is decisive is an honest upfront analysis of what percentage of processes can actually be standardised globally.

Big-bang go-live or staggered wave planning — which makes more sense for multi-site?

For small, homogeneous organisations a big-bang go-live can be faster and cheaper, because no parallel operation of the old and new systems has to be financed. In larger multi-site and multi-country programmes, however, a big bang across many countries is considered significantly riskier, as scope, data migration and change management would have to be mastered simultaneously across all units. In practice, staggered wave planning with a pilot site therefore usually prevails: it spreads the risk, allows lessons learned between waves and keeps the programme manageable. The price is a longer overall runtime and higher ongoing costs from the temporary parallel operation.

Who should lead a group-wide rollout — corporate IT or the implementation partner?

Responsibility should sit with the group as the owner of the programme, while an external partner contributes the methodological and technical implementation expertise. Critical success factors are a dedicated internal programme lead with a decision-making mandate, a clearly documented requirements document and an implementation partner with proven industry and multi-country experience. A central programme organisation (PMO) and a template board that decides on changes prevent sprawl and template erosion. Supplementary consulting is useful but does not replace internal control of the programme — fully outsourcing programme leadership is considered a common source of failure.

What does a typical multi-site rollout cost and why do budgets so often spiral out of control?

Per site, experience puts the costs at around 0.8 to 2.5 million euros depending on size and complexity, so a programme with about 15 sites realistically lands in the range of 15 to 35 million euros. Licence fees typically account for only a smaller portion; by far the largest share goes to implementation, customising, training and data migration. Industry analyses show that a considerable share of ERP programmes exceed their planned budgets, some substantially. The main causes cited regularly are underestimated staffing needs, creeping scope expansion and unexpected data and integration problems.

How long does a multi-site programme realistically take?

The pilot site typically takes about 12 to 18 months, since this is where the template is built and stabilised. Subsequent waves get faster with growing routine: the first wave of two to three sites often takes 9 to 14 months, later waves typically 4 to 8 months per wave. For an overall programme of around 15 sites, a runtime of roughly four to six years is therefore realistic, provided time for lessons learned and template updates is deliberately planned between waves. Ambitious plans that aim to push such a programme through in a few quarters very frequently fail in practice.

Which localisation and compliance obligations do I need to keep in view per country?

Every multi-country rollout has to distinguish between globally standardised processes and locally mandatory adaptations, for example around taxes, statutory documents, banking standards, languages and date formats. A growing driver is electronic invoicing: in Germany, since 1 January 2025 there has been an obligation in domestic B2B transactions to be able to receive structured e-invoices compliant with the European standard EN 16931 (for example as XRechnung or ZUGFeRD from version 2.0.1), while audit-proof archiving must still satisfy the GoBD and the obligation to issue e-invoices phases in on a staggered schedule until 2028. At EU level, the “VAT in the Digital Age” reform package introduces mandatory structured e-invoices and digital reporting obligations for cross-border intra-Community B2B transactions from July 2030. Since many countries additionally operate their own real-time or near-real-time reporting systems (such as the SdI clearance system in Italy or SII reporting in Spain), local compliance requirements should be gathered early rather than addressed only shortly before each go-live.