Template
Onboarding Plan Template With Dates, Owners and Milestones
An onboarding plan template turns a checklist into a schedule for one customer. It holds the project summary, the people on both sides, phases with tasks dated from the kickoff, milestones the customer signs off, known risks and a weekly status format. Copy the template below and fill it in per account.
Onboarding plan, Growth package
Due dates relative to kickoff, tasks split between your team and the customer
- 1Kickoff 4 tasks
- 2Discovery 5 tasks
- 3Configuration 8 tasks
- 4Data migration 6 tasks
- 5Training 5 tasks
- 6Go-live and handoff 5 tasks
What makes an onboarding plan different from a checklist
A checklist answers "what has to happen". An onboarding plan answers "who does it, by when, and what has to be finished first". That extra layer is what lets a customer success or implementation manager run ten onboardings at once without losing track.
The template below has five parts. A one-page summary that an executive sponsor can read in two minutes. A stakeholder table, because a plan without named people on the customer side is a wish list. A phased schedule with due dates counted from the kickoff. Milestones the customer signs off. And a short status format, so updates look the same every week.
If you do not have a checklist yet, start with the onboarding checklist template and come back here to turn it into dates.
Relative dates
Every task is set as Day N from the kickoff. Change the kickoff and the plan recalculates.
One owner per task
Each row names a person on your team or the customer team, never "both" or "IT".
Dependencies written down
The plan says which task waits on which, so a late customer item visibly pushes the go-live.
The onboarding plan template
Copy the full template. Replace the bracketed fields, keep the Day numbers, and add or remove rows per package.
Customer onboarding plan
Onboarding plan for [Customer name]
1. Summary
- Package purchased: [Package, modules, seats]
- Kickoff date (Day 0): [Date]
- Target go-live: [Date] (Day [N])
- Customer goal in their words: [One sentence]
- How success is measured at 90 days: [Metric and target]
2. Stakeholders
| Role | Our team | Customer team |
|---|---|---|
| Executive sponsor | [Name] | [Name] |
| Project lead | [Onboarding manager] | [Name] |
| Technical lead | [Name] | [IT or admin contact] |
| Approver for sign-offs | n/a | [Name] |
| Billing contact | [Name] | [Name] |
3. Schedule
| Day | Phase | Task | Owner | Depends on |
|---|---|---|---|---|
| -3 | Prepare | Welcome email and portal access sent | [Our PM] | Signed SOW |
| -1 | Prepare | Intake form completed | [Customer lead] | Welcome email |
| 0 | Kickoff | Kickoff call, scope and dates confirmed | [Our PM] | Intake form |
| 2 | Kickoff | Plan approved by customer | [Customer approver] | Kickoff call |
| 5 | Discovery | Current process and data sources mapped | [Our technical lead] | Plan approved |
| 7 | Discovery | Admin users and access provided | [Customer IT] | Plan approved |
| 12 | Data migration | Data export delivered in import template | [Customer IT] | Access provided |
| 14 | Configuration | Configuration built to agreed design | [Our technical lead] | Discovery |
| 17 | Configuration | Configuration walkthrough and approval | [Customer approver] | Configuration built |
| 20 | Data migration | Test import validated | [Customer lead] | Data export |
| 24 | Training | Admin training held and recorded | [Our trainer] | Configuration approved |
| 28 | Training | End users invited and logged in | [Customer lead] | Admin training |
| 30 | Go-live | Final import and go-live | [Our PM] | Test import validated |
| 37 | Handoff | Hypercare check-in | [Our PM] | Go-live |
| 40 | Handoff | Handoff to customer success manager | [Our PM] | Hypercare check-in |
4. Milestones the customer signs off
- M1. Plan approved (Day 2)
- M2. Configuration approved (Day 17)
- M3. Data validated (Day 20)
- M4. Go-live confirmed (Day 30)
5. Risks and assumptions
- [Risk] Example. Customer IT has a change freeze in [Month]. Mitigation. Book access before Day 7.
- [Assumption] Example. Data export comes in one file per entity.
6. Weekly status format
- Overall status: On track, At risk or Blocked
- Done this week: [Three lines]
- Next week: [Three lines]
- Waiting on customer: [Item, owner, original due date]
- Go-live date: unchanged or moved to [Date] because [Reason]
How to fill in the plan for a real customer
Take Northwind Logistics, a fictional freight broker that buys a Growth package with a TMS integration and 40 seats. Their onboarding manager starts from this template and makes four changes.
- Set Day 0. Kickoff is booked for a Tuesday, so every Day number turns into a calendar date.
- Add package rows. The TMS integration adds three rows to Data migration. Two belong to Northwind's IT lead, one to the vendor's engineer.
- Check the go-live. Northwind wants to be live before their peak season, which is Day 35. With the extra rows the plan lands on Day 34. Tight, but realistic.
- Name every owner. The IT lead's name goes on five rows, which is a signal to confirm their availability at kickoff.
The result is a plan both teams can read in the same way. When Northwind's export arrives three days late, the plan shows exactly which later rows move, and the weekly status says so in one line.
Building an onboarding program template for several packages
Once you onboard more than one product or package, keep one program template per package rather than one huge plan with optional rows. A Startup package might have four phases and 18 tasks. An Enterprise package adds security review, SSO and a pilot group.
Keep the phase names identical across packages. That way reporting across all onboardings still makes sense: you can compare how long Configuration takes for each package and spot where customers get stuck.
For complex software rollouts, use the deeper implementation plan template, which adds workstreams, cutover and a RACI. For the step before kickoff, the project kickoff agenda covers the first meeting minute by minute.
Let the plan build itself from the SOW
Filling in a template by hand works for the first few customers. After that, the time goes into copying rows, recalculating dates and emailing the customer their part.
In OnboardingCustomers you save this structure as a template per package. When a new deal closes, paste the SOW or let HubSpot, Salesforce or Pipedrive send it. The AI onboarding plan picks the right template, adds rows for what was sold, sets dates from the kickoff and names the stakeholders from the document.
The customer gets a portal with their tasks and milestones, and your team sees every active onboarding with its status in one view.
Northwind Logistics, Growth rollout
Go-live Nov 15, 32 days left
- Closed-won Oct 1
- Kickoff Oct 6
- Discovery Oct 13
- Configuration Oct 27
- Training Nov 7
- Go-live Nov 15
- Confirm data fields to import Customer
- Share current carrier contracts Customer
- Map warehouse codes to locations Vendor
- Review user roles with IT lead Vendor
- Approve configuration workbook 2 days late Customer
Frequently asked questions
Still deciding? Write to [email protected] and a person on our team answers.
What is an onboarding plan template?
Why count due dates from the kickoff instead of using calendar dates?
What is the difference between an onboarding plan and an onboarding program template?
How detailed should the onboarding plan be?
Should the customer see the whole plan?
Paste a SOW and get this plan filled in
OnboardingCustomers reads the SOW, applies your onboarding plan template with real dates and opens a portal where the customer follows their part.