Skip to main content

CRM Salesperson Handover

Purpose​

CRM Salesperson Handover organizes portfolio transfers for leave, territory changes, team restructuring, or employee exits. Coordinators preview the records and recipients, submit the handover, and track acceptance and execution. Permanent transfer changes ownership; temporary delegation and Shared Backup Owner grant backup access while preserving the primary salesperson.

The guide describes the Odoo 19.0 source workflow. No ownership transfer, notification, or scheduled handover was executed during this review.

Before you start​

Install the exact-major package. The 19.0 manifest requires CRM (crm) and no Enterprise-only or other paid Corvus addon. Version 15.0 also declares base_sparse_field. Both source and target users must be active internal users in the selected company. Identify a coordinator distinct from the designated recipient.

Review the portfolio and open activities before submitting. A permanent handover can reassign all currently open activities on each selected CRM record if its policy enables that option; it is not limited to activities originally owned by the outgoing salesperson.

Access and roles​

CRM Handover Coordinator configures policies, previews and creates handovers, submits them, and manages activation or ending. The native Sales Manager group implies this role in 19.0, and the coordinator role implies all-document sales access.

Sales users can see handovers where they are the designated recipient or a line recipient, within allowed companies. Only the handover's designated recipient can accept it. The coordinator cannot self-accept as recipient. Backup access is provided through a CRM access rule while the handover is active; other native company and CRM restrictions remain relevant.

Setup and menu​

Open CRM → Configuration → Handover Policies. Choose the company and optional team, then decide whether recipient acceptance is required, whether permanent transfer reassigns open activities, whether the recipient becomes a follower, and whether backup access is allowed.

The Incoming Lead Coverage field does not implement automatic future-lead routing. The source explicitly leaves new-lead assignment to an administrator process or native assignment. Plan that separately when covering a salesperson's leave.

Workflow​

  1. Open CRM → Sales → New Pipeline Handover. Select company, source salesperson, optional source team, stage/type/priority, probability and revenue ranges, country, source/campaign, or tags. Refresh Preview selects up to 500 accessible, active records. Review the count, revenue, and individual records.
  2. Choose the handover type and policy. For temporary delegation or backup, provide an end date on or after the start date. Select recipient users and a mapping mode. One Recipient uses the first selected recipient by record order. Equal Distribution distributes records in turn. Capacity-Aware balances the expected revenue assigned within this preview; it does not inspect each salesperson's existing workload or availability.
  3. Select Create Handover. Review the resulting portfolio lines and target users, target team, dates, and instructions. The first recipient becomes the designated recipient on the handover header; multi-recipient distribution does not create a separate acceptance decision for every recipient.
  4. Select Submit. With acceptance required, the designated recipient finds it in Handover Inbox and chooses Accept, Request Clarification, or Reject. Clarification and rejection require a reason. If the policy does not require acceptance, submission immediately executes the handover; review dates and effects before using that setting.
  5. Acceptance activates a due handover. Future accepted handovers are processed by the scheduler; a coordinator can also use Activate on an Accepted handover. Permanent transfer changes each lead's salesperson and optional team, applies the policy's activity/follower choices, and completes the handover. Temporary or backup coverage sets the backup user and remains Active.
  6. At the end of temporary coverage, the scheduled process or End Delegation Now removes backup access. If the primary owner or team changed after the snapshot, those newer values are preserved and the line is marked Conflict. Inspect Delegation Conflicts rather than assuming every line ended identically.
  7. Use Pipeline Handovers, each lead's Handovers smart button, the Handover Pack, and Ownership & Handover Analysis with PDF/CSV output to inspect the portfolio and recorded results.

Practice scenario​

In an authorized test database, create two fictional opportunities owned by “Alex Morgan” and a separate recipient “Sam Ellis,” with an independent coordinator. Configure a policy requiring acceptance and allowing backup access. Preview the two records, create a temporary handover, and have Sam accept a due handover. Inspect that Alex remains the primary salesperson while Sam is the backup. End delegation and inspect the expected removal of backup access. The scenario is source-derived and has not been executed here.

Troubleshooting and limitations​

An empty preview can reflect company, owner, active status, filters, or access. Split larger portfolios into reviewed batches because preview is capped at 500. A recipient who can see a line still may not be the designated recipient authorized to accept the header.

Temporary coverage needs both an end date and a policy allowing backup access. It does not transfer open activities in the same way as permanent transfer. Ending removes the backup relationship even when primary ownership changed; it does not undo newer work. Adding the recipient as a follower is a separate policy effect and is not described as automatically reversed when backup access ends.

The catalogue lists 15.0–20.0. The 15.0 sparse-field dependency, older view conventions, and 20.0 access-definition changes are handled in their corresponding packages. The full workflow scope here is 19.0; targeted comparisons do not establish all-version runtime equivalence.