Docs · Migrating from Another CRM

Migrating from AgencyBloc or Radius (Radiusbob)

Insurance-native systems: real policy data, exported separately from contacts. Import clients first, then policies.

Who this is for

Agencies with a real book of business and per-policy data — the migration where the policy detail matters as much as the contacts.

Before you begin

Export contacts/clients and policies as separate files — these systems keep them separate, and that's the shape to keep.
Check whether commission data is in the policy export or its own report.

Steps

Export your clients and your policies.
Import the client file with Import Clients.
Import policies keyed to those clients so each policy lands on the right record.
Spot-check a multi-policy household — a client with auto, home and life should show three policies, not three clients.
Import any leads/prospects separately with Import Leads.

These are the good exports

Insurance-native systems export what an insurance CRM actually needs: carrier, policy number, policy type, effective date, premium, status. Most of it maps directly, so this is usually a cleaner migration than coming from a general-purpose CRM where policy data was crammed into custom fields.

Clients with several policies

The common failure is one row per policy becoming one client per policy. Import the client file first so each person exists once, then attach policies to them. If your export is one flat file with a row per policy, deduplicate the client columns first.

Lapsed and cancelled policies

Bring them. A lapsed policyholder is a win-back target, and cancelled history is how you spot a retention problem. They import with their real status rather than being filtered out.

Ongoing sync, not just migration

If you want to keep pulling policy data from an agency management system rather than importing once, that's a different feature — see the Agency Management System connection under Setup.

How to check it worked

Pick a household you know has multiple policies and confirm it's one client with several policies.
Check premiums and effective dates on a handful of records against the old system.

Common mistakes

One row per policy creating duplicate clients.
Dropping lapsed/cancelled policies from the export and losing your win-back list.
Importing policyholders as leads.

Moving from another CRM — start hereWhat comes across, what doesn't, and the order to do it in — whichever platform you're leaving.Will importing my contacts text my existing customers?Not if you map your stages on the way in.

Where this lives in the app

Open this screenOpens in the app

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