Modernize the core
Your core systems are twenty years old. Your business can't wait for it to be replaced.
We modernize in stages, around the core, the systems that sustain your operation —the core systems (the central system where your rules and operations live), the financial ERP and the integrations between systems— without switching them off all at once and keeping what already works.
Prefer email? Write to us at hola@habil.mx
Trusted by organizations where continuity and security are non-negotiable
- BanCoppel
- Zurich
- Allianz
- GNP Seguros
- MetLife
- Costco
- Seguros Multiva
- Aserta
- Bx+
- Veolia
- Truper
- Argos
The risk is not the old system: it's replacing it all at once
The core systems of a bank or an insurer hold twenty years of rules, exceptions and data. That is why no one dares touch them, and every new channel gets attached to them with one more patch. A full replacement sounds clean, but it tends to be the project that absorbs the most budget and carries the most risk of cancellation. The way out is different: surround the core with a layer that speaks today's language and modernize in stages, with the core running while what is new proves that the numbers match.
- Moved over
Stage 1: policy lookup
The lowest-risk part goes first.
- Moved over
Stage 2: issuance
The previous stage is accepted first.
- Moved over
Stage 3: premium collection
The current system stays as a fallback.
- Moved over
Stage 4: claims
The core keeps running; the new is added around it.
What we often hear
"Nobody wants to touch the core systems."
IT leadershipevery change turns into a months-long project.
"The person who knew how it works has already retired."
General managementthe knowledge lives in two or three people.
"Every new product takes months to launch."
Salescompetitors launch first.
"The old system's vendor no longer provides support."
Riskthe operation depends on something no one stands behind.
"We pay licenses for an integration bus that nobody understands."
Financea fixed cost with no owner.
Digital channels, AI and business partners ask for data as it happens, and the core was not built for that. Every month you postpone, another patch is added and change gets more expensive.
Three signs we have already done it
We kept the operation of an insurer feeding its financial ERP while the ERP was being replaced, with confirmation of every submission.
We have worked on insurance core systems such as Acsel/X, SIVI, SABE and SIS/SISnet, and on IBM's WebSphere family.
Critical systems for banking, insurance and regulated companies since 2006.
What we offer
Your core system as services, without replacing its logic.
If it runs on traditional platforms such as AS/400, we turn its business functions into services your channels can call; the adjustments each interface requires are defined in the diagnosis. If it lives on Oracle —Siebel, E-Business Suite, Acsel/X, SIS/SISnet or another— we connect through its stored procedures or exchange tables, without touching its logic or its screens.A modern layer around the core system.
Your channels, partners and AI talk to the layer; the layer talks to the core system. When the core system changes, the layer concentrates the adaptations in a single point and reduces the impact on your channels.Modernization in stages: the core keeps running and the new is built around it, function by function.
We build one function at a time around the core, with controlled coexistence with what already runs and an agreed rollback.Moving off the legacy bus.
If your integrations live in WebSphere ESB, IBM Integration Bus, MuleSoft, WSO2 or Pentaho processes that nobody wants to touch, we keep them running while we move them to a layer your team can operate.Less key-person risk.
We reconstruct and document how your system works today —rules, interfaces, exceptions that only live in your experts' heads— before changing it, so that the knowledge stays in your company.Data that adds up during the change.
Reconciliation between the old and the new system while they coexist, so that no figure gets lost along the way.With operations running.
Agreed windows, testing against real data and a plan for each risk.The bridge to a platform of your own.
If what you are renewing is your offering, sales and collections, Hábil MDW already comes built for it and coexists with your core system.
How we work
First we map what exists: functions, interfaces, dependencies and what only one person knows. Then we choose the first stage —the one that hurts most or carries the most risk— and modernize it around the core with controlled coexistence. Each stage is accepted before moving on to the next.
What we've already done
From the core system to the accounting ERP, while the ERP was changing
At a global insurer, with confirmation of every submission.Two core systems kept in sync without duplicate data entry
Over the insurer's integration bus.A COBOL core system issuing digital tax receipts
Working into its programs to generate what the stamping provider requires.An insurer's core system connected to its sales CRM
So that sales could see what operations issued.
We have worked with insurance and banking core systems since 2007: we know the system you have today and how to modernize around it without stopping it.
What you receive first
Modernization map: what stays, what changes first, with what risk and what impact on the business. Your technology lead and the person who knows the system from the inside take part; it makes dependencies, operational risks and owners visible, so you can decide which stage to authorize first.
For your technology team
IBM i (AS/400) and RPG; Oracle (stored procedures, exchange tables); DB2, Informix, SQL Server, PostgreSQL; WebSphere (application server, MQ, ESB, Business Integration), MuleSoft, WSO2; insurance core systems (Acsel/X, SIVI, SABE, SIS/SISnet, Guidewire) and banking core systems; REST and SOAP APIs; events and queues (IBM MQ, Kafka, RabbitMQ); gradual modernization in stages, around the core.
What your Compliance area receives
Operational evidence for your internal reviews and for the documentation your auditor requests: the reconciliation between the old and the new system while they coexist, the record of every operation that crosses the layer, and the acceptance evidence for each stage.
Is what you are renewing sales and collections? Hábil MDW already comes built for it.
Explore Hábil MDWDo you want AI to query your core systems? The same layer is what gives AI access to your data.
Hábil AIThe layer that keeps the operation alive while the modernization happens around it
Integration and APIsFrequently asked questions
What people ask us before starting
Not necessarily. Often it makes more sense to surround them and modernize only what gets in the way.
No. Work happens in stages, with the old system running and an agreed rollback.
We reconstruct it with your team before changing anything.
Yes. We integrate through the interfaces the vendor supports.
Don't see your question?
Start by knowing what can be changed first. Tell us which system worries you to touch. In the first conversation, at no cost, we review what it does today and you leave with the map of the first stage.
Prefer email? Write to us at hola@habil.mx