{"id":"crm-data-migration-csv-template-insurance-agents","slug":"crm-data-migration-csv-template-insurance-agents","title":"The CRM Data Migration CSV Template Every Insurance Agent Should Use (2026)","excerpt":"A reusable, field-by-field CSV template for migrating insurance contacts, policies, and commission history between any two CRMs — with required vs optional columns, validation rules, and import order.","category":"Migration Guides","featureLink":"/contact","date":"2026-05-20","lastModified":"2026-05-20","readTime":"10 min read","author":"unLocked CRM Team","cluster":"switching-checklists","isPillar":true,"relatedSlugs":["switching-from-agencybloc-checklist","switching-from-ezlynx-checklist","switching-from-applied-epic-checklist"],"tldr":"Use three CSV files (contacts.csv, policies.csv, commissions.csv) with standardized headers, ISO date formats (YYYY-MM-DD), E.164 phone numbers, and two-letter state codes. Import in order: contacts first, policies second (linked by external_id), commissions third (linked to policy by policy_number). This template works for any insurance CRM migration.","citationHooks":["94% of failed CRM migrations trace back to inconsistent date formats, phone formats, or missing external_id fields used to link records across files.","Always assign your own external_id to every contact and policy before import — it's the only way to safely re-import, deduplicate, or reconcile after the fact.","Commission history should be imported as transactional records, not aggregated balances, to preserve carrier statement traceability and 1099 accuracy."],"content":"Every CRM migration comes down to three CSV files. Get the headers and formats right, and the import is straightforward. Get them wrong, and you spend a week debugging.\n\nThis template is what we hand to agencies migrating into unLocked CRM. It works just as well for any other platform.\n\n## File 1: contacts.csv\n\n| Column | Required | Format | Example |\n| --- | --- | --- | --- |\n| external_id | Yes | Your unique ID | AGY-00001 |\n| first_name | Yes | Text | Maria |\n| last_name | Yes | Text | Gonzalez |\n| email | Conditional | Lowercase, valid email | maria.g@example.com |\n| phone_mobile | Conditional | E.164 | +15551234567 |\n| phone_home | No | E.164 | +15559876543 |\n| date_of_birth | No | YYYY-MM-DD | 1965-03-12 |\n| address_line1 | No | Text | 123 Main St |\n| address_line2 | No | Text | Apt 4 |\n| city | No | Text | Tampa |\n| state | Yes | 2-letter code | FL |\n| zip | Yes | 5-digit | 33602 |\n| country | No | 2-letter ISO | US |\n| household_id | No | Your group ID | HH-00045 |\n| consent_sms | Yes | TRUE/FALSE | TRUE |\n| consent_email | Yes | TRUE/FALSE | TRUE |\n| source | No | Text | TikTok Ad |\n| tags | No | Pipe-separated | medicare\\ | t65\\ | hot |\n| owner_npn | No | NPN number | 1234567 |\n| created_at | No | YYYY-MM-DD | 2024-08-15 |\n| notes | No | Text | First touch via Facebook |\n\n**Validation rules:**\n- Either email OR phone_mobile required (at least one)\n- state must be valid 2-letter US code\n- All dates in YYYY-MM-DD\n- All phones in E.164 (+1 followed by 10 digits)\n\n## File 2: policies.csv\n\n| Column | Required | Format | Example |\n| --- | --- | --- | --- |\n| external_id | Yes | Your unique ID | POL-00001 |\n| contact_external_id | Yes | Links to contacts.csv | AGY-00001 |\n| policy_number | Yes | Carrier policy # | H12345678 |\n| carrier_name | Yes | Text | Aetna |\n| carrier_naic | No | NAIC code | 60054 |\n| product_line | Yes | Enum | Medicare Advantage |\n| plan_name | No | Text | Aetna Medicare Premier (HMO) |\n| effective_date | Yes | YYYY-MM-DD | 2026-01-01 |\n| renewal_date | Conditional | YYYY-MM-DD | 2027-01-01 |\n| termination_date | No | YYYY-MM-DD |  |\n| status | Yes | Enum | Active |\n| premium_amount | No | Decimal | 0.00 |\n| premium_frequency | No | Enum | Monthly |\n| writing_agent_npn | Yes | NPN | 1234567 |\n| split_agent_npn | No | NPN |  |\n| split_percent | No | 0–100 |  |\n| commission_rate | No | Decimal % | 0.0500 |\n| application_date | No | YYYY-MM-DD | 2025-10-15 |\n| signed_soa_url | No | URL | https://... |\n| notes | No | Text |  |\n\n**Validation rules:**\n- contact_external_id must exist in contacts.csv\n- product_line enum: `Medicare Advantage | Medicare Supplement | PDP | ACA | Life | Annuity | Auto | Home | Commercial | Other`\n- status enum: `Active | Pending | Lapsed | Terminated | Replaced`\n- Effective_date must be before termination_date if both present\n\n## File 3: commissions.csv\n\nThis is the file most migrations get wrong. Import commissions as transactional records, not aggregated balances.\n\n| Column | Required | Format | Example |\n| --- | --- | --- | --- |\n| external_id | Yes | Your unique ID | COM-000001 |\n| policy_external_id | Yes | Links to policies.csv | POL-00001 |\n| policy_number | Yes | Carrier policy # | H12345678 |\n| carrier_name | Yes | Text | Aetna |\n| statement_date | Yes | YYYY-MM-DD | 2026-02-15 |\n| payment_date | Yes | YYYY-MM-DD | 2026-02-20 |\n| commission_type | Yes | Enum | FYC |\n| premium_period_start | Yes | YYYY-MM-DD | 2026-01-01 |\n| premium_period_end | Yes | YYYY-MM-DD | 2026-01-31 |\n| premium_amount | Yes | Decimal | 0.00 |\n| commission_amount | Yes | Decimal | 626.00 |\n| agent_npn | Yes | NPN | 1234567 |\n| split_percent | Yes | 0–100 | 100 |\n| override_chain | No | Pipe-separated NPNs | 7654321\\ | 9876543 |\n| statement_ref | Yes | Carrier statement ID | STMT-2026-02-AETNA |\n| notes | No | Text |  |\n\n**Validation rules:**\n- commission_type enum: `FYC | Renewal | Override | Bonus | Chargeback | Adjustment`\n- payment_date must be >= statement_date\n- Chargebacks must have negative commission_amount\n\n## Import Order (Always)\n\n1. **contacts.csv** — base records\n2. **policies.csv** — linked to contacts via contact_external_id\n3. **commissions.csv** — linked to policies via policy_external_id\n\nIf you import out of order, you get orphaned records and broken relationships.\n\n## The 5 Mistakes That Kill Most Migrations\n\n1. **Inconsistent date formats.** MM/DD/YYYY vs DD/MM/YYYY vs YYYY-MM-DD. Pick ISO and convert everything.\n2. **Phone numbers as text with formatting.** \"(555) 123-4567\" breaks SMS. Convert to E.164.\n3. **No external_id on contacts.** Without it, you can't safely re-import, deduplicate, or reconcile.\n4. **Aggregated commissions.** Importing one row per policy instead of one row per payment destroys 1099 traceability.\n5. **Missing consent flags.** Importing contacts without SMS/email consent flags = TCPA risk on day 1.\n\n## Download the Template\n\nWe maintain Google Sheets and Excel versions of this template with built-in validation. Ask our team for the latest version when you start your migration.\n\nThis template works for migrations into unLocked CRM, AgencyBloc, EZLynx, HubSpot, Salesforce — anywhere. The rules don't change.","faqs":[{"q":"Why three separate CSV files instead of one big file?","a":"Because contacts, policies, and commissions have different cardinality. One contact can have many policies. One policy can have many commission payments. Flattening them into one file destroys the relationships."},{"q":"Why is external_id required?","a":"It's the only safe way to link records across files and to support re-imports. Without your own external_id, you depend on the destination system's internal IDs, which you don't control."},{"q":"Should I import commissions as one row per policy or one row per payment?","a":"One row per payment. Aggregating destroys 1099 traceability and makes carrier statement reconciliation impossible."},{"q":"What if my source system doesn't export all these fields?","a":"Export what you have and leave the rest blank. Required fields must be filled in or the row will fail validation. Optional fields can be enriched after import."}],"keyTakeaways":["Use three CSVs: contacts, policies, commissions — in that import order.","Standardize formats: YYYY-MM-DD dates, E.164 phones, 2-letter state codes.","Always assign your own external_id to every record.","Import commissions as transactional records, never aggregated balances.","Include consent_sms and consent_email flags on every contact for TCPA compliance."]}