CRM Data
Sending a contact or company to another tribe
Handing a record to another tribe: moving it, duplicating it, and what travels with it.
Last updated September 2, 2026
Leads land in the wrong place. Someone enquires through a national website and belongs to a branch two hundred miles away; a customer moves; a territory is redrawn. Transferring hands the record to the tribe that should have it.
Move or duplicate
| Choice | What happens | Use when |
|---|---|---|
| Move | The record leaves your tribe and belongs to the other one. | It was never yours — a misrouted enquiry, a customer in their area. |
| Duplicate | They get their own copy; yours stays. | You both genuinely deal with them, at different sites. |
Duplicating is the right answer more often than people expect in a network: two tribes serving the same national chain each need their own record, because each has its own relationship and its own reporting.
Doing the handover properly
- Log the conversation first, so the receiving tribe can read what was said.
- Transfer the record.
- Tell them. A transferred record does not announce itself.
- If a company and its contacts should both move, transfer them all — the two are not moved together automatically.
A MOVE TAKES IT OUT OF YOUR REPORTING
Once moved, the record counts towards the other tribe's numbers, not yours — including any deal already in play. If the lead is genuinely shared, duplicate it rather than moving it.