From AMS360 or Applied Epic to Expert Insured: Go Live Now, Sunset Later
You do not need a risky one shot migration to move from a closed agency system into Expert Insured.
Run both systems in parallel, start issuing and servicing in Expert Insured, and sunset the legacy system once operational data lives in EI. We will discount EI during the overlap so you do not pay twice.
Why parallel beats big bang
Closed systems make full data extraction slow and unpredictable. A parallel approach avoids downtime and lets your team learn EI while the legacy system stays available for history and lookups.
Benefits of parallel
- No operational risk if an export is incomplete
- Teams learn EI on real work while old records remain accessible
- You can phase carriers, lines, or branches at your own pace
- Clean data grows in EI from day one
What moves first
Focus on live work. Let history sit until you actually need it.
- Active submissions and quotes
- Create new submissions in RQB
- Use appetite rules and API rating to avoid rekeying
- New binds and all future endorsements
- Issue policies from EI
- Use the Forms Engine for bind packs and endorsements
- All renewals coming due
- Pull expiring accounts into EI
- Run your renewal cadence and remarketing from EI
- Operational artifacts
- COIs, service tickets, audit notes, and email trails for accounts now living in EI
What to keep in the legacy system
- Historical policies and documents not needed for day to day
- Accounting history that is easier to reference than to convert
- Old report layouts that are not worth rebuilding
Keep logins for a small team during the overlap. Shut down only after a few renewal cycles.
Practical data plan
Minimal viable data to seed EI
- Account and contact basics for in flight and renewal cases
- Current term policy details when the policy will be serviced in EI
- Key documents you need regularly: dec pages, endorsements, certificates
How to bring it in
- CSV or report exports for accounts and contacts
- Targeted document pulls for active or renewing policies
- Manual key fields for a limited set of high value accounts where exports are not possible
This keeps scope small and impact high.
Timeline you can trust
- Week 1: Pick first line and carrier, enable RQB rating, create submissions in EI
- Week 2: Issue first set of policies in EI, begin renewal cadence in EI
- Week 3: Move COIs and service work for those policies into EI
- Week 4 and beyond: Add more carriers and lines, continue renewals, shrink legacy usage to lookup only
Finance note
You should not pay double while you sunset.
We will discount Expert Insured during the parallel period so your combined cost stays neutral until the legacy system is turned off.
What success looks like after 90 days
- All new business, endorsements, and renewals are in EI
- Legacy logins used only for lookups or rare audits
- Service tickets, COIs, and documents created from EI
- Unified analytics in EI for cycle time, SLA, and policy quality
FAQs
Do we need a full data migration to start?
No. Start with live work in EI and bring history only when needed.
What about accounting and commissions history?
Leave detailed historical accounting in the legacy system during the overlap. EI will handle accounting going forward for new and renewing policies.
How long should we run both systems?
Two to three renewal cycles is typical. Retain read only access to legacy data if required by your audit policy.
What if we cannot export some fields?
Enter key fields manually for a small set of high value accounts. Do not delay the program to chase perfect exports.
Next step
Launch your first program in Expert Insured, keep legacy for lookups, and turn it off when you are ready.
