Client implementation Gantt chart template: kickoff to handover
An editable Gantt chart for a vendor implementing its product for a customer: kickoff, requirements, configuration, data migration, UAT, go live and hypercare, with client-side inputs shown as explicit gates.
What the client implementation gantt chart template: kickoff to handover process is
When a vendor implements its product for a customer, the plan is only half yours. You control configuration, integrations and training. The client controls who joins the project, when the data extract arrives, whether the API credentials work and whether testers turn up. Plans that hide those inputs inside vendor tasks look healthy until the day a client file is late and nobody can say which task it blocked. This template makes the client side visible as its own group so the conversation at the weekly call is about dates, not blame.
The chart has 22 rows in five groups: Kickoff and requirements, Configuration and build, Client dependencies, Testing, training and go-live, and Hypercare and handover. Eighteen are tasks and four are milestones: "Requirements signed off", "UAT signed off", "Go live" and "Customer handover accepted". "Hold kickoff call" (1 working day) is the only starting task. "Client names project team and approvers" (2) follows it, and "Run requirements workshops" (4) waits for that, because workshops without the people who can decide are a rehearsal.
Requirements sign-off is the gate that releases most of the plan. "Configure product to requirements" (8), "Client delivers source data extract" (6) and "Client provides API credentials and test access" (3) all follow "Requirements signed off". Overlap is used only where it is safe. "Cleanse and map client data" (5) starts 3 days after the extract starts, so mapping begins on the first records instead of waiting for the whole file. "Build integrations with client systems" (7) starts 3 days after configuration starts but also waits for the credentials, so the client's access can hold it back.
The test phase is where the two sides meet. "Run trial data migration" waits for both configuration and the mapped data. "Run internal quality check" (4) waits for the trial migration and the integrations, so the client does not find your defects. "Run user acceptance testing" (6) waits for that check and for "Client books UAT testers" (1), which is a client task on purpose: it can slip while the vendor work is on time. "Train client administrators and users" (4) starts 2 days after acceptance testing starts. "Run final migration and cutover" (2) needs both "UAT signed off" and the training before "Go live".
After go live, "Provide hypercare support" (10) and "Hand over runbooks and configuration records" (3) start together, and "Hand over to support team" (2) waits for both before "Customer handover accepted". All durations are illustrative: set your own from past implementations. A timeline schedules the work. It does not make a configuration correct or a migration complete, and it does not replace your contract or statement of work. For an advisory engagement see /templates/consulting-project-gantt, and for the buyer's own rollout see /templates/implementation-plan-gantt-chart.
What this flowchart covers
In this template
- Five groups, Kickoff and requirements, Configuration and build, Client dependencies, Testing, training and go-live, and Hypercare and handover, with 18 tasks and four milestones: "Requirements signed off", "UAT signed off", "Go live" and "Customer handover accepted".
- Client-side gates as tasks: "Client names project team and approvers", "Client delivers source data extract", "Client provides API credentials and test access" and "Client books UAT testers".
- Safe overlap: "Cleanse and map client data" starts 3 days after "Client delivers source data extract" starts, and "Build integrations with client systems" starts 3 days after "Configure product to requirements" starts.
- A test phase that waits for two sides: "Run internal quality check" follows the trial migration and the integrations, and "Run user acceptance testing" also waits for "Client books UAT testers".
- A close that waits for support to be ready: "Hand over to support team" follows both "Provide hypercare support" and "Hand over runbooks and configuration records".
When to use this template
- You are a vendor, partner or customer success team planning a customer's onboarding and need to agree dates with the client's project lead.
- You want to show the client which of their inputs, such as data, access or testers, decide the go-live date.
- You are comparing the finish date with the date the customer has asked for and want to see which wait decides it.
- You want a repeatable implementation skeleton to copy for each new customer and adapt to the product.
The plan, task by task
Every task in the chart with its length in working days and what it waits for. A dependency is a step number; SS is start-to-start, FF is finish-to-finish, and +n is a lag in working days.
| # | Task | Group | Working days | Depends on |
|---|---|---|---|---|
| 1 | Hold kickoff call | Kickoff and requirements | 1 | |
| 2 | Run requirements workshops | Kickoff and requirements | 4 | 4 |
| 3 | Requirements signed off | Kickoff and requirements | Milestone | 2 |
| 4 | Client names project team and approvers | Client dependencies | 2 | 1 |
| 5 | Provision client environment | Configuration and build | 3 | 1 |
| 6 | Configure product to requirements | Configuration and build | 8 | 3, 5 |
| 7 | Client delivers source data extract | Client dependencies | 6 | 3 |
| 8 | Cleanse and map client data | Configuration and build | 5 | 7SS+3 |
| 9 | Build integrations with client systems | Configuration and build | 7 | 6SS+3, 10 |
| 10 | Client provides API credentials and test access | Client dependencies | 3 | 3 |
| 11 | Run trial data migration | Configuration and build | 3 | 6, 8 |
| 12 | Run internal quality check | Testing, training and go-live | 4 | 9, 11 |
| 13 | Run user acceptance testing | Testing, training and go-live | 6 | 12, 14 |
| 14 | Client books UAT testers | Client dependencies | 1 | 4 |
| 15 | UAT signed off | Testing, training and go-live | Milestone | 13 |
| 16 | Train client administrators and users | Testing, training and go-live | 4 | 13SS+2 |
| 17 | Run final migration and cutover | Testing, training and go-live | 2 | 15, 16 |
| 18 | Go live | Testing, training and go-live | Milestone | 17 |
| 19 | Provide hypercare support | Hypercare and handover | 10 | 18 |
| 20 | Hand over runbooks and configuration records | Hypercare and handover | 3 | 18 |
| 21 | Hand over to support team | Hypercare and handover | 2 | 19, 20 |
| 22 | Customer handover accepted | Hypercare and handover | Milestone | 21 |
How it works
Name the people before the workshops
Keep "Client names project team and approvers" ahead of "Run requirements workshops". Replace the 2 and 4 working days with what your customers usually need.
Treat sign-off as the gate
"Requirements signed off" releases configuration, the data extract and the API access. If your contract allows work to begin on part of the scope, split the milestone by module rather than removing it.
Set the data and access lead times with the client
Agree the length of "Client delivers source data extract" and "Client provides API credentials and test access" at kickoff, and put the dates in the notes so the client sees what each one blocks.
Adjust the overlaps to your product
The two start-to-start links carry a 3-day lag, and the training link a 2-day lag. Change each lag to how much of the earlier task your team needs before the next one can start.
Hold the test gates
Keep "Run internal quality check" before "Run user acceptance testing", and write the acceptance criteria in the task notes before "UAT signed off". Size hypercare from the number of users and integrations you expect.
Add owners, share and export
Put the responsible person in People, share the chart with the client project lead, and export a PDF or CSV for the project file when you need a copy.
Frequently asked questions
How is this different from the buyer's own implementation plan?
This plan is written by the supplier and treats client inputs as scheduled gates. The buyer's rollout covers their internal change, budget and users. For that view, see /templates/implementation-plan-gantt-chart.
Does the chart show if the client is late?
It shows what a late client task would push. If "Client delivers source data extract" takes longer than 6 working days, the dependent tasks and the "Go live" milestone move later. Update the length and read the new finish date.
Why is "Client books UAT testers" a task?
Because testers are usually the scarcest client resource and a booking made late delays acceptance even when the vendor work is done. Giving it a task makes the request, and its date, visible.
Can I add a phase for a data migration only?
Yes. Expand "Run trial data migration" into extract, load and reconciliation tasks, or use /templates/data-migration-gantt for a migration-focused plan. For the process side, see /templates/enterprise-software-implementation-process.
Can I use this for several customers at once?
Copy the chart for each customer, since their gates and dates differ. For the method behind linking tasks, see /guides/gantt-chart-dependencies, and for the onboarding steps as a flowchart, see /templates/customer-onboarding-process.