ERP Implementation Roadmap Template: 6 Phases

9 min read ยท 2026-10-28

An ERP implementation roadmap is a one page plan that takes a company from signed scope to a stable new system in six phases: plan and mobilize, design, build and migrate data, test and train, go live, then stabilize. The template below takes about 26 weeks to go live. It fits a focused rollout of finance plus one or two operational areas in a single entity, and it ends with reviews at 30, 90 and 180 days.

It is written for finance and operations leaders, project managers, IT leads and implementation partners who need one plan everyone can read. Each phase comes with its duration, its concrete steps and a milestone you can check. The guide also gives the owner and exit gate for every phase, compares big bang, wave and module rollouts, and walks through two illustrative examples. It ends with the Excel columns for the detailed plan and a way to present the roadmap to a steering committee.

The roadmap at a glance

Goal: Go live on the new ERP with clean data, trained users and a completed first month end close, then show the gains within 180 days. Duration: About 26 weeks to go live, then reviews at 30, 90 and 180 days

  1. Plan and Mobilize (Weeks 1 to 3)

    Lock scope, governance and the team before anyone configures anything.

    • Write a signed scope document that lists the modules, legal entities, sites and integrations in scope and out of scope.
    • Name an executive sponsor, a project manager and one process owner per module.
    • Set up change control, a decision log and a weekly status report.
    • Backfill the daily work of key users so they can give the project real time.

    Milestone: The steering committee approves the project charter, the scope and the governance model.

  2. Design (Weeks 4 to 8)

    Decide how each business process will run in the new system.

    • Run fit gap workshops for record to report, procure to pay and order to cash.
    • Design the chart of accounts, dimensions and reporting structure with finance.
    • Start from standard functionality and require a business case for every customization.
    • Specify integrations with CRM, ecommerce, payroll and banking.
    • Define the data migration scope, the cleansing rules and the balances that move at cutover.

    Milestone: Process owners sign the solution design for every process area.

  3. Build and Migrate (Weeks 9 to 15)

    Configure the system, build the integrations and rehearse the data load.

    • Configure modules in short sprints, with a demo to process owners at the end of each one.
    • Build and unit test the integrations and any approved extensions.
    • Clean master data for customers, vendors, items and bills of materials.
    • Run at least two mock migrations and reconcile each one with finance.

    Milestone: A mock migration loads into the test environment and reconciles to source balances.

  4. Test and Train (Weeks 16 to 21)

    Prove that full processes work and prepare every user for day one.

    • Run system integration testing on complete business scenarios.
    • Have key users write user acceptance testing (UAT) scripts from real transactions, then run them.
    • Fix every critical defect before the go or no go meeting.
    • Deliver role based training on the configured system, with local procedures.
    • Finalize the cutover plan with timings, owners and rollback criteria.

    Milestone: UAT is signed off and the go or no go checklist passes at steering review.

  5. Go Live and Hypercare (Weeks 22 to 26)

    Switch over safely and keep operations running through the first close.

    • Freeze legacy transactions and run the final data migration.
    • Validate opening balances and open orders with finance before releasing the system.
    • Staff a hypercare desk with key users and partner consultants.
    • Track daily issue counts, integration errors and transaction backlogs.

    Milestone: The first month end close is completed in the new ERP.

  6. Stabilize and Optimize (Days 30 to 180 after go live)

    Turn a working system into one the business relies on.

    • At day 30, review open issues, the workarounds still in use and how long the close took.
    • At day 90, compare process indicators with the baseline captured during design.
    • At day 180, decide what goes into the next release: deferred modules, reports, automation.
    • Hand hypercare over to normal support with a named system owner.

    Milestone: The day 180 review approves the next release backlog and the legacy system is retired.

Owners, Deliverables and Exit Gates for Each Phase

An ERP roadmap is not the ERP project plan. The roadmap is the one page view the sponsor and steering committee use to make decisions. The project plan is the detailed task list the team works from. For each phase, the roadmap needs three things: who owns it, what it delivers and the condition for moving on.

Put a person's name on each line, not a department. A gate with a named owner gets a clear yes or no at steering review. A gate owned by "IT" or "Finance" tends to slip without anyone deciding.

  • Plan and mobilize: owned by the project manager with the sponsor. It delivers the charter and scope. Exit gate: every process owner is named and their time is freed.
  • Design: owned by the process owners. It delivers a signed design per process. Exit gate: the customization list is approved through change control.
  • Build and migrate: owned by the partner lead and the data migration lead. It delivers a configured test system. Exit gate: the second mock migration reconciles.
  • Test and train: owned by the test lead and key users. It delivers signed UAT and trained users. Exit gate: no open critical defects.
  • Go live and hypercare: owned by the project manager. Exit gate: the first close is done and normal support can handle the issue volume.
  • Stabilize: owned by the system owner. Exit gate: the day 180 review.

Big Bang, Waves or Modules: Choosing the Cutover

The way you switch over shapes the whole roadmap, so decide it during design. It changes how many migrations you run, how long the old and new systems run side by side, and how much temporary integration you build.

  • Big bang: every module and site switches on the same date. There is one cutover and no temporary link between old and new, but all the risk falls on one weekend. It suits a single entity with simple operations.
  • Waves by site or entity: the same design rolls out one location at a time. The first wave acts as the pilot and later waves reuse what it taught you. The cost is a longer period of reporting across two systems.
  • By module: finance first, then inventory, then manufacturing. Each step is smaller, but every module needs a temporary interface with the legacy system until the next one moves.

Illustrative Examples: A Small Manufacturer and a Multi Entity Group

In this hypothetical example, a small manufacturer runs an entry level accounting package, spreadsheets for inventory and email for purchase approvals. It picks a cloud ERP for financials, inventory and purchasing and goes big bang on the 26 week template. Suppose the design workshops find that each warehouse numbers items differently. Data cleansing then becomes the critical path from week four. Go live is set for the start of a quiet month, and production planning moves to a second release.

In a second hypothetical example, a group with three entities in two countries uses waves instead. The home entity goes first on the same template, and its signed design becomes the group standard. Later waves reuse that design and focus on local tax, language, banking and data. The roadmap shows each wave as its own row, with the same phases and gates.

How to Set the Timeline and Budget

Duration and cost depend on your scope, the number of entities, customizations, integrations and the state of your data. A general range will not tell you much about your own project. Ask your partner for a scoped estimate built on your signed scope. Give training, data cleansing and hypercare their own budget lines so they do not get squeezed later.

Set the go live date formally at two checkpoints: after design sign off and after the second mock migration. At those moments you have real evidence about complexity. Moving the date then costs far less than finding out in week 25 that the data or the testing is not ready.

ERP Implementation Plan Template in Excel: The Columns to Copy

The detailed plan behind the roadmap works well in a spreadsheet. Use one row per task or deliverable, with the columns listed below.

Add four tabs: the signed scope, a risk register, a cutover runbook with hour by hour steps, and the post go live indicators for days 30, 90 and 180. Keep the spreadsheet as the working plan and the roadmap as the summary on top, so the two always tell the same story.

  • Phase, workstream and task or deliverable
  • Owner and backup owner
  • Start week, end week and dependency
  • Exit criterion and status
  • Risk and mitigation

Risks to Plan For

Write down a fallback for each risk before it happens.

  • Data quality: start cleansing in design and set a rule for records that cannot be fixed in time.
  • Scope creep: send every new request through change control with an effort estimate.
  • Key user availability: backfill their jobs and escalate missed workshops to the sponsor.
  • Adoption: appoint super users per department and measure workarounds at day 30.

How to Present the Roadmap to Leadership

For the steering committee, show the phases as columns, the workstreams as swimlanes and the milestones as markers. Give slipped milestones a different color instead of quietly moving dates. End each review with the two or three decisions you need, because a roadmap that asks for nothing gets nodded through.

Common mistakes to avoid

  • Customizing the ERP to copy old processes makes every upgrade expensive, so start from standard functionality and justify each change.
  • Treating data migration as a late technical task delays go live, so start cleansing during design and run several mock loads.
  • Letting consultants make business decisions leads to poor fit, so require named process owners to sign each design.
  • Testing only scripted happy paths misses real failures, so have key users write UAT scenarios from actual transactions.
  • Going live at quarter end or in peak season adds pressure, so pick a quiet period and plan for the first close.
  • Ending support on go live day leaves users stuck, so keep a hypercare desk through the first month end close.

Frequently asked questions

How long does an ERP implementation take?

It depends on scope, the number of entities, customization and integrations. A focused single entity rollout can fit the 26 week roadmap above. Multi country programs usually run in several waves and take longer. Confirm the date after design sign off and again after the second mock migration.

What is the difference between an ERP roadmap and an ERP project plan?

The roadmap is a one page view of phases, milestones, owners and gates for leadership. The project plan breaks each phase into tasks, dates and dependencies for the team. You need both, and they must match.

Who should be on the ERP implementation team?

You need an executive sponsor, a project manager, a process owner per module, key users, a data migration lead, IT or integration specialists and usually an implementation partner. Choose process owners and key users who are respected in their departments, since they drive adoption.

How much does an ERP implementation cost compared to the software?

The licenses are only one part of the cost. Configuration, integrations, data migration, testing, training and hypercare all add to the budget, and their size depends on your scope. Ask your partner for a scoped estimate before you fix the budget.

What is hypercare in an ERP project?

Hypercare is the period right after go live when the project team gives extra support. Key users and consultants staff a help desk, fix issues quickly and watch integrations and backlogs. It ends when normal support can handle the issue volume, usually after the first close.

Generate this roadmap with AI