---
title: "How Do I Run an Implementation to CSM Handoff Properly?"
description: "The implementation to CSM handoff on one page: goals as measured, configured or skipped, open issues with owners, adoption by team, and first value."
topic: "Onboarding & Adoption"
author: "Raj Bheda, Co-founder, GainTrace"
audience: "Implementation Specialist, Onboarding Manager"
published: 2026-09-04
modified: 2026-09-04
source: https://gaintrace.com/explore/onboarding/implementation-to-csm-handoff
---

# How Do I Run the Implementation to CSM Handoff Without Losing Context?

*The second handoff is the one nobody designed*

**Short answer:** An implementation to CSM handoff works when six things move on one page: the goals and how they were measured, what was configured and what was skipped, every open issue with an owner, adoption by team, the stakeholder map as it is now, and whether the first value milestone was reached. Confirm it on a 25-minute joint call, then introduce the CSM on a call the implementation lead runs.

**Key takeaways**

- The sales handoff moves the promise; the implementation handoff moves the reality. The CSM inherits goals that have been measured against, configuration that was skipped, and issues the customer thinks are still being worked on. None of those three has a CRM field.
- Write the goals as they were measured, not as they were sold. 'Cut invoice processing time' from the order form becomes 'from 4 days to 1.5 days on the AP team, measured in week 5' on the handoff page. The CSM should never have to ask the customer what the goal was.
- Every open issue leaves implementation with a named owner and a date, or it is closed with the customer told why. An issue that is open in the implementation tracker and absent from the account record has vanished as far as the customer is concerned.
- The CSM is introduced by the implementation lead on a call the customer already has in the diary, and the implementation lead is off the account seven days later. Two contacts for a month means the customer keeps emailing the one who knows the configuration.
- If the first value milestone was not reached during implementation, the page says so and the CSM's first 30 days are about reaching it. A 'complete' handoff of an account that has not seen value is the pattern behind onboarding-complete-but-churned.

