The AMS Migration With a Hard Deadline
A 30-person agency is migrating from a 15-year-old agency management system to a cloud platform. The carrier download interfaces, accounting ledger, and 42,000 client files must move. The vendor's implementation plan calls for a 90-day cutover. The agency's operations manager, who has led every prior system change, resigns 20 days into the project. The remaining project lead is a 26-year-old account manager with strong system skills but no authority over the producers, who are refusing to attend training during renewal season. The CFO reports that the old system's accounting module and the new one calculate producer commission splits differently, and the discrepancy has not been reconciled. Two carriers have confirmed their download interfaces will not be ready by cutover. The vendor's contract has a fixed go-live date with penalty clauses but no rollback provision.
1. Should the agency proceed with the 90-day cutover? What is the decision framework?
Read the worked answer
The agency should not proceed on the vendor's calendar. The decision should be made on four tests, and the agency currently fails at least three.
Test 1 - Data integrity. Commission splits calculate differently between systems and the discrepancy is unreconciled. If the agency cuts over without resolving this, every producer statement for the first quarter will be wrong, which destroys trust in the new system and creates a compensation dispute simultaneously. This must be resolved and tested against a parallel run before cutover.
Test 2 - Carrier connectivity. Two download interfaces will not be ready. That means two carriers' policy data must be handled manually, which is exactly the kind of hidden labor that causes post-cutover service failures. The agency needs a documented manual workaround with named owners before go-live, or it needs to delay.
Test 3 - Organizational readiness. The experienced project leader is gone, the remaining lead lacks authority, and producers are refusing training during renewal season. A system migration is a change-management project, not an IT project. Without producer adoption, the agency will run two systems in parallel indefinitely - the worst outcome.
Test 4 - Contractual and financial exposure. The vendor contract has penalties for missing go-live but no rollback provision. That asymmetry means the agency bears all the downside of a failed cutover. The agency should seek an amendment: a revised go-live with a defined contingency window, a rollback or parallel-run provision, and a holdback of final payment until acceptance testing passes.
Recommendation: do not cut over in 90 days. Negotiate a phased approach - accounting and commission module first with a parallel run, then policy and client data, then download interfaces as carriers come online. Use the penalty exposure as leverage to renegotiate rather than as a reason to rush.
2. How should the agency address the leadership gap and producer resistance?
Read the worked answer
Two distinct problems need two distinct responses.
Leadership gap. The departing operations manager held informal authority accumulated over years. That cannot be transferred to a 26-year-old account manager by title alone. The agency should: (a) name an executive sponsor - ideally the owner or a principal - who chairs a weekly migration steering meeting and is visibly accountable; (b) give the project lead a written mandate with decision rights over training attendance, data validation sign-off, and vendor communication; (c) pair the project lead with a senior producer as co-lead so producers see one of their own invested in the outcome; and (d) consider a temporary contractor with prior AMS migration experience to backfill the operational knowledge that walked out the door.
Producer resistance. 'Not during renewal season' is a scheduling objection, and scheduling objections are solved with scheduling, not persuasion. Options: schedule training in 45-minute blocks outside core renewal hours; run role-specific sessions (producers learn quoting and pipeline, CSRs learn service and download); record sessions and require completion within a defined window; and tie completion to a visible, non-punitive tracker reviewed at the steering meeting. The key is to make training attendance a management expectation with a named owner, not a favor requested by a junior employee.
Also address the underlying fear. Producers resist system changes when they believe the new system will slow them down or expose their book. The agency should show them one concrete win early - faster quoting, a cleaner pipeline view, mobile access - and let the project lead demonstrate value before asking for full adoption.
Finally, build a feedback loop: a short weekly survey or open session where producers report what is not working. Resistance often shrinks when people see their objections change the plan.