Docs · Migrating from Another CRM

Migrating from a carrier back-office or NAAIP (no real CRM)

Policy lists with thin contact detail. Import what you have, then fill in the gaps as you work them.

Who this is for

Agents whose 'system' has been the carrier portals and a commission statement. This is a first-CRM migration, not a platform switch.

Steps

  1. Pull policy lists from each carrier portal you write with.
  2. Combine them into one sheet, one row per policyholder where you can.
  3. Import as Clients — these are customers, not leads.
  4. Fill in missing contact detail over time as you touch each client.

Missing emails are fine

Carrier exports are policy-first and often have no email at all. Email isn't required — import with what you have. A client with a phone and a policy is perfectly usable; the record improves as you work them.

One person, several carriers

If you've written the same household with two carriers, they'll appear in two exports. Combine them into one client with two policies rather than importing twice, or the same person shows up as two clients.

This is where the CRM starts paying off

Coming from no CRM, the win isn't the import — it's what becomes possible after. Renewals and policy anniversaries can trigger outreach automatically, which is the thing that's impossible when your book lives in a PDF statement.

Common mistakes

  • Waiting until the data is 'complete' before importing. Import what you have.
  • One client per policy instead of one client with several policies.

Related

Moving from another CRM — start hereWhat comes across, what doesn't, and the order to do it in — whichever platform you're leaving.Migrating from AgencyBloc or Radius (Radiusbob)Insurance-native systems: real policy data, exported separately from contacts.

Where this lives in the app

Open this screenOpens in the app

This is documentation for Virtual Closer. Book a walkthrough or sign in.