Handing a CRM over to the client: clean, complete, drama-free

Handing a CRM over to the client is the moment of truth for any agency mandate: either the client takes ownership of a system they understand and truly own – or a project ends with open questions, orphaned data and frustration on both sides. A clean CRM handover can be planned: complete data, clarified roles and a technical change of ownership that in Advanzo is a single step.

This guide is written for agencies and consultancies that set up and hand over client CRMs. It walks through what to do before, during and after handover – drama-free and without a single data export.

What does a clean CRM handover include?

Four things: complete and cleaned data, a documented sales process, a trained client team and the technical transfer of ownership. Only when all four are in place is the handover really done – system access alone does not make an owner.

In Advanzo the last point is deliberately simple: the client workspace is transferred to the client as a whole, with every contact, deal, email and setting. There is no export, no migration and no transition period with data living in two systems.

Why do handovers fail without a plan?

Usually at three points: knowledge stays in the agency's heads, responsibilities stay unclear, and technical ownership stays stuck with the service provider. The client then works in a system they neither own nor understand – until the first disagreement.

You may recognise the symptoms: the client calls about every small thing because nobody internal is admin. Pipeline stages only the agency can explain. Or the most awkward scenario of all: the collaboration ends, and the client has to ask their ex-provider for access to their own customer data. A planned handover closes exactly these gaps – structurally, not through goodwill.

How do you prepare the handover?

With a checklist you work through in the two to three weeks before the cut-over date. This scope has proven right:

• Clean the data: merge duplicates, close dead deals, delete or enrich contacts without context. The client should inherit a well-kept system, not an archive.
• Document the pipeline: capture every stage with entry and exit criteria on one page. What does "Qualified" mean? When does a deal count as "Negotiation"?
• Clarify responsibilities: who on the client team becomes admin? Who maintains deals? Who answers internal questions as first point of contact?
• Review open deals: go through every active deal with the client: status, next step, owner. Never hand over anything nobody knows.
• Check email connections: are the client team's mailboxes (Gmail, Outlook or IMAP) syncing correctly so correspondence keeps landing on the deal?

This preparation is the real work of the handover; the technical part afterwards takes minutes. Plan these points as joint working sessions with the client, not as silent agency tasks – whoever helped tidy the system understands it twice as well afterwards.

How does the technical handover work in Advanzo?

Through workspace transfer: from the agency console, you transfer ownership of the client workspace to the client. Afterwards the client fully owns their CRM – all data, all settings, all history stay exactly where they are.

The decisive extra: if wanted, you as the agency keep access as a collaborator. "Your workspace with the client invited" becomes "the client's workspace with the agency invited" – the collaboration continues seamlessly, only the ownership is now the right way round. How the console works overall is covered in our post on agency mode in practice and on the agency console page.

The ownership change is clean from a data-protection angle too: the data stays hosted in Switzerland throughout, no copy remains with the agency, and after the transfer the client is formally and factually in control of their customer data – exactly as the Swiss DPA (DSG) and the GDPR intend.

Which pitfalls should you avoid?

Most handover mishaps are predictable – and therefore avoidable. Five classics from practice:

• Handover by email: sending credentials is not a handover. Plan a joint handover meeting where you walk through system, data and open points together and trigger the ownership transfer together.
• Personal accounts: email connections or integrations running through an agency person's account break after the project ends. Everything recurring belongs on the client's accounts.
• Vague leftovers: "we'll tidy that later" never happens. Anything not cleaned up by handover belongs on a written list with owners and dates.
• Silence after the cut-over: agree a fixed check-in for the first four weeks after handover. Most questions surface in week two, not on handover day.
• Everything at once: don't hand over ownership, new processes and new workflows on the same day. Stable operations first, then the ownership change – that way it stays clear what caused what.

The common thread: a handover is a process spanning two to four weeks, not an appointment. Plan it that way and surprises become rare.

What do you change about roles and access?

At handover you flip the roles: at least one person on the client team becomes admin of the workspace, and the agency moves to a member role – or leaves the workspace entirely if no ongoing care is agreed. In Advanzo, roles always apply per workspace, cleanly separated from your other mandates.

The order matters: first appoint and train the internal admin, then transfer. A workspace without a capable admin on the client side is the most common cause of support ping-pong after handover.

How do you train the client team?

Short, concrete and on the real system: two one-hour sessions cover most SME teams – one for daily sales work (creating deals, maintaining stages, email on the deal), one for admins (users, roles, settings, workflows). Train inside the client workspace with real deals, not demo data.

Also capture the most important routines in a short document that stays with the company. That way the knowledge survives staff changes on the client side.

What happens after the handover?

Ideally, the second phase of the mandate begins: ongoing care. The transferred workspace still appears in your agency console – now as a shared workspace – and you support at the agreed level: quarterly reviews, new workflows, data hygiene, training new team members.

This model – the build as a project, the care as a retainer – is the core of the Advanzo partner programme. You'll find the agency terms on the partner page and the overview at Advanzo for agencies.

And if the client wants to continue fully on their own: also fine. A handover after which the client needs nothing more from you is not a lost mandate – it is your best reference for the next one.

Frequently asked questions (FAQ)

Does the client lose data during handover?

No. Handover in Advanzo is a change of ownership of the existing workspace, not a migration. Contacts, deals, email history, documents and settings remain fully intact – nothing is exported or re-imported.

Can the agency still access the CRM after handover?

Yes, if both sides want that. During the transfer, the agency can stay in the workspace as a collaborator and keep supporting the client. As admin, the client can adjust or end this access at any time.

When is the right time for the handover?

Once the data is clean, the sales process is documented and the client team has worked independently in the system for at least two weeks. Handing over purely by project plan often means handing over too early – team maturity matters more than the date.

What does the CRM cost the client after handover?

The workspace simply keeps running: free up to 25 deals, then CHF 25 per user/month on the Plus plan or a flat CHF 350 per month for unlimited users (Pro Unlimited). The optional AI add-on costs CHF 9 per user/month.

What happens to workflows and settings?

They stay unchanged. Configured workflows, pipeline stages, fields and email connections belong to the workspace and move with the ownership change automatically. The client should know them, though – which is why they belong in the admin training.

Does the handover require a data export?

No. That is precisely the advantage of the workspace model: the client takes over the running system as a whole. An export is at most a useful extra backup for the files – it is not needed.

Planning your first handover or want to test the model? Start Advanzo for free, build the client workspace and transfer it once everything is in place – the transfer itself is one click.