How to Switch CRMs Without Losing Your Book of Business

Take inventory, then test your export

The scariest part of switching isn’t the import — it’s discovering, three weeks after cutover, that something you needed only lived in the old system. Before any demo, list every kind of data your agency touches: contacts, policies, notes and history, files, call recordings, email, calendar items, templates, and follow-up automations. Recordings and automations are the most often forgotten — the first usually lives with a phone vendor, the second exists only as settings with no export button — document them screen by screen. (Still choosing? See our guide to the best CRM for insurance agents.)

Then run your current system’s full export today, while you’re a customer in good standing, and actually open the files. Are notes in there, or just names and numbers? Are policies structured fields, or one text blob? Contacts usually export fine; history and files are where mainstream tools get thin, and the fallbacks are slow — better discovered before you’ve committed to a switch date.

Apply the same test to your destination. Workganic’s answer: Batch exports your filtered client list to CSV anytime, with sortable columns including each client’s current age — the book you bring in stays a book you can take out.

Asset	Export it as	Common gotcha
Contacts	CSV with every custom field	Custom fields dropped; phones merged into one column
Policies	CSV or per-client report	Details flattened into a note instead of structured fields
Notes & history	CSV or per-client PDF	Often excluded from standard contact exports
Files & documents	Bulk download (ZIP)	Links instead of files — they die with the account
Call recordings	Audio plus transcripts	Stored with the phone vendor — a separate export
Automations & templates	Screenshots and copied text	Settings rarely export; rebuild by hand
Phone numbers	Port request to the new provider	Canceling old service mid-port can forfeit the number

Typical patterns as of June 2026 — check your own vendor’s export documentation.

Map fields and statuses on paper first

Build a two-column sheet: every column in your export on the left, its destination on the right. Decide the ambiguous cases now — which phone column is primary, where the spouse’s name lands, where homeless custom fields go. A mapping improvised mid-import is how books end up with thousands of duplicates.

Statuses aren’t labels — they’re your pipeline, and collapsing ten old stages into three new defaults erases where every client stands. Workganic lets you define your own client statuses with colors, categories, and ordering, and statuses drive follow-up lists, batch updates, and the power dialer’s calling pools — so map to statuses your team will actually work.

Then import a test batch — fifty clients, not five thousand — and inspect it before loading the rest. Afterward, Batch’s filters slice the book by status, state, company, or agent to spot-check the landing.

Phone numbers and email: the two slow lanes

Your numbers are portable, and the rules favor you. FCC rules require simple ports — generally a single line — to complete in one business day, and your old provider cannot refuse a valid port request even if you owe a balance. Multi-line business ports run slower in practice — plan on weeks, not days. The mistake that loses numbers is canceling old service mid-port: a number must be active to transfer, and a released number is hard to recover. Keep the old line until you’ve test-called the new system.

Email has the same trap, so don’t cut over to a new address on day one. Workganic’s Mail app works as the email client for the account you already have — Zoho, Gmail, Outlook/Microsoft 365, or just about any email provider — with reads, folders, and actions staying in sync, nothing changing on the other end. When you’re ready to consolidate, migration runs incrementally with pause and resume; move to your own domain later, and guided setup confirms your domain is pointed right before anything switches.

Run in parallel, then cut over with a checklist

Plan a two-to-four-week parallel run: new activity in the new system, the old one open as read-only reference. Resist updating both — double entry is how parallel runs die. Pick a hard cutover date before training starts, and train by workflow, not feature tour: log a call, set a follow-up, find a policy, send a text. Fifteen minutes per task beats a two-hour demo.

Cutover day is a checklist, not a feeling: numbers ported and test-called; email syncing; statuses spot-checked against the mapping sheet; files opening; the team confident on their five daily tasks. Then take one final full export, store it dated, and keep the old account alive (downgraded if possible) for 60 to 90 days. Insurance records can carry state retention requirements — check your state’s rules before deleting anything; this is general guidance, not legal advice.

1. Inventory and test your exportList everything living in the old system, then actually run its export before you commit to anything.
2. Map fields and statuses on paperDecide where every field and status lands before the first import, not after.
3. Start the number port earlyCarrier ports take time — never cancel old phone service until the port completes.
4. Keep email continuousConnect your existing mailbox first; migrate history incrementally instead of cutting over day one.
5. Parallel-run, then cut overWork both systems briefly, then switch on a checklist — and keep the old export archived.

Frequently asked questions

Competitor and third-party names and marks belong to their owners. Pricing and feature details about other products reflect public list information as of June 2026 and may have changed — always confirm on the vendor’s site. Workganic capabilities described here reflect the platform as shipped today.