Your implementation to CSM handoff is a calendar invite titled 'go-live' and a spreadsheet the CSM has not opened. Twelve weeks ago you took the account from sales with a kickoff, a goal and a deadline. Since then you have configured it, worked around two integrations that did not behave, trained three teams, and logged nineteen issues, four of which are still open. The customer knows you. They do not know the CSM, and the CSM knows the account from the CRM, which says it is 'onboarded'.
This page is for the implementation specialist or onboarding manager who runs that handoff and wants the CSM to start from where you finished, not from the beginning. It gives the six-item handoff document as a checklist, the 25-minute joint call as an agenda, the customer-facing introduction, the failure modes we see in the corpus with the fix for each, and a table of what lives where. The first handoff, from sales into implementation, is on [the sales to customer success handoff checklist](https://gaintrace.com/explore/onboarding/sales-to-customer-success-handoff-checklist); this page assumes it happened and picks up at go-live.

## Where does the context get lost between implementation and the CSM?

The sales handoff has a thread of its own in most CS communities. The second handoff, from the people who configured the product to the person who will own the relationship, mostly does not, because it happens inside the same department and everyone assumes it is fine. The corpus says otherwise. A Head of CS whose customer had stopped a meeting to say they had already answered the question described where the pieces were.

> "Sales has their notes in the CRM, Support is in [the help desk], Implementation has a checklist on a random [project] board, and CS is trying to piece it all together. Everyone has a piece of the puzzle, but nobody actually knows the current ground truth."
>
> — Head of Customer Success, r/CustomerSuccess, 2026

The implementation checklist on the random board is the problem in one line. It is written for the implementer, in the implementer's shorthand, organised by task rather than by what the customer wanted, and it is complete the moment the last task is ticked. Nothing in it says whether the customer got what they bought. Another poster, describing years of handoffs at their company, put the cost in a metric.

> "Our CSAT at day 30 was always lower than at day 0. The enthusiasm from buying turned into frustration during implementation."
>
> — r/CustomerSuccess, 2026

The numbers in our corpus are small and telling. Of 946 r/CustomerSuccess threads, 42 mention implementation and 30 a handoff or handover; only 3 mention both. Among 3,628 public G2 reviews of the three most-reviewed customer success platforms, 40 name or come from an implementation, professional services or onboarding team, and 30 mention handoffs or transitions as a problem the buyer wanted solved. One mid-market reviewer listed 'gap identification relative to functional department handoffs, tighter ownership' among the reasons they bought a platform. People are buying software to find the gaps between their own teams. The gap this page closes needs a page, a call and a rule; the wider [customer onboarding best practices](https://gaintrace.com/blog/customer-onboarding-best-practices) sit around them.

## What goes in an implementation to CSM handoff document?

> **The go-live six:** The go-live six are the six things a CSM needs on the day they inherit an account: goals marked measured, configured or skipped, open issues with owners and dates, adoption by team, the stakeholder map with who attended, what was promised, and the first value the customer has seen. Everything else is in the tools already.

One page, drafted by the implementation lead in the last week before go-live, corrected by the CSM on the joint call. Each item has a test. If the item fails the test it is not handed off, and the CSM will rediscover it on a call with the customer, usually the wrong one.

**Before the CSM is introduced, the handoff page contains**
- [ ] **Goals, and how they were measured.** The goal from the sales handoff, restated as it was tracked during implementation, with the baseline and the current reading. 'Cut invoice processing time' becomes 'invoice cycle from 4 days to 1.5 days on the AP team, measured week 5; the target was 1 day'. Test: the CSM can state the goal, the number and the gap without asking the customer.
- [ ] **What was configured, and what was skipped.** Every workflow, integration and permission set that is live, and every one that was descoped, deferred or worked around, with the reason and who on the customer's side agreed. Test: when the customer asks in month two why the CRM sync only runs nightly, the CSM knows their IT lead chose that, and why.
- [ ] **Open issues, each with an owner and a date.** Bugs, requests, data problems and questions still in flight, wherever they live: the support desk, the product backlog, the implementation tracker. Each one is either closed and the customer told, or open with a named owner and a next date. Test: nothing is open in the tracker that is absent from the page.
- [ ] **Adoption by team.** Which teams were trained, which are active, which have not signed in, with active users against the seats they bought. Test: the CSM knows which team to worry about on day one.
- [ ] **The stakeholder map as it is now.** The sponsor, the champion, the day-to-day owner and the sceptic from the sales handoff, updated: who turned up, who was replaced, who has become the real decision maker, who blocked. Test: the CSM's first email goes to the right person and copies the right person.
- [ ] **The first value milestone: reached or not.** The moment the customer would call a result, dated if it happened, with what is blocking it if it did not. Test: the page says one of two things, 'reached on [date], evidence: ...' or 'not reached, blocked by ..., owner ...'. It never says 'onboarding complete'.

The last item is the one that changes the CSM's first month. A handoff that says 'complete' hands over a project; a handoff that says 'not reached, blocked by the data feed from their ERP, owner their IT lead, next date the 12th' hands over the account. The difference between those two, and why customers churn after finishing onboarding, is on [time to value](https://gaintrace.com/explore/onboarding/time-to-value-onboarding-complete-but-churned).

The second item is where promises hide. A delivery lead in our corpus described a data migration that was not in the statement of work: 'Somewhere in the sales cycle, someone on our side told them we'd handle the historical data migration. It's not in the SOW. Nobody remembers saying it. We're doing it for free now.' Whatever the resolution, it goes on the page under skipped or worked around, with the reason, because the CSM will hear about it at renewal otherwise.

## What happens on the 25-minute joint call, minute by minute?

Internal: the implementation lead and the CSM, booked for the week before go-live so the introduction can happen at go-live rather than after it. The CSM has read the page; the call is for correcting it.

1. **Before the call: the CSM reads and marks.** Fifteen minutes with the page, the sales handoff doc and the implementation tracker. Every line the CSM does not understand, or would otherwise have to ask the customer about, gets a question mark. Those are the agenda.
2. **Minutes 0 to 5: the project in the implementer's words.** One question: what happened between kickoff and now that is not on this page? The answer contains the personality of the account: who was hard to reach, who changed their mind, what nearly went wrong.
3. **Minutes 5 to 10: goals and the gap.** Read the goal line and the current number. Agree what 'reached' means and whether it was. If the first value milestone was not reached, agree what the CSM will do in the first 30 days to reach it and what implementation still owes.
4. **Minutes 10 to 15: configured and skipped.** Walk the skipped list. For each item the CSM asks: will the customer raise this, and when? Anything the customer thinks is coming moves to open issues with a date.
5. **Minutes 15 to 20: open issues and the stakeholder map.** Every open issue gets an owner who is not the implementation lead, or a close date the implementation lead commits to. Then the four names, corrected: who runs this now.
6. **Minutes 20 to 25: the introduction and the exit date.** Agree which customer call the introduction happens on (the go-live review, ideally), who says what, and the date the implementation lead leaves the account: seven days after the introduction, unless an open issue on the page names them.
7. **After the call: the page goes on the account record.** Linked from the account, shared with support so they stop routing tickets to the implementer, and used by the CSM to write their first email. The page is edited in place from here; the tracker is archived.

## How should the customer be introduced to their CSM?

The introduction is done live, by the implementation lead, on a call the customer already has in the diary. A poster who had run handoffs for years described why their company stopped doing it by email and started doing it in the room.

> "The customer never feels like they're starting over with someone who doesn't know them. The CS rep has context from being in the room, not from reading notes."
>
> — r/CustomerSuccess, 2026

The go-live review is the natural place. The implementation lead runs the first fifteen minutes: what was set up, what was measured, what is still open and who owns it, said in front of the customer so the open issues become a shared list rather than a private one. Then the introduction, in three sentences the customer can repeat.

> **The three sentences, said on the call and repeated in writing the same day:** 'From today, Sam owns your account. Sam has the full record of what we built, what we measured and the four items still open, and I have walked through every one of them with Sam. For the next week you have both of us; after that, Sam is your contact for anything about goals, priorities and decisions, support handles anything broken, and I am off the account.' The implementation lead then sends the same three sentences in an email that afternoon, with the open-issues list attached and Sam copied, and Sam's own first email follows within one working day.

The CSM's first email is its own subject, on [the first email from the new CSM after handoff](https://gaintrace.com/explore/onboarding/first-email-from-the-new-csm-after-handoff). The point here is the sequence: introduction on the call, confirmation from the implementer, then the CSM's email that proves the context arrived. Three messages in two days, then one owner.

## Which failure modes break the handoff, and what fixes each?

Every implementation to CSM handoff we have seen go wrong went wrong in one of these ways. The middle column is what the customer sees.

| Failure mode | What the customer sees | Fix |
| --- | --- | --- |
| The CSM re-asks the goals | 'What are you hoping to achieve with the platform?' three months after they told sales and then implementation | Goals as measured on the page, with the number. The CSM's first email restates them; it never asks. |
| Open issues vanish | A bug they reported in week 8 is never mentioned again, then comes back at renewal as 'you never fixed it' | Every open issue has an owner who is not the implementer and a next date, and the list is read out on the introduction call. |
| 'Complete' means configured, not adopted | Onboarding is marked done, two of three teams never signed in, the account churns at month 10 | Adoption by team on the page; first value milestone stated as reached or not. 'Complete' is retired as a status. |
| The implementer stays the contact | The customer emails the person who knows the configuration for months; the CSM is a name on a signature | Live introduction, seven-day overlap, then a one-line redirect from the implementer on every email: 'Sam owns this now', Sam copied. |
| The stakeholder map is one name | The CSM writes to the sponsor who delegated in week 2 and never replies; the real owner is unknown | The map updated at handoff: who turned up, who was replaced, who decides now. |
| A skipped item becomes a promise | 'You said the ERP sync would be in phase two', with nobody who remembers saying it | The skipped list with reasons and who on the customer's side agreed, on the page, dated. |

The third row is the expensive one. A poster who ran a cohort analysis on their own accounts found that the strongest predictor of renewal at month 12 was whether a structured week-four review happened as a dedicated meeting: in their data, 91% renewed when it did and 67% when it did not. Those are one company's figures and we would not generalise them, but the mechanism is the one this page is about. The review asks the customer whether they are using what they expected to use. The handoff page is where the answer is written down and given to the person who has to act on it.

## What lives where after go-live?

The implementation tracker, the account record and the handoff page have different lifetimes. The tracker dies at go-live. The account record lives as long as the customer. The handoff page is the bridge between them and should stay small enough to reread.

| Item | Implementation tracker | Account record | Handoff page |
| --- | --- | --- | --- |
| Task list, dates, who did what | Yes, the source | No | No; archived with the tracker |
| Goals as measured, baseline and current number | Sometimes, buried in a task | The current number, updated | Yes, with the method and the gap |
| Configuration: live, skipped, worked around | As tasks | Live config in the product itself | The skipped and worked-around list, with reasons and who agreed |
| Open issues | As tickets | Linked to the support desk | Each with owner and next date; the list read out at introduction |
| Adoption by team | No | Live usage by team, from product data | The snapshot at handoff and the team to worry about |
| Stakeholder map | Contacts on invites | Contacts and roles, updated | The four roles, who decides now, and what changed since sales |
| First value milestone | A milestone task, ticked | The date it was reached, if it was | Reached or not, with evidence or the blocker |
| Promises from the sales cycle | No | The sales handoff doc, linked | Only the ones that changed during implementation |

Gaps found during implementation between what was sold and what exists go to product too, with the ARR attached, through the shared intake on [customer feedback to product](https://gaintrace.com/explore/playbooks/customer-feedback-to-product-from-cs-sales-support). For enterprise accounts, the goal line and the open issues become the first rows of the [mutual success plan](https://gaintrace.com/explore/playbooks/mutual-success-plan-template-customers-use), which is the document the customer sees; the handoff page is the internal one.

## How do I know the handoff is working?

Four numbers, kept by the onboarding manager and reviewed monthly with the Head of CS.

- Customers asked by the CSM to restate a goal, a configuration decision or an open issue in the first 30 days. Target zero. Count them by asking CSMs; they know.
- Open issues at go-live without an owner and a date. Target zero. Each one is an issue the customer thinks is being worked on and nobody is.
- Emails from the customer to the implementation lead after day 7 post-introduction. Target under one a month per account. Above that, the introduction did not land.
- Accounts handed off with the first value milestone not reached, and how many of those reach it within 30 days. The first number tells you about implementation scope; the second tells you whether the CSM's first month is doing the right work.

The person who most needs this page to exist is the one who wrote in our corpus, six months into an implementation role, that a client was churning and the account management team was 'really digging into it'. When the handoff page says what was measured, what was skipped and why, and who owned each open issue, the investigation has a document to read instead of a person to blame.

## How does GainTrace keep the implementation context on the account?

GainTrace puts billing, CRM, product usage and support on one account record, so adoption by team and the open support issues are already there when the handoff page is written, rather than copied from three tools. [Product signals](https://gaintrace.com/platform/product-signals) show whether the team implementation worried about has started signing in after the introduction, and [customer success on GainTrace](https://gaintrace.com/solutions/customer-success) turns an open issue past its date, or a first value milestone not reached by day 30, into a task with an owner, without an admin building the workflow.

## Frequently asked questions

### What should implementation hand over to the CSM at go-live?

Six things on one page: the goals as they were measured, with baseline and current number; what was configured and what was skipped, with reasons; every open issue with an owner and a next date; adoption by team against seats bought; the stakeholder map as it stands now; and whether the first value milestone was reached, with evidence or the blocker. Confirmed on a 25-minute joint call before the customer introduction.

### How is the implementation to CSM handoff different from the sales to CS handoff?

The sales handoff moves what was promised and why the customer bought; the implementation handoff moves what was built, measured and left open. The first is written in the customer's words before anything exists; the second is written against numbers and a configuration. A CSM needs both: the sales doc to know the promise, the implementation page to know the reality.

### When should the implementation specialist leave the account?

Seven days after the live introduction of the CSM, unless an open issue on the handoff page names them as owner, in which case they stay on that issue only until its close date. Longer overlaps mean the customer keeps emailing the person who knows the configuration and the CSM never becomes the owner. Shorter ones, or an exit by email, feel like being dropped.

### The customer keeps emailing the implementation manager instead of the CSM. What do we do?

The introduction did not land, or there was no live introduction. Fix it on the next customer call: the implementation lead says the three sentences (the CSM owns the account, has the full record, and the implementer is off after this week), then confirms in writing the same day. After that, the implementer answers any customer email with one line redirecting to the CSM, copied.

### What do we do when the first value milestone was not reached during implementation?

Say so on the handoff page, with the blocker and its owner, and never mark the account complete. The CSM's first 30 days are about reaching it: one plan, one date, the implementation lead still on the blocking issue if it is theirs. A handoff that says complete when the customer has not seen a result is the pattern behind accounts that finish onboarding and churn.

### Should the handoff document live in the CRM, the project tool or somewhere else?

On the account record, linked from wherever the CSM works, and edited in place. The project tool is archived at go-live and nobody in CS opens it. The CRM has the contacts and the contract but no field for 'skipped because their IT lead chose nightly sync'. The page is small enough to reread and is the only thing anyone will.

## How this was researched

We read 946 r/CustomerSuccess threads and pulled the 42 that mention implementation and the 30 about a handoff or handover, including the threads on the implementation handoff, the customer asked the same question twice, and the delivery lead's unscoped migration; the quotes and counts above come from those threads and are linked below. We searched 3,628 public G2 reviews of the three most-reviewed customer success platforms for handoffs, transitions and implementation or professional services teams and counted the reviews naming them. The six-item page, the call agenda and the failure-mode table are our synthesis; the renewal figures quoted from one poster's cohort analysis are theirs, not a benchmark.

## Sources

- [r/CustomerSuccess: The implementation handoff is where customer relationships die](https://reddit.com/r/CustomerSuccess/comments/1t8wk2m/the_implementation_handoff_is_where_customer/)
- [r/CustomerSuccess: The most awkward handoff failure is asking a customer the same question twice](https://reddit.com/r/CustomerSuccess/comments/1unwfik/the_most_awkward_handoff_failure_is_asking_a/)
- [r/CustomerSuccess: Client took 3 weeks to send one file. Somehow we're the ones behind schedule.](https://reddit.com/r/CustomerSuccess/comments/1vdmy9f/client_took_3_weeks_to_send_one_file_somehow_were/)
- [r/CustomerSuccess: The onboarding step we always skipped that turned out to predict renewals](https://reddit.com/r/CustomerSuccess/comments/1tr0b69/the_onboarding_step_we_always_skipped_that_turned/)
- [r/CustomerSuccess: Will I get fired bc a customer churned?](https://reddit.com/r/CustomerSuccess/comments/1u7dqtv/will_i_get_fired_bc_a_customer_churned/)
- [G2: Customer Success software category (source of the 3,628 public reviews)](https://www.g2.com/categories/customer-success)

## Next steps

Draft the six-item page for the account going live next week, book the 25-minute call before the go-live review, and watch adoption by team from the account record after the introduction. [Start free](https://app.gaintrace.com/auth/login) or [book a demo](https://gaintrace.com/booking).