Agency Management System Implementation Checklist

Phase 1: Before you sign

Write down what must work on day one. Servicing a policy change, issuing a certificate, quoting new business, logging a lead, and processing a commission statement are typical.
Get your all-in cost on paper. Include setup, migration and email fees, plus any third-party contracts you will still need. See what to expect on pricing.
Confirm data ownership and export rights in writing.
Name one internal owner. Someone in your agency must make decisions quickly. Without one, every question waits.

Phase 2: Inventory your current data

Find out what your current system can export: clients, policies, notes, documents, open leads and commission history.
Decide what has to move and what can stay in the old system as a read-only archive.
Clean obvious problems first: duplicate clients, expired policies that were never closed, and inconsistent carrier names.

A good vendor will start from your actual export and list exactly what comes across. That is how we work at DarkHorse AMS, and it's described on our page about switching systems. If you are moving from a specific system, the pages for Applied Epic, AMS360, HawkSoft, EZLynx and AgencyZoom have a worksheet for the right questions.

Phase 3: Map and trial import

Map fields. Line-of-business names, carrier names, policy statuses and producer names rarely match one for one. Build an explicit mapping and flag anything that doesn't fit rather than guessing.
Run a trial import into a test environment and compare counts: clients in versus clients out, policies in versus policies out, open leads in versus open leads out.
Spot-check records. Open twenty clients at random and compare them to the old system line by line.

Phase 4: Integrations

Carrier downloads. Request or re-establish IVANS download connections early because carriers can take time to enable them. See what IVANS is and how downloads work.
Quoting tools. Confirm which carriers and lines the rater covers and which third-party contracts (for example, your own Quotamation or Bold Penguin agreements) you need.
Email and phone. Set up agency email, signatures and any call integration before go-live, not after.
Branding. Add your logo, colors and agency name so staff and clients see your agency throughout.

Phase 5: Users, roles and training

Create each user, assign a role and confirm what each can see and change.
Set up producer records and commission split rules. Our guide to reconciling commission statements shows what those rules need to cover.
Train by task, not by menu: have each person do their five most common weekly jobs on test data.
Write a one-page cheat sheet for the questions you expect in the first week.

Phase 6: Parallel run

Freeze changes in the old system on a chosen day, then do the final import.
Keep the old system read-only for a week or two so staff can look things up.
Reconcile a full commission cycle between old and new numbers if producers are paid from them.

Phase 7: Go-live and first thirty days

Pick a quiet week, not a renewal peak.
Hold a short daily check-in for the first week and log every problem in one place.
Re-check counts after the first renewal cycle and confirm carrier downloads are arriving and matching.
Decide a date to cancel the old system once you have confirmed you've exported everything you need.

Who does what

Write a short responsibility list before kickoff. The agency owner approves scope and the go-live date. The internal project owner answers questions and signs off on the trial import. Each department lead (sales, service, accounting) confirms that their five most common tasks work. The vendor owns the technical setup, the import and the integrations. When everyone knows which of those they are, decisions stop waiting in someone's inbox.

How long should it take?

Timelines vary with the size of the book, the cleanliness of the data and how many carrier connections have to be activated. Ask the vendor for a written schedule with dates for the trial import, training and go-live, and ask which of those dates depend on actions by the agency or by carriers. A schedule you can't see is a schedule that slips.

Common reasons implementations stall

Three causes show up repeatedly: nobody in the agency owns decisions, the data wasn't cleaned before import, and integrations were left until the last week. Handle those three and most of the rest takes care of itself. For the wider buying decision, see our nine questions to ask first and the comparison guide, or book a demo to walk through a plan for your agency.

Agency management system implementation checklist: from signed to live