How to Switch Agency Management Systems Without Losing Data
A step-by-step checklist for migrating to a new insurance agency management system without losing commission history, compliance records, or client data — and how to time it around AEP and OEP.
How to Switch Agency Management Systems Without Losing Commission or Compliance History Switching your agency management system safely comes down to three things: export and map every record before you touch the new system, run both systems in parallel long enough to prove the numbers match, and never schedule the cutover during AEP or OEP. Do those three things in order and the move is a project. Skip any one of them and you find out at tax time, or during an audit, that a chunk of your book never made the trip. Most agencies don't think about this until they're already unhappy with their current CRM. By then the decision gets rushed, and the risk isn't the new software — it's everything that has to survive the handoff: policy records, household relationships, Scope of Appointment documentation, call recordings, and months or years of commission history that ties a paid statement back to a specific client and policy. What actually breaks when agencies switch systems Three categories of records cause almost every migration problem agencies report after the fact: Orphaned client data. A policy, household member, medication, or health condition record gets imported as a flat row with no link back to the contact it belongs to. The data exists, but nothing in the new system connects it to the client, so it's effectively invisible the next time someone opens that record. Broken commission history. Spreadsheet-based or loosely structured commission tracking rarely maps cleanly to a new system's data model. If the new platform can't match a historical paid commission back to the client and policy that generated it, you lose the ability to catch missing payments or prove what you were owed on a chargeback. Compliance records that don't travel with the client. Scope of Appointment forms, consent and TCPA opt-in records, and call recordings are useless if they end up in a folder or a separate archive instead of attached to the client record CMS or a carrier audit will ask about. Before you sign anything: audit what you actually have Do this before you pick a new system, not after. You need an honest inventory of what has to move, because it determines both the timeline and the questions you ask every vendor on your short list. Export every client, household, and policy record from your current system, including custom fields. If your current vendor can't produce a full export on request, get that answer in writing before you negotiate your exit. Pull a full commission history export — every paid, pending, and charged-back commission, tied to a client and policy ID. Locate every compliance artifact: SOA forms, consent/TCPA records, call recordings and their retention dates, and any BAA or compliance documentation tied to your current vendor. Count duplicates. Agencies that have been through two or three systems usually find duplicate contacts and duplicate household members from previous imports. Clean these up in the old system first; a new system will faithfully import duplicates right along with everything else. Write down every custom field your team actually uses day to day, separate from the fields nobody has touched in a year. You only need a mapping plan for the first group. This is also where you decide what AgencyView's practical guide to choosing a CRM for insurance agents calls "the questions to ask any vendor" — ask every finalist exactly how they handle commission history and compliance record import, and get the answer before you sign, not during onboarding. Map commission and compliance records first, not last Client and policy data is usually the easy part of a migration — names, addresses, and policy numbers map fairly cleanly between systems. Commission history and compliance records are where agencies lose things, because they depend on the new system's data model matching a payment or a document back to a specific client and policy. Record type What has to survive the move How to verify it did Commission history Every historical paid, pending, and charged-back amount, tied to the client and policy that generated it Pull a report by carrier and compare total paid commissions against your old system's report for the same period Policy records Status, effective date, carrier, and the household member it covers Spot-check a sample of policies per product line against the source system Scope of Appointment / consent records The signed document and the date, attached to the specific client it covers Open five random client records and confirm the SOA or consent is attached, not just "somewhere in storage" Call recordings and transcripts Attached to the client and call date, retained per your state's requirement Confirm a sample of recordings plays and is linked to the right contact A platform where every policy, household member, medication, provider, and health condition record is created through the client's own contact record — rather than inserted as a standalone row — is what keeps this from becoming a recurring problem after the move, not just during it. Time the cutover around AEP and OEP, not around your contract renewal date Medicare's Annual Enrollment Period runs October 15 through December 7 every year, and ACA Open Enrollment for the coming plan year runs November 1 through January 15 in most states, with December 15 as the deadline to enroll for a January 1 start. If your book includes Medicare or ACA clients, a system cutover inside either window is the single most avoidable mistake in a migration: it's also the period when your team can least afford a week of reduced productivity while they learn new screens. Work backward from whichever enrollment period affects more of your book. If your renewal with your current vendor falls inside AEP or OEP, that is a negotiating point, not a deadline you have to honor — ask for a short extension so the cutover itself happens before the period starts or after it closes. A day-by-day migration checklist This is the sequence to follow once you've picked a new system and have a go-live date set outside AEP and OEP. 60–45 days out: Finish the data audit above. Get a written field-mapping plan from the new vendor for your commission and compliance data specifically, not just contacts. 45–30 days out: Run a test import of a small, representative slice of your book — one carrier, one product line, 20–30 clients. Check that policies, household members, and commission history all land attached to the right contact. 30–14 days out: Fix whatever the test import got wrong. Clean duplicates in the source system. Confirm every team member knows the go-live date and what their job is that week. 14–7 days out: Run the full import into the new system while keeping the old system live and unchanged. This is your parallel run. 7–1 days out: Reconcile. Pull a commission report from both systems for the same period and confirm the totals match by carrier. Spot-check SOA and consent records on a sample of clients. Don't go live until this reconciliation is clean. Go-live day: Freeze changes in the old system. Move your team's daily work — calls, quotes, follow-ups — to the new system only. First 30 days after go-live: Keep read-only access to the old system for reference. Reconcile commission statements as they land, since this is when a missed mapping shows up as a payment that doesn't match anything in the new system. Example: a five-agent Medicare and ACA agency with three years of commission history decided to switch systems in July, specifically to avoid touching anything during AEP. They ran their test import on their 40 Medicare Advantage clients from a single carrier, caught a mapping error where chargebacks weren't linking to the original commission record, fixed it with the vendor before the full import, and were live on the new system by August 1 — more than ten weeks before AEP opened. Where AgencyView fits in AgencyView is built so…
Where AgencyView fits
Keep reading
Share: Facebook · LinkedIn · X · Email
All articles · AgencyView