Guide

Customer onboarding checklist: the sales handover

A customer onboarding checklist starts at the sales handover. Before onboarding begins, sales should hand over eight facts about the deal, and four of them should be required. This guide lists the eight, explains why each matters, and shows how to run the project through to go-live.

The handover checklist

Most onboarding problems start with something sales knew and nobody wrote down. A short checklist fixes that. Items marked required should block the handover until they are filled in.

ItemRequiredWhy it matters
Signed order form attachedYesIt is the source of truth for what was bought. Without it, scope is a matter of memory.
Go-live target dateYesEvery plan needs an end date. It also tells you when the customer expects value.
Customer project contactYesSomeone on the customer side must own the work and answer questions.
Modules / scope purchasedYesThe team sets up what was sold, not what they guess was sold.
Licences soldNoTells you how many users to plan for and how to track deployment later.
Special commitments made in the saleNoDiscounts, promised dates or extra training. The customer will remember them.
Integrations requiredNoIntegrations take the longest and need the customer's IT team early.
Kickoff call scheduledNoA booked date turns the handover into a start.

Keep the required list short. If every item is required, people fill in junk to get past it. Four required items that are always true beat eight that are half guessed.

After handover: the project stages

Once the handover is accepted, track the onboarding as a project with a clear stage. These stages cover most teams:

  • Queued: accepted, waiting for a team to start.
  • Planning: tasks, owners and dates being agreed with the customer.
  • In progress: setup, data migration, integrations and training under way.
  • CSM review: the work is done and the CSM is checking it.
  • Live: the customer is using what they bought.

Two more stages handle the exceptions. On hold is for projects paused by the customer. Cancelled is for projects that will not go ahead. Both keep the board honest instead of leaving stale projects in progress.

A go-live date that means something

A go-live date is only useful if everyone agrees on what live means. Write it down at kickoff. For example: "Live means the sales team is logging every deal in the system and the two integrations are syncing." That sentence prevents arguments later.

Set the date with the customer, not for them. If it moves, record the new date and the reason. A project that slips three times without a note is a renewal risk you can see a year early.

CSM sign-off before live

The CSM will own the account for years. The implementation team owns it for weeks. So before a project goes live, the CSM should check each onboarding task and sign it off.

If a task is not right, the CSM sends it back with a note that says what is missing. The project stays in review until it is fixed. This one habit catches the half-finished setups that otherwise turn into the first support tickets.

Mistakes that slow onboarding down

  • A handover by meeting only. A call with no written checklist loses details within a week.
  • Missing commitments. If sales promised something, delivery must know about it before kickoff.
  • No customer owner. Without a named project contact, tasks wait for answers nobody gives.
  • Integrations left to the end. Start them in planning, because they depend on other teams.
  • Going live on a finished task list. Done tasks are not the same as a working setup. Get CSM sign-off first.

How OneVio enforces it

In OneVio's customer onboarding, every project starts with this handover checklist, and you can change the items to fit your team. A project stays in Handover until every required item is filled, and OneVio names the items still missing. Projects then move through Queued, Planning, In progress, CSM review and Live, with On hold and Cancelled for exceptions. In CSM review, the CSM signs off each task or sends it back with a note.

Handover checklist on a OneVio onboarding project, with completed items ticked and one required item still empty and flagged
Make every handover complete.Book a 30-minute demo and we will walk through handover, project stages and CSM sign-off.
Book a demo

Choosing a tool for onboarding? Compare customer success CRMs by the jobs your team does every week.

Related

Book a demo

See OneVio with your own renewals.

A 30-minute walkthrough with your accounts in mind. Tell us a little about your team and we'll reply within one working day.

  • A 30-minute walkthrough with a CS lead
  • Your own separate workspace if you go ahead
We only use these details to reply. Privacy
FAQ

Onboarding checklist questions

What should a sales-to-CS handover include?

At minimum: the signed order form, a go-live target date, the customer's project contact and the modules or scope they bought. It also helps to record licences sold, any special commitments made in the sale, integrations required and whether the kickoff call is booked.

Who fills in the handover checklist?

The salesperson who closed the deal fills it in, because they know what was promised. The implementation lead or CSM reviews it and asks questions before accepting the handover. A required item left empty should block the handover.

Why record special commitments made in the sale?

Because the customer remembers them even when your team does not. A discount on year two, a promised feature date or extra training hours all need to be known by the people delivering onboarding, or they become a broken promise.

When is customer onboarding finished?

When the customer is live on what they bought and the CSM has signed off every onboarding task. Finishing the task list is not enough. The CSM who will own the account checks the work before the project is marked live.

What happens if the CSM is not happy with the work?

The CSM sends the task back to the implementation team with a note that says what is missing. The project stays in review until the gaps are fixed. That is far cheaper than handing a half-finished setup to the customer.