What's included
The rows owned by the customer are marked as theirs. Look at how many there are, and where they sit relative to your own work:
- Sales handover & kickoff, The handover pack, the success criteria and the specific first-value outcome, the customer project owner and decision makers, the kickoff call and the customer-side commitments with dates against them. Milestone: kickoff complete and owners named.
- Discovery & customer dependency mapping, A walkthrough of the current process, then the honest list: every input the customer owes you, who owns the data, who holds the integration credentials, and what security review or procurement step stands between you and production. Milestone: customer dependencies confirmed with dates.
- Fast path to first value, Deliberately narrow. Provision the tenant, configure one workflow, hand-load enough data to make it real, onboard a handful of users, and get the customer to produce one genuine output before the big work starts. Milestone: first value delivered.
- Data migration & integrations, The phase most likely to slip, because most of it is theirs: extracting and delivering files, mapping and transformation, a trial import with a data quality report back to them, their cleansing pass, the integration build and their security sign-off. Milestone: data and integrations live.
- Configuration, training & rollout, Remaining workflows and permissions, the customer's configuration sign-off, admin training, and end-user sessions that the customer has to fill with its own people. Milestone: users trained and configuration signed off.
- Go-live, adoption & handover, Readiness check, cutover from the legacy process, hypercare, measurement of time to first value and adoption, legacy retirement, and handover to the customer success manager. Milestone: onboarding closed and account in run state.
Who uses this template
Customer success managers, onboarding specialists, and implementation teams at SaaS and B2B companies use this plan after a deal closes. It runs from kickoff through data and integrations, training, and go-live, mapping customer-side dependencies and a fast path to first value so accounts reach adoption quickly and hand off cleanly to ongoing support.
How to customize it
- Mark every customer-owned row clearly and put a named person from their side against it, not a department.
- Move the first-value milestone earlier if your product allows it; four weeks is a common target and shorter is better.
- Add a row per integration and per data source, one combined bar hides exactly the dependencies that will slip.
- Insert the customer's security review, procurement and legal steps explicitly if they are enterprise; these routinely take longer than the technical work.
- Lengthen the cleansing loop if the trial import is likely to find problems; one round is optimistic for most migrations.
- Add rows for the customer's own change management if you are replacing a process people are attached to.
Scheduling tips
- Publish a shared plan, not your plan. The customer needs to see their own rows and dates, because those are the ones that move.
- Define first value as one specific output. "Live" is not a milestone; "the operations team produced this week's schedule in the product" is.
- Ask who has actually done the export before. The answer is often nobody, and that changes your estimate more than any technical detail.
- Give the data quality report back to the customer. Cleansing is theirs to do, and a specific list of bad records moves faster than a request to tidy the data.
- Measure time to first value on every account. It is the one onboarding metric that predicts adoption, and it makes the case for front-loading rather than sequencing.
Related templates
- CRM Implementation Plan Template
- Free Employee Onboarding Gantt Chart Template
- ERP Implementation Schedule Template
- Free 30-60-90 Day Plan Gantt Chart Template
- Data Migration Project Plan Template
- Browse all Gantt chart templates
Frequently asked questions
How long should customer onboarding take?
It varies enormously with the amount of data and integration involved. The template runs about five months for a mid-market implementation with a migration; a self-serve product can be days. The more useful question is time to first value, which should be a small number of weeks regardless of how long full rollout takes.
What is time to first value?
The elapsed time from the contract or kickoff to the moment the customer gets one genuine, useful output from the product, not a demo, not a training exercise. It is the metric this template is built around, because a customer who has seen real value tolerates the rest of the implementation, and one who has not starts asking what they bought.
Why does the plan front-load one narrow outcome?
Because full configuration before first login produces a long silent stretch where the only thing the customer experiences is work they owe you. A narrow first workflow with hand-loaded data creates something real to build outward from, and it surfaces misunderstandings while they are still cheap to fix.
What do I do when the customer misses their dates?
Expect it, and design for it. Name the dependency and its owner in the first fortnight, review the customer-owned rows in every status call, and show the knock-on effect on the go-live date rather than absorbing it quietly. Absorbing slippage teaches the customer that their dates do not matter, and the delivery team pays for it later.
How is this different from an employee onboarding plan?
Completely different plan despite the shared word. The employee onboarding template covers a new hire's first weeks, equipment, access, introductions, ramp. This one covers implementing a product for a paying customer, where the schedule is shared with another organisation and most of the risk lives on their side of it.
Is the customer onboarding template free?
Yes. Free Excel, PowerPoint and CSV downloads, and free online editing with no account and no watermark.