Core-system projects are commonly organized around configuration, interfaces, data conversion and a launch date. For an MGA, each of those tasks can change how delegated authority is exercised. A field default, rating rule, referral trigger or endorsement workflow can alter the portfolio even when the software performs as designed.
Lloyd’s standards and delegated guidance emphasize consistent reporting and ongoing accountability. That obligation does not pause during transformation. The organization must know which system, rule set and evidence applied to each risk throughout the transition.
Define migration cohorts
New business, renewals, endorsements, cancellations and open claims may move on different schedules. Each cohort needs a clear system of record, authority version, reconciliation method and fallback process.
A “big bang” can reduce dual operation but increases the consequence of hidden defects. A phased approach limits exposure but creates interfaces and inconsistent experience. The choice should be made against underwriting and service risk, not project convenience alone.
Reconcile meaning, not just records
A successful record count does not prove equivalent coverage, pricing or portfolio classification. Testing should compare consequential outputs on representative risks, including missing data, referrals and unusual endorsements.
Historical fields may have been used differently across teams. Migration is an opportunity to resolve those meanings, but changes must be versioned so prior decisions remain interpretable. Rewriting history to fit a new schema can destroy evidence.
The countercase: perfect parity preserves bad process
Requiring the new system to reproduce every legacy behavior can import the complexity the migration was intended to remove. Some controls and workflows should change.
The distinction is intentionality. Leaders should approve which underwriting behavior changes, why, for which cohort and with what monitoring. Accidental change is a migration defect; deliberate change is portfolio management.
Treat go-live as the beginning of observation
Post-launch monitoring should examine referral rates, manual workarounds, premium and coverage differences, data completeness, issuance delays and underwriter overrides. Thresholds should trigger containment or rollback before the new behavior compounds.
A core migration is complete only when the organization can reconcile portfolios, explain changed decisions and retire the legacy dependency without losing evidence. Technical availability is necessary. Controlled underwriting continuity is the actual outcome.
Questions for the room
- Which cohort could exist in two systems with different authority?
- What historical meaning would be lost during conversion?
- Which post-launch signal would cause us to stop or roll back?
Sources and methodology
This analysis draws on the public sources below. Company-specific disclosures are treated as examples, not market-wide evidence. Interpretation is MGA Index’s own.
1 Lloyd’s — Coverholder Reporting Standards 2 Lloyd’s — Delegated Underwriting Guidance 3 AM Best — Performance Assessment for Delegated Underwriting Authority EnterprisesMGA Index Newsroom
The MGA Index Newsroom produces independent reporting and analysis for leaders across the delegated insurance market. Our work connects public evidence to the operating and strategic decisions facing MGA leadership teams.
Newsroom analysis distinguishes reported facts from interpretation and identifies the public sources supporting material claims. Relevant relationships or potential conflicts are disclosed with the coverage.
Editorial standards and corrections