A CRM handover should transfer the work surrounding a customer, rather than merely change the name on a record. Open quotes, dated tasks and promises still need an accountable owner.
Different systems handle reassignment differently. Before a team change or workload redistribution, test which linked records move automatically and which need separate action.
List the work being transferred
- Customer or account ownership
- Open opportunities and quote versions
- Scheduled tasks and appointments
- Pending support or service work
- Necessary team access and approvals
Where sales and service teams share a customer, a sales reassignment may not imply a service reassignment. Alongside “Who owns this account?”, answer “Who will make tomorrow's call?”
Prepare a concise handover note
Summarise the current need, most recent decision, outstanding commitment and next action. Use factual language. “The second quote was sent; the customer needs a delivery estimate; confirm with the technical team before Thursday's call” is more useful than “Follow up later.”
The new owner should not have to reconstruct the entire relationship from disconnected messages. Keep the history intact, while making the immediate next step easy to find.
Test before bulk reassignment
- Select a suitable low-risk sample account.
- Record its owner and outstanding tasks.
- Apply the approved reassignment.
- Check visibility for the new owner.
- Verify reminders, reports and related work.
Understand the correction or rollback route before making a bulk change. Creating a new customer card and copying the details can fragment history and introduce duplicates.
Coordinate the first customer contact
If an introduction is necessary, agree who will make it and what pending commitment they will address. Avoid two employees contacting the same customer independently. Internal staffing details do not need to become part of the customer message.
Review the handover outcome
Look for ownerless tasks, reminders sent to the previous employee, hidden quotes and duplicate follow-up. Account access changes belong to the authorised administrator's separate institutional process.
Common questions
Should previous notes disappear?
No. Relationship history should remain available to authorised staff; verify actual behaviour in the system.
Will every task move automatically?
That depends on the CRM. Test opportunities, reminders and tasks separately.
Describe your workflow to BE Soft through the English website to discuss an appropriate CRM scope.
