Policy calculation estate
Business rules distributed across programs, jobs and production history.
Data and code migration
for insurance leaders.
We extract, modernise, and migrate; with every rule accounted for and every record validated.
80%cost reduction
50%faster delivery
100%CH data centres
100%your IP
Turn your legacy data into a competitive moat.
Bring us in before your institutional knowledge decays further.
Step 1
Discovery
Capture what lives in people's heads
We interview your domain experts and reverse-engineer decades of undocumented decisions before they walk out the door.
Step 2
Migration
Move forward without losing the past
We migrate your data and modernise your code with zero-loss precision — every business rule accounted for, every edge case tested.
Step 3
Insight
Turn legacy data into business intelligence
We structure and surface your historical data as analytics and reports your actuaries and executives can actually use.
Technically correct is not enough
Has your data strategy become a business risk?
Migration workbench
From estate to evidence.
A working illustration.
01Capture
02Rebuild
03Validate & govern
- Program lineage
- Calculation variants
- Affected policy history
Which rules belong in the target — and which are accumulated workarounds?
Technologies We Modernise
We have deep expertise in legacy applications.
So you can focus on your target state.
Mainframe
z/OS
COBOL
IMS
PL/I
Assembler
IBM AS/400
RPG
Progress OpenEdge
Databases
VSAM
DB2
Adabas
Oracle DB
MSSQL
FoxPro
Excel
HOW WE HELP
How we help, in the order you usually ask for it.
Each service is commissioned standalone or as part of a wider migration programme. Most clients start with a data migration and add code modernisation as the scope becomes clear.
DATA MIGRATION
A unified, auditable data foundation your systems can act on.
Legacy policy data extracted with full temporal history preserved, validated against source across the whole timeline, so nothing rests on a flattened snapshot.
WAYS THE WORK COULD OPERATE
Choose how much of the method you want to own.
The estate, access model and internal capability shape the operating relationship. The material decisions stay visible in every version.
Bring the estate. Keep one accountable path through the work.
A working model for organisations that want Qubiz to carry the migration activity while business and engineering owners retain material decisions.
Possible Outcomes
The Reconciliation Files
Happening every day in financial services —
told by the people who had to put their name on the number.
FILE 01
CHIEF ACTUARY · SWISS LIFE & PENSIONS INSURER
The Ghost in the Stored Procedure
One undocumented change to a 30-year-old NPV calculation put six years of technical reserves — and my signature — on the line.
Open file →
Talk to an Expert
Speak with someone who has sat across from an underwriter.
Every insurance engagement starts with the underwriting workflow, the actuarial hypothesis, and the model-risk framework — not the technology stack. No discovery decks, just an honest conversation.
Book a scoping call
25+ years across IT domains. Lead Architect at Zurich Insurance, Helvetia, Swiss Re, Munich Re, Helsana.
FAQ
We take out the guesswork.
01What kinds of data and code problems can Qubiz take on?
Bring software that is hard to change, data that cannot support a decision, systems that disagree or a release whose evidence is not strong enough. Bring the situation as it is, not a solution written in advance.
02Do we need a legacy system for this to apply?
No. The same work can begin with a modern application, a platform decision, post-merger complexity, a data foundation or a new custom software need.
03Is this another platform we must license or operate?
No. The method belongs in the engineering work. The intended result is software, data and understanding that stay with your organisation.
04Where does AI fit in the work?
AI can accelerate reading, comparison, reconstruction and drafting. Business meaning, architecture, material differences and release decisions remain with accountable people.
05What must our team contribute?
The business outcome, access to the relevant estate and the people who own its meaning, constraints and acceptance decisions.
06What do we keep when the engagement ends?
The intended package is the working code or data change, reviewable requirements, tests, evidence and recorded decisions the next team needs.
07Can Qubiz work inside our environment?
That depends on the system, its security boundaries and who owns the decisions. Those conditions belong in the first conversation.
08How does a first conversation work?
Bring what must change, what cannot be lost and what nobody can explain today. We will start there and decide whether Qubiz is the right engineering partner.