Applied Epic BOB Import & Book of Business Conversion
An Applied Epic BOB import uses the Applied Epic Book of Business Import Utility to bring client, policy, and related records into Applied Epic through structured, format-exact files. We prepare and, where scoped, run and reconcile your BOB import — not just format a spreadsheet and hand it back.
What's Involved
More than a formatted file
Receiving or coordinating source data and, where needed, restoring a database backup
Extracting the relevant records from the source system or database
Mapping and normalizing values to Applied Epic's expected structure
Preserving the exact required file structure, column names, and tab organization
Dividing files according to Applied Epic's import constraints
Running the applicable BOB import tool or supporting your team through execution
Reconciling source counts against import results
Resolving failures and preparing corrected rerun files
Is BOB Import The Right Pathway?
A BOB import isn't the only way into Applied Epic
BOB Import (this page)
Structured file-based import through Applied Epic's Book of Business Import Utility. Typically used for a defined batch of records with a known structure.
OldNew Mapping
A mapping-engine approach for certain migration scenarios, translating source codes and structures to Applied Epic equivalents.
Full Database Conversion
Broader engagements spanning multiple data domains and coordinated import phases beyond a single BOB batch.
We'll confirm which pathway fits during scoping. See the full Applied Epic data conversion overview for how these compare.
Have a specific BOB file question?
Tell us about your source data and we'll tell you what the import will actually require.
Exception Handling
How common BOB import issues get resolved
Duplicate clients or contacts
Flagged during mapping and normalization, before the file is ever submitted — not discovered as an import failure.
Values that don't match Applied Epic's expected format or code list
Normalized during transformation where the mapping is clear; documented as an exception where a business decision is needed.
Records that fail the import itself
Captured from the import results, diagnosed against the source data, corrected where actionable, and included in a rerun file.
Records intentionally excluded from scope
Documented as exclusions in the reconciliation report — not silently dropped.
Who Does What
Your team's responsibilities and ours
| Your team | InsurCore |
|---|---|
| Confirm which data domains and history are in scope | Extract, map, and normalize the data into the required structure |
| Provide source access or an exported backup | Preserve exact column names, tab structure, and file organization |
| Approve business-rule and mapping decisions | Run or support the import, and reconcile every result |
| Review and sign off on the handoff package | Diagnose failures and prepare corrected reruns |
Deliverables
What you receive from a BOB import engagement
FAQ
Common Questions
What is the Applied Epic BOB Import Utility?
It's Applied Epic's Book of Business Import Utility — a structured import process for bringing client, policy, and related records into Applied Epic using files that must match specific column names, ordering, and formatting requirements.
Are you just formatting a spreadsheet for us?
No. Depending on scope, we receive or coordinate your source data, restore a database backup, extract records, map and normalize values, preserve the exact required file structure, divide files according to import constraints, run or support the import process, reconcile results, resolve failures, and prepare corrected reruns.
How do you handle failed records and import exceptions?
We reconcile every BOB import run against your source data. Failures and exceptions get documented, actionable ones get corrected, and we prepare a rerun file rather than leaving failed batches unresolved.
Is a BOB import the same as a full conversion?
Not necessarily. A BOB import is one pathway among several — see the distinction below. Which one applies depends on your source system, backup, and scope.
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.