Core replacement has a bad name in insurance. Most CEOs and COOs have seen a programme run years late and well over budget, then go live with the same products on a newer screen. The board has usually seen one too.
The real choice is rarely "replace or do nothing". There are three paths. Each fits a different position, and many insurers end up using more than one over time.
The three paths
Launch
Starting a new insurer or a new line
When it fits
You hold a new licence, are entering a new market, or are launching a line your current system was never built for.
What you do
Build the line on Ubiquity from day one. Products, rating, underwriting rules and regulatory returns are set up for that market. Nothing has to be migrated.
Watch for
Agree reinsurance treaties, bordereaux and finance postings early. They decide go-live more often than the policy screens do.
Modernise
Keeping the core, changing what sits in front of it
When it fits
Your policy admin system is stable and paid for, but brokers, agents and bank partners wait days for quotes and endorsements.
What you do
Put Ubiquity in front of the existing core for quote, bind, endorsements and first notice of loss. The core stays the system of record and Ubiquity talks to it through APIs.
Watch for
Be clear about which system owns each piece of data. Two systems that both think they own the policy will cost you at year end.
Move
Replacing an ageing core
When it fits
Product changes need vendor releases, regulatory returns are pieced together in spreadsheets, and support for the old platform is thinning out.
What you do
Move line by line. New business goes on Ubiquity first and renewals follow. Mature books stay where they are until they run off or are migrated.
Watch for
Do not migrate everything at once. Prove one line in production, then move the next.
Questions to answer before an insurance core replacement
Put these to your operations, underwriting, finance and IT leads. Where the answers disagree, that is usually where the problem is.
- How long does a new product or rate change take today, from pricing sign-off to live?
- Which lines are growing, and which are closed or in run-off?
- Who owns underwriting authority today, and how is it recorded and audited?
- How are regulatory returns produced: by the system, or by people with spreadsheets?
- How many days does month-end close take, including reinsurance recoveries?
- What do brokers and partners complain about most: speed of quote, endorsements, or claims updates?
- What does the current vendor charge for change, and how long is the contract left to run?
What to move, and what can stay
Move first
- Policy administration for new business and renewals
- Rating and underwriting rules, with authority limits recorded
- Claims, from first notice of loss to settlement
- Broker, agent and bank partner channels
Can stay, for now
- Closed books and business in run-off
- Your general ledger, fed by clean postings
- Specialist systems you choose to keep, linked by API
Where Ubiquity fits
Agilis Ubiquity supports all three paths on one platform. It covers General, Life, Health, Pensions & Annuities and Takaful, with each market's regulatory rules, taxes and reporting configured for that market. You can start with one path and move to another later without changing platform.
Customer announcement · 12 October 2026
Insurance Corporation of Belize selects Agilis Ubiquity and Agilis Sentinel
An Agilis Core Insurance Suite customer for more than three years, ICB is moving to Ubiquity for its next generation of insurance operations. Go-live is planned for Q1 2027.