Most agencies begin considering a new agency management system for a practical reason. The current platform has become limiting, costs have increased, or another system appears to be a better fit for the agency’s future.

Any of those reasons can justify a change. The success of that change depends on how well the agency prepares for everything surrounding the technology.

An AMS migration affects data, accounting, workflows, carrier connections, reporting, training, and day-to-day responsibilities across the agency. The agencies that prepare for those pieces early have a much smoother transition.

Clean data gives the new system a better start

A conversion moves the data included in your migration scope. It cannot interpret why that data was entered a certain way or determine which records your agency still needs.

If three people entered the same commercial client three different ways over eight years, the conversion process may see three separate clients. Duplicate parent and writing companies can create even more complicated reconciliation problems. Inactive clients, outdated carrier codes, and former employees attached to active records may also move into the new system.

These issues are common in agencies with years of history and multiple people entering data. They are also much easier to resolve before the conversion begins, while your team still understands the records and can make informed decisions quickly.

The validation period will identify many inconsistencies, but it arrives during an already demanding stage of the project. Your team is learning the new system, testing workflows, reviewing converted data, and preparing for cutover. Cleanup decisions that were manageable several months earlier can become project bottlenecks when the go-live date is approaching.

The validation period works best when it confirms decisions your agency has already made. Review duplicate records, inactive users, carrier codes, company relationships, and other known problem areas as early as possible.

Your accounting does not convert with the rest of your data

This is the one that surprises agencies most often, and it is why my team gets called into conversions that are already underway.

Your historical accounting records do not move into the new system with your client and policy data. The chart of accounts must be mapped and established, opening balances must be entered or imported, and the supporting accounts receivable and accounts payable detail must be rebuilt in the new system. Your general ledger history and prior reconciliations remain in the legacy platform for future reference.

Accounting therefore needs its own transition plan and timeline.

Before cutover, your agency should have reconciled bank accounts, reviewed and aged receivables, documented commission structures and producer splits, and decided how opening balances will be established. You also need to identify who will reconcile the new system and make sure that person receives accounting-specific training before the transition.

Your accounting cutover and operational go-live do not have to happen on the same day. Separating those milestones can give the accounting team a clean period to close the old system, establish the new one, and verify that everything balances.

Treat accounting as a separate workstream from the beginning. Discovering that distinction halfway through the conversion creates exactly the kind of pressure the agency was trying to avoid.

Decide how much history you need

The amount of historical data included in a conversion can affect both the project cost and complexity.

Some vendors include a baseline number of years and charge additional fees for older data. Others limit which types of historical information they can convert. Ask for those details before you begin comparing proposals.

“Bring everything” may feel like the safest answer, but it should still be an informed decision. Consider how often your team accesses older notes, activities, attachments, and policy records. Then weigh those operational needs against your agency’s E&O exposure and record-retention requirements.

Legacy read-only access may also influence the decision. If the old system remains accessible for an appropriate period, your team may not need every historical record converted into the new platform.

Document workflows before rebuilding them

Most agency workflows are a combination of written procedures, system configurations, and habits that have developed over time.

A certificate request may move through three people in a particular order. An endorsement may trigger an activity that only one department knows how to close correctly. A producer may rely on a custom field that nobody else realizes is important.

Document those processes before the conversion begins. Your team cannot rebuild a workflow it has never fully defined.

This review also gives the agency an opportunity to decide which steps still serve a purpose. Some procedures exist because the current system required a workaround. Others may have been added years ago and never reconsidered. A new AMS should support the way your agency needs to operate now.

Start with the processes your team performs most often or those with the greatest E&O implications:

• New business
• Renewals
• Endorsements
• Certificates
• Cancellations
• Claims
• Client and policy documentation
• Accounting handoffs

For each process, identify who owns it, what information is required, what triggers the next step, and how completion is documented.

The project needs a team and someone to wrangle it

An AMS conversion has too many moving parts for one person to manage alone. Different people inside your agency understand different parts of the business: data, accounting, workflows, system administration, training, and executive priorities. The software provider will have its own team as well, typically a project manager, data implementation specialist, system trainer, and salesperson.

Your agency needs a project team that can match that structure, along with one dedicated resource to keep everyone moving in the same direction.

That person is the project wrangler. They schedule calls, coordinate training, track deadlines, document decisions, and make sure every meeting’s homework gets completed before the next one. They do not necessarily need to know every answer, but they do need to know who does and be persistent enough to get it.

The system administrator or executive assistant may gather the details. Department leaders may explain existing workflows. The owner or another executive may make the final decisions. The wrangler connects those people and keeps unanswered questions from bringing the conversion to a standstill.

How many years of notes are coming over? Will the custom fields convert? Who needs admin access? Who approves the data mapping? Each question may seem small, but together they can quietly add weeks to the timeline.

If your agency does not have someone with the authority, calendar space, and follow-through to wrangle the project, identify that before you sign. Otherwise, unresolved homework and missed handoffs can drag the conversion straight into your busiest season.

Choose the quietest practical go-live window

The best conversion window is often the least interesting month on the agency calendar.

Start with your renewal cycles. An agency with a large January 1 book should avoid a December go-live. The same applies to agencies with heavy July 1 renewals or other seasonal peaks.

Then look at the accounting calendar. Month-end and year-end already require concentrated attention, and the accounting team will need time to establish and verify the new system.

Also consider employee vacations, planned acquisitions, office moves, major client commitments, and other projects competing for the same people. A technically available date can still be a poor operational choice.

Late February or September may work well for some agencies. The right window is the period when your team has the most room to learn, test, and resolve issues without compromising client service.

Plan for legacy-system access

Include read-only access to the legacy platform in the conversion agreement and budget for any continuing license fees.

Twelve months is a reasonable target for many agencies. Six months can feel surprisingly short once the team begins working in the new system.

Historical questions will continue after go-live. Someone may need information about an endorsement completed several years earlier. A claim may involve a policy that predates the conversion. Accounting may need to research an older transaction.

Confirm how long the old platform will remain available, what information users can access, how many people will retain access, and what the vendor will charge.

Start with a readiness review

Changing your AMS is a rare opportunity to improve the agency’s underlying operations. With the right preparation, the project can leave you with cleaner data, clearer workflows, stronger reporting, and more consistent processes.

That work begins well before cutover.

If your agency is evaluating a change, use the AMS Migration Readiness Checklist before signing an agreement. It covers:

• Data condition and cleanup
• Accounting and cutover sequencing
• IVANS and carrier downloads
• Integrations and connected tools
• Reporting requirements
• Workflow documentation
• Project ownership, training, and timing

Angela Kristensen, CAO

angela@linchpininsurtech.com

Need help with your migration?

Linchpin supports independent agencies through AMS planning, conversions, optimization, accounting, and training. Our team works in Applied Epic, AMS360, EZLynx, and other agency platforms. Linchpin is a Vertafore Orange Partner and an Applied Preferred Consultant Partner, and our accounting professionals work directly inside these systems every day.

If you would like an outside perspective before committing to a system or timeline, we will review your current situation with you. You will leave the conversation with a clearer understanding of your agency’s readiness, potential gaps, and the work required for a successful migration.