Two customer layers, policyholder and producer, both have to survive the move, along with complaint history that examiners may one day ask to see.
Insurance migrations commonly retire an older CRM or agency management tool used for distribution, a spreadsheet of producer relationships, and a service log kept by the contact center. We load agencies, producers, households and policyholders into Salesforce, reference policies from the policy administration system rather than copying policy data, and carry forward service requests, complaints and communications with their dates intact. Producer appointments and license status come across where the distribution team relies on them. Matching rules are built around policy numbers, producer codes and tax IDs, since names alone are unreliable across carriers, MGAs and agencies.
Insurance data has two customer layers that both matter: the policyholder and the producer or agency that placed the business. Legacy systems often store only one well. Producer data also changes constantly, with agencies merging, producers moving and codes being reassigned, so older extracts can attribute business to the wrong distribution partner. Complaint and service records carry regulatory weight, since market conduct examinations may ask for them, which means history needs original timestamps and outcomes preserved. Nonpublic personal information is present throughout, subject to GLBA and state privacy rules, so extract handling and access design are part of the migration plan from the start.
Agencies, branches, individual producers and their codes are rebuilt as a hierarchy, with appointment and license status attached where the distribution team relies on them. Mergers and code reassignments are resolved during cleanup, so production reports and service routing credit the right partner after cutover. Inactive producers are kept for history but clearly marked, which stops new business or cases from being assigned to them.
Personal lines customers often appear once per policy in legacy tools. We match on policy links, addresses and identifiers to build households with related individuals, then attach service history to the person or household it belongs to. Representatives get a combined view of every policy a family holds, and cross-sell reporting stops counting one household as several unrelated customers. Commercial insureds follow a separate entity-based rule.
Complaints, inquiries and endorsement requests from the contact center's old system move with received date, category, state, resolution and response dates. We validate that the migrated history reproduces existing complaint reports, because compliance teams may need to produce those records later for an examiner, and the original correspondence stays attached to each record. Department of insurance inquiries are tagged separately from direct complaints so the two can be reported on their own.
Opt-ins, do-not-call flags and channel preferences from agency and carrier systems are consolidated with a clear precedence rule when sources disagree. Preferences load before any campaign or automation is enabled, so the first outreach from Salesforce respects what customers asked for. Each preference keeps its source and capture date for later review by compliance. Agency-held preferences are merged only when agreements allow it.
We start with distribution, service and compliance leaders, since each owns part of the data and part of the risk. Producer and agency records load first, because policyholder and service data reference them. Policies come in as references from the policy administration system, not copies. Test loads are reconciled by line of business and state, and compliance reviews a sample of migrated complaints against their original files. Extracts are encrypted in transit and at rest, access is limited to named people, and temporary files are deleted after sign-off. Cutover usually follows a month-end close so production reporting stays clean.
Policy numbers, effective dates and status are used for matching and loaded as reference records, while coverage, premium and endorsement data remain governed by the policy system.
Producer contacts, activities and client lists from agencies or internal agency tools are matched against carrier data so each relationship lands under the correct producer.
License states, lines of authority and appointment status are linked to producer records, helping distribution teams avoid routing business to someone not appointed for it.
Nonpublic personal information is in extracts, staging tables and sandboxes as well as production. Apply GLBA and state privacy requirements with your compliance team to each environment, restrict who can access raw files, and document how temporary copies are destroyed.
Received and resolved dates drive complaint reporting and response-time analysis. A migration that replaces them with load dates quietly corrupts compliance history. Map original dates to dedicated fields, lock them against editing and confirm reports match prior filings for every state involved.
Agency acquisitions and producer moves should be settled before policyholder data loads. Otherwise, service history and relationships attach to outdated producers, and correcting them afterward means reassigning large volumes of records by hand while agents and policyholders wait. A frozen producer mapping, signed off by distribution, is the safer path.
Client names are anonymized.
Usually as a reference, not a full copy. Policy number, product, status, effective dates and the related producer are typically enough for service and sales teams. Coverage details, rating and billing stay in the policy administration system, with integration or on-screen lookups where people need more. That keeps one authoritative version of each policy and a smaller data set to secure.
Yes, where agreements permit it. Agency-owned client data may have contractual limits on how a carrier can use it, so we confirm those terms with your distribution and legal teams first. Approved lists are matched against policyholder records by policy number and address, and anything outside the terms stays with the agency that owns it.
We rerun the complaint reports compliance already relies on, using the migrated data, and compare them by state, category and period to the originals. Differences are traced to specific records and corrected before compliance signs off. A second reviewer also samples individual complaints end to end, checking dates, correspondence and resolution notes against the original source files.
Often it is. Commercial lines may have more complex account hierarchies, brokers and service teams, while personal lines brings volume and household matching. Sequencing them separately lets each team validate its own data without competing for attention. The shared model for producers and customers is designed up front, so the second phase joins cleanly without rework to the first.
One onshore team with 150 Salesforce certifications, a Salesforce Consulting Partner since 2017.
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.