Map Imported Reps to Your Team

Leads imported from another CRM keep their original rep's name, and mapping that name to a real user re-owns every one of their leads at once.

What it is

A roster of every distinct lead owner seen in imported data, with the lead count per owner and their current mapping. Mapping an owner to a platform user is one roster row plus one bulk update that re-owns every one of that owner's leads. Transfer re-owns one person's leads onto another user and retires the source row, keeping the history.

Also called: zoho lead owner · old CRM rep names · my rep quit · transfer leads to another rep

See it
Leads Manager
Leads Manager48 leads · 48 shown · 1 selectedImport leadsMap imported reps
Search name, email, phone, city…
Lead age: newest → oldestAny budgetAny ownerAny lead statusAny sourceAny stateAny county
Emily Wenger
Jan 9, 2027
Sheila Nunez
Paige Nolt
Dec 21, 2026
Janelle Ruiz
Dawson Hoover
Sep 16, 2026
Curtis Vance
Ashley Gehman
$72,936.00 · Aug 20, 2026
Rosa Delgado
Justin Reinford
$43,779.00 · Aug 19, 2026
Sheila Nunez
Emily Wenger
Emailemily.wenger7@demo.invalid
Phone(717) 555-0111
Address2819 Ridge Rd, Seneca, KS
CountyNemaha
Reassign to
Choose a team member…
Leave unassigned
Bess Kowalczyk
Emmett Boyd
Gus Petrillo
The Imported Reps roster: each external owner with a lead count, a name-match suggestion chip, and a Map / Transfer control. The real screen, drawn from the product’s own design system. Sample data — no customer information appears here.
How it works
  1. 1Imported leads stamp the external owner id and name, and set the displayed rep name to the CRM name even before that person is a platform user
  2. 2Auto-suggestion is by name equality only, because the export carries no owner email, and it is surfaced as a one-click suggestion never auto-committed
  3. 3The bulk write only runs after an admin confirms in a dialog
  4. 4Writing the assignment email lets the link self-heal when the rep signs in
Why we built it

Leads imported from another CRM arrived owned by a name rather than a person, so the board showed reps who did not exist as users and nobody could tell whose book was whose. The original name reads correctly from the moment of import, and mapping it to a real user re-owns every one of that rep's leads at once. A name match is only ever a one-click suggestion and is never committed automatically, because the write behind it changes ownership of hundreds of records. The same path covers the case that forced it: a rep quits, and their book has to move.

The problem
  • Imported ownership data becoming meaningless on migration
  • A departed rep's book being unreachable
  • Manual reassignment of a whole rep's pipeline
Sound familiar?
What you get
Imported leads read with the right rep's name from day one
One confirmation re-owns an entire rep's book
A departure is a transfer, not a rebuild

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →