EZLynx to Applied Epic Conversion
An EZLynx to Applied Epic conversion extracts personal and commercial clients, contacts, policies, carriers, users, activity history, and attachments from the agency's EZLynx data, maps them to Applied Epic codes and service roles, loads clients first, matches the new lookup codes back to every record, and reconciles the results.
The Source
What an EZLynx conversion starts from
Our EZLynx conversions run against the agency's EZLynx data in a SQL Server database: applicant, commercial applicant, policy, carrier, user, activity, note, task, claim, and attachment tables. Attachment files are delivered separately as a folder of documents and are matched back to their records during the conversion.
Two choices shape the project early: how far back activity history should go, and whether attachments are in scope. A conversion readiness assessment is a good place to settle both.
Data Domains
What moves from EZLynx
Actual scope is set per engagement. These are the EZLynx data domains we extract and map:
Personal clients
Applicants and co-applicants, with their addresses.
Commercial clients
Commercial applicants, kept separate from personal accounts throughout.
Contacts
Individual and commercial contacts for each account.
Policies
Policy master and detail records, split into package and monoline policies, with policy status mapped.
Carriers and lines of business
Carrier names and NAIC codes, and the lines of business on each policy.
Users, producers, and CSRs
Users, account CSR assignments, producer code mappings, and service teams.
Activities, notes, and tasks
Activities, activity emails, applicant notes, note activities, tasks with checklist items, and claim entries.
Attachments
Attachment records matched against the attachment files delivered with the data.
Known Quirks
EZLynx-specific challenges and how we handle them
Personal and commercial accounts use different IDs
EZLynx keeps personal applicants and commercial applicants in separate tables with separate ID sequences, so the same number can identify two different accounts.
How we handle it: Personal accounts carry their applicant ID as the prior account reference and commercial accounts carry their commercial applicant ID. A guard checks for collisions between the two before any matching runs.
Lookup codes have to be matched back after the client load
Applied Epic assigns client lookup codes when clients are loaded. Policies, activities, and attachments then need those codes, which EZLynx has never seen.
How we handle it: We load the Applied Epic import results back into a mapping table and match each EZLynx account in stages: direct ID, normalized exact name, raw exact name, partial name, then phonetic. Low-confidence and personal-versus-commercial mismatches go to manual review, and unmatched accounts stay unmatched rather than being guessed. Strict matching can be used for commercial accounts.
History comes from six different places
Activity history is split across activities, activity emails, applicant notes, note activities, tasks, and claim entries.
How we handle it: We combine all six into Applied Epic activities, strip HTML and embedded links from note text, trim notes to the length the import accepts, map task status to open or closed, assign a default employee where the user is blank, and set aside duplicates in their own review tab.
Carrier and line of business codes need agency decisions
Carrier names in EZLynx can come from the NAIC list, the carrier record, or the policy, and line of business codes do not match Applied Epic codes.
How we handle it: Carrier names are resolved from the NAIC name first, then the carrier name, using the numeric NAIC code. Companies and lines of business are exported with a blank new-code column for your team to fill in, and carrier rules can be made conditional on line of business or package.
Service roles and account settings
Applied Epic expects service roles and account-level settings that EZLynx does not store in the same form.
How we handle it: Service roles are mapped separately for commercial and personal accounts at both client and policy level (for example account manager, personal lines producer, and commercial lines producer), alongside organization and client configuration values your team approves.
Attachment files without a matching record
The attachment files on disk and the attachment records in the database do not always line up.
How we handle it: We scan the delivered files into an inventory, match them to attachment records, and flag files with no record as orphaned in the data-quality report so your team can decide what to do with them.
The Process
How the EZLynx conversion runs
Every engagement follows our seven-stage Applied Epic conversion process. For EZLynx the work concentrates in four places:
- Pre-run audits on the EZLynx data: the date window in scope, missing applicants or carriers, and duplicate or orphaned activities.
- OldNew extraction into review workbooks covering clients, policies, contacts, activities, attachments, and mapping tabs for your team to confirm.
- Client load, lookup-code matching against the Applied Epic import results, and checks before the remaining loads (for example accounts with blank names).
- Import of policies, activities, and attachments, then exception resolution, reconciliation, and first-run verification.
For the full service scope, see Applied Epic data conversion services; for how import files are built, run, and reconciled, see Applied Epic BOB import preparation.
Moving an EZLynx agency onto Applied Epic?
Tell us what you have from EZLynx and we will tell you what the conversion will require.
Deliverables
What you receive
Related
Converting more than one agency?
EZLynx agencies are often one source among several in an acquisition pipeline. Our agency acquisition data migration work treats each source system as a repeatable conversion. Related source-system pages: HawkSoft to Applied Epic conversion and QQCatalyst to Applied Epic conversion. Terms are defined in the Applied Epic conversion glossary.
FAQ
EZLynx Conversion Questions
Can you convert EZLynx attachments into Applied Epic?
Attachments can be in scope. We inventory the attachment files delivered with the data, match them to EZLynx attachment records, and report orphaned files and match results before anything is loaded.
How are personal and commercial accounts kept apart?
EZLynx stores them in separate tables with separate IDs. We keep the distinction from extraction through lookup-code matching, and flag any account whose Applied Epic lookup code looks like the wrong account type for review.
What happens to EZLynx notes and emails?
Activities, activity emails, applicant notes, note activities, tasks, and claim entries are combined into Applied Epic activities. Note text is cleaned of HTML and embedded links and trimmed to the length the import accepts.
Who decides how carriers and lines of business map?
Your team does. We export every carrier and line of business actually in use with a column for the Applied Epic code, and apply the mapping you approve.
What if an EZLynx client cannot be matched to an Applied Epic lookup code?
It stays unmatched and goes on a review list. We would rather leave a record for a decision than attach history to the wrong account through a loose name match.
More questions? Read the full Applied Epic Conversion FAQ.
Bring Us the Backup. We Will Help Carry the Conversion Across the Finish Line.
Whether you need overflow capacity for one acquisition or a repeatable conversion partner across an active pipeline, we'll help you define the scope, inspect the source data, and build a practical path into Applied Epic.
Built for insurance agencies, brokerages, aggregators, and acquisition teams that need experienced conversion capacity without building another internal department.