ERP Implementation Project Plan Template Excel: Columns and Formulas
9 min read ยท 2026-11-19
An erp implementation project plan template excel users can rely on is a workbook with one row per task and 13 columns: ID, phase, workstream, task, owner, start, duration, end, predecessor, status, exit condition, baseline end and variance. Dates come from formulas, not typing, so one delay moves everything that depends on it.
Below is the template ready to copy, with sample rows, the exact formulas with cell references, a Gantt built with conditional formatting, and the extra tabs your steering committee needs.
The roadmap at a glance
Goal: Run a single-entity ERP rollout from charter to support handover from one Excel workbook, with every date calculated from its predecessor and every slip measured against a frozen baseline. Duration: 20 weeks
Mobilize (Weeks 1-2)
Set up the team, governance, charter and the baseline plan.
- Have the executive sponsor sign the project charter, scope and success measures.
- Build the Plan tab with the 13 columns and create the Holidays named range.
- Fill in tasks, owners, durations and predecessors, and let the formulas calculate the dates.
- Paste the End column as values into Baseline end once the plan is approved.
Milestone: Baseline end column filled and plan approved at the first steering committee.
Requirements (Weeks 3-7)
Capture requirements per process area and get the design approved.
- Run finance fit gap workshops, led by the finance process owner.
- Run supply chain fit gap workshops, led by the supply chain process owner.
- Log every requirement with an ID and a MoSCoW tag.
- Submit the solution design to the executive sponsor for approval.
Milestone: Design document approved by finance and supply chain process owners.
Build (Weeks 8-10)
Configure the system and build extensions, reports and integrations.
- Configure the chart of accounts and legal entity with the finance lead consultant.
- Build the extensions, reports and integrations listed in the approved design.
- Demo the configuration to the finance process owner.
Milestone: Configuration demo accepted by the finance process owner.
Data (Weeks 11-12)
Map, cleanse and rehearse the data migration, alongside Build where possible.
- Map source data objects to the new system.
- Cleanse the data before each load.
- Run migration rehearsal 1 and give each later rehearsal its own row, owner and exit condition.
Milestone: Rehearsal log shows duration and error count per data object.
Test (Weeks 13-15)
Prove the solution works end to end and train the users.
- Run integration testing across finance and supply chain.
- Run user acceptance testing, led by the test manager.
- Train users before cutover.
Milestone: UAT sign off with no open critical defects.
Cutover (Weeks 16-20)
Decide, go live and hand over to support.
- Prepare the cutover runbook.
- Hold the go or no go meeting with the executive sponsor and record the decision in the Milestones tab.
- Go live and run hypercare.
- Hand over to the support manager.
Milestone: Go decision recorded in the Milestones tab and handover document signed by the support manager.
The phases the workbook needs
You don't need a long phase guide to build the file. You only need phase names that match how your project will report. These six work for most single-entity rollouts.
If your partner follows its own method, such as SAP Activate (Prepare, Explore, Realize, Deploy), use its phase names in the Phase column. Then your status reports match their documents. For several entities or sites, add a Wave column and filter on it.
- Mobilize: team, governance, charter and the baseline plan.
- Requirements: fit gap workshops per process area, then design approval.
- Build: configuration, extensions, reports and integrations.
- Data: data mapping, cleansing and migration rehearsals, run alongside Build.
- Test: integration testing, user acceptance testing and training.
- Cutover: runbook, the go or no go decision, go live and hypercare.
The ERP project plan template to copy into Excel
Paste the lines below into cell A1 of a sheet named Plan, then use Data > Text to Columns with a comma delimiter. Row 1 holds the headers and the sample tasks start at row 2. The dates and durations are examples. Replace them with your own. Leave Start (from row 3 down), End, Baseline end and Variance empty. The formulas in the next section fill them in.
Each row gets a real exit condition. "Design done" can't be checked. "Design document approved by finance and supply chain process owners" names the document and the people who approve it.
- Task ID,Phase,Workstream,Task,Owner,Start,Duration (working days),End,Predecessor ID,Status,Exit condition,Baseline end,Variance (days)
- MOB-01,Mobilize,PMO,Sign project charter and scope,Executive sponsor,2027-01-04,5,,,Not started,Charter and success measures signed by the sponsor,,
- MOB-02,Mobilize,PMO,Build plan workbook and save baseline,Project manager,,5,,MOB-01,Not started,Baseline end column filled and plan approved at first steering committee,,
- REQ-01,Requirements,Finance,Run finance fit gap workshops,Finance process owner,,10,,MOB-02,Not started,Every finance requirement logged with an ID and a MoSCoW tag,,
- REQ-02,Requirements,Supply chain,Run supply chain fit gap workshops,Supply chain process owner,,10,,REQ-01,Not started,Every supply chain requirement logged with an ID and a MoSCoW tag,,
- DES-01,Requirements,All,Approve solution design,Executive sponsor,,5,,REQ-02,Not started,Design document approved by finance and supply chain process owners,,
- BLD-01,Build,Finance,Configure chart of accounts and legal entity,Finance lead consultant,,15,,DES-01,Not started,Configuration demo accepted by the finance process owner,,
- DAT-01,Data,Data,Run migration rehearsal 1,Data lead,,10,,BLD-01,Not started,Rehearsal log shows duration and error count per data object,,
- TST-01,Test,All,Run user acceptance testing,Test manager,,15,,DAT-01,Not started,UAT sign off with no open critical defects,,
- CUT-01,Cutover,PMO,Hold go or no go meeting,Executive sponsor,,1,,TST-01,Not started,Go decision recorded in the Milestones tab,,
- HYP-01,Cutover,Support,Run hypercare and hand over to support,Support manager,,20,,CUT-01,Not started,Handover document signed by the support manager,,
The formulas, cell by cell
First, create a named range called Holidays. On a separate tab, list your public holidays and freeze days, such as the year-end close, in one column. Select them and type Holidays in the Name Box.
Then add these formulas to the Plan tab and copy each one down the column.
- End (H2): =WORKDAY(F2,G2-1,Holidays). The minus 1 matters. A 5-day task that starts on a Monday should end on that Friday. =WORKDAY(F2,G2) would return the next Monday, and every task would end one day late.
- Start of a dependent task (F3): =WORKDAY(XLOOKUP(I3,$A:$A,$H:$H),1,Holidays). This finds the predecessor's End and starts on the next working day. Excel versions without XLOOKUP can use =WORKDAY(INDEX($H:$H,MATCH(I3,$A:$A,0)),1,Holidays). Copy it down from F3. Only F2, the first task, keeps a typed date.
- Two predecessors: add a column for Predecessor 2 and wrap both lookups in MAX: =WORKDAY(MAX(XLOOKUP(I3,$A:$A,$H:$H),XLOOKUP(N3,$A:$A,$H:$H)),1,Holidays), where N3 holds the second ID. Put this extra column after Variance so the Gantt can start one column further right.
- Baseline end (L): once the sponsor signs the plan, copy column H and use Paste Special > Values into column L. Never paste formulas here, or the baseline will move with the plan.
- Variance in days (M2): =IF(L2="","",H2-L2). A positive number is a slip, measured in calendar days. For working days, use =IF(L2="","",IF(H2>=L2,NETWORKDAYS(L2,H2,Holidays)-1,1-NETWORKDAYS(H2,L2,Holidays))).
- Status (J): use Data > Data Validation > List with Not started, In progress, Blocked and Done, so filters and counts stay clean.
Build the Gantt with conditional formatting
To the right of the table, leave column N empty as a spacer, so the Predecessor 2 column can go there later. Then use one column per week, starting in O1. Follow these steps in order.
- In O1, type =$F$2-WEEKDAY($F$2,3) to get the Monday of the first week. In P1, type =O1+7 and copy it across for as many weeks as the project runs.
- Format row 1 as a short date and narrow the week columns.
- Select O2 to the last week column of your last row. Add a conditional formatting rule with a formula: =AND(O$1<=$H2,O$1+6>=$F2). Give it a fill in your report color.
- Add a second rule, placed above the first, to mark milestones: =AND($G2=1,O$1<=$H2,O$1+6>=$F2), with a darker fill. One-day tasks such as the go or no go meeting then stand out.
- Add a third rule on the whole table A2:M100 to flag late work: =AND($J2<>"Done",$H2<TODAY()), with red text.
- Select cell E2 and use View > Freeze Panes, so the IDs, phases and task names stay visible as you scroll across the weeks.
The other tabs, and how they read the Plan tab
The Plan tab is the single source of truth. Every other tab pulls its dates from it, so nobody updates dates in two places.
MINIFS and MAXIFS need Excel 2019 or later. XLOOKUP needs Excel 2021 or Microsoft 365. On older versions, use INDEX and MATCH.
- Milestones: one row per gate, with the gate name, Task ID, date, approver and decision. Date: =XLOOKUP(B2,Plan!$A:$A,Plan!$H:$H), where B2 holds the Task ID, such as DES-01.
- RACI: one row per deliverable and one column per role, with R, A, C or I in each cell. Check that each row has exactly one A: =COUNTIF(C2:J2,"A")=1.
- Risks: description, probability, impact, score (=probability*impact on a 1 to 5 scale), owner, mitigation and next review date.
- Budget: planned cost per phase, committed, actual, and variance as actual minus planned.
- Roadmap: one row per phase, for the steering committee. Phase start: =MINIFS(Plan!$F:$F,Plan!$B:$B,A2). Phase end: =MAXIFS(Plan!$H:$H,Plan!$B:$B,A2). Worst slip in the phase: =MAXIFS(Plan!$M:$M,Plan!$B:$B,A2).
Turn the workbook into a steering committee page
Leadership won't read the Plan tab. Copy the Gantt rules onto the Roadmap tab, so each phase shows as one bar. Then add a short status note per phase, the next three milestones from the Milestones tab and the top three risks by score.
Set a print area on that range. Switch to landscape, choose Fit All Columns on One Page and save it as a PDF. Send the same page before every steering committee. Because the dates come from formulas and the baseline is frozen, the Variance column shows progress honestly.
Common mistakes to avoid
- Using =WORKDAY(F2,G2) for End pushes every task one working day late and compounds down the dependency chain, so subtract 1 from the duration with =WORKDAY(F2,G2-1,Holidays).
- Typing start dates by hand after the first row means a delay upstream never reaches the tasks that depend on it, so calculate every start from its predecessor's End.
- Overwriting the baseline each time the plan moves hides every slip from the steering committee, so paste it once as values after sign off and leave it alone.
- Leaving data migration as one row in Build hides the real work, so give each rehearsal its own row, owner and exit condition.
- Forgetting the Holidays range lands tasks on public holidays or during the year-end close, so list those days on their own tab and name the range Holidays.
- Putting all tasks, risks and costs on one sheet makes filtering slow and reporting error-prone, so keep tasks on the Plan tab and give milestones, risks and budget their own tabs.
Frequently asked questions
Is there a free ERP implementation project plan template in Excel?
Yes. Copy the comma-separated lines in this guide into cell A1 of a new sheet and split them with Text to Columns. Then add the End, Start, Baseline and Variance formulas listed above. You get the Plan tab with ten sample rows, ready to replace with your own tasks.
What columns should an ERP project plan have?
In this order: Task ID, Phase, Workstream, Task, Owner, Start, Duration in working days, End, Predecessor ID, Status, Exit condition, Baseline end and Variance. The IDs and predecessors are what let Excel calculate the dates for you.
How do I calculate task end dates in Excel without counting weekends?
Use =WORKDAY(Start,Duration-1,Holidays). The minus 1 makes a task's first day count, and the Holidays range skips public holidays and freeze periods.
How do I make a Gantt chart for an ERP plan in Excel?
Add one column per week with the Monday date in the header row. Then apply a conditional formatting rule such as =AND(O$1<=$H2,O$1+6>=$F2), which fills each week a task is active. A second rule with a darker fill marks one-day milestones.
What is the difference between the ERP project plan and the ERP roadmap?
The project plan is the task-level sheet the team updates every week. The roadmap is the one-page summary of phases, milestones, decisions and risks for leadership. In this workbook, the Roadmap tab reads its dates from the Plan tab, so both always match.