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.
Related Topics
Frequently Asked Questions
Is big bang or phased better for mid-market?
Mid-market organisations (50-300 employees) with single primary entity often succeed with big bang; complexity and risk are manageable. Multi-entity mid-market groups (10+ entities) typically benefit from phased rollout by entity. Above 500 employees or with multi-country operations, phased rollout becomes near-universal.
How long should each rollout phase take?
Per-entity rollouts in a phased deployment typically run 3-6 months from kick-off to go-live for similar-template entities. Module-by-module phased rollouts run 6-12 months per module group. Acceleration is possible with template-based approaches; deceleration is common with unique operational requirements.
What about cloud-ERP rolling deployments?
Cloud ERP changes some rollout dynamics: shorter cutover weekends (no infrastructure cutover), faster environment provisioning, easier rollback scenarios. The functional and change-management challenges of rollout remain unchanged regardless of deployment model. Cloud reduces some technical risk but does not eliminate the broader organisational challenge.