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 organizations — especially multi-entity, multi-state or multinational 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: smaller organizations with limited entity count and clean operations; situations where running parallel systems is impossible (e.g., a central HR or payroll system used by all entities); strong executive sponsorship willing to commit to a 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: headquarters or home region first, then expansion to additional states or countries. 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 realization of consolidated benefits. When phased fits: larger organizations with multiple entities, states or geographies; transformational projects where learning matters; risk-averse cultures.
Multi-state and multi-entity rollout patterns
US groups operating across multiple states, entities or countries face specific rollout decisions.
- Largest entity or headquarters first: deploy the flagship US entity first (typically the largest by revenue or headcount), then expand to subsidiaries, divisions and acquired companies. Suits groups where the core US operation dominates revenue.
- Smallest entity first as pilot: deploy a small entity (e.g., a 30-person regional subsidiary) first to learn before tackling the corporate core. Suits groups using the rollout for transformation; the headquarters rollout then becomes the 'mature' deployment that incorporates the lessons learned.
- Geographic or regional clusters: roll out by region, grouping entities that share similar operations, tax footprint and reporting needs — and aligning the sequence with multi-state sales-tax and economic-nexus obligations (post-Wayfair, most states impose a collection obligation once a seller crosses a revenue threshold, commonly $100,000 in in-state sales, with some states set at $500,000).
- Two-tier strategy: large entities on a full-scope ERP, smaller or recently acquired entities on a lighter ERP under the 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.
- Big-bang within entity, phased across entities: each entity goes live big-bang on all modules but the entities sequence across time. A common pattern for multi-entity groups.
- 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.
- Module-first then entity-rollout: a pilot entity goes live on full scope, learns the lessons, then remaining entities roll out one-by-one. Common for complex industrial manufacturers. The choice should reflect the organization's risk tolerance, change-management capacity and entity-similarity profile.
Practical considerations
Five rollout-planning patterns from successful implementations.
- 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.
- Build in dress rehearsals: a minimum of three full cutover rehearsals with realistic data volumes and timing. Each rehearsal reveals issues that would otherwise surface during production cutover.
- 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.
- Budget hyper-care: the first 2-4 weeks after go-live require concentrated support from the implementation team and key users. Plan for 50-100% over-staffing during hyper-care.
- 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 for it explicitly.