Moving to ClaimCore
Your old system keeps running until you are satisfied.
The most common reason firms stay on software they dislike is not the software. It is the thought of moving four thousand live claims out of it while continuing to run a business.
The honest version
That fear is rational. A migration goes wrong in four specific ways: data arrives wrong and nobody notices until a claim goes out with the wrong figure on it; data does not arrive at all because a field was quietly dropped; there is no way back once the switch is thrown; and the business stops for a week while it happens.
Every one of those is addressable in advance, and the process below is built around addressing them rather than around being fast.
The Migration Centre is included at every tier. We do not price migration “on analysis, payable upfront” with the figure left blank, and we do not ask for it before you know the number.
Seven stages
- 01
Discovery
A look at a sample export — fifty claims is enough. We establish what system you are on, how much you want to bring, which fields matter to you, and what lives outside the system entirely.
From you: A sample export, and half an hour with whoever knows your current system best.
- 02
Extract
Most systems export to CSV or Excel. Some make it deliberately awkward. Where yours will not produce a clean export we quote extraction in days, agreed in writing before any work starts.
From you: A full export, once you are ready. Documents are handled separately and usually later.
- 03
Map
Your columns to ClaimCore's fields. Anything you do not map is listed explicitly as unmapped rather than silently discarded — that list is the review, and it is where 'the old system had a field for that' gets said while it is still cheap.
From you: An hour to read the unmapped list.
- 04
Validate
Every row checked against the field rules, with errors reported per row and the reason for each. Row 1,847: date of birth is 31/02/1987. You fix them at source or accept them as known exceptions.
From you: Decisions on the exceptions.
- 05
Rehearse
The import runs end to end and changes nothing. You get the counts of what would be created, the full exception list, and a duplicate check against references you already hold. Run it as many times as you like.
From you: A morning reading the output. Nobody should commit a migration they have not already watched happen.
- 06
Commit
The batch imports and is recorded, so what came in and when stays answerable. Documents follow, matched to their claims.
From you: The decision to proceed.
- 07
Verify
Counts reconciled against your source, financial totals compared, and a sample of claims opened side by side with the old system. Done with you, not reported to you.
From you: An hour to check it with us.
Nothing is irreversible until stage six, and your existing system is untouched throughout. We will never ask you to decommission it before you are satisfied.
What usually goes wrong
The old system will not export cleanly
Common, and occasionally deliberate on the vendor’s part. Quoted in days, agreed in writing before any work starts. Never open-ended.
A field has no equivalent
Surfaced at mapping, before anything is imported. Usually the answer is a field you had not spotted; occasionally it is genuinely lost, and we say so rather than dropping it quietly.
The data is dirtier than anybody expected
It always is. That is what validation is for — errors row by row with the reason, so nobody has to clean a spreadsheet blind.
The team does not adopt it
The real risk, and not a technical one. Phased go-live so nobody faces the whole book at once, training in the week they start using it, and an administrator inside your firm who can change things without raising a ticket with us.
How long does it take?
Three weeks for a firm coming off spreadsheets. Five or six for an existing book with a normal amount of mess. Longer for unusual source data or a phased go-live by branch. Your proposal states the schedule.
Do we have to move everything?
No, and most firms do not. Open claims plus the last two years is a common choice. The old system stays available for anything older.
What about our documents?
Scanned PDFs, photographs and signed agreements migrate as a bulk transfer matched to claim references, after the claim data is in. It is usually the larger job and it is planned separately.
Can we go live gradually?
Yes, and it is what we recommend. New claims are created in ClaimCore from day one while the back book migrates behind you, so the team learns on a handful of fresh claims rather than on four thousand at once.
What does assisted migration cost?
It is priced by claim volume and quoted after we have looked at your data — before you commit to anything. The self-service Migration Centre is included at every tier if you would rather drive it yourself.
What if it goes wrong?
The rehearsal stage exists so that it does not. It runs the entire import and changes nothing, as many times as you want, and you see exactly what would be created before anything is.
Send us fifty claims and we will tell you honestly what will migrate cleanly.
Before you commit to anything, and before we quote you for anything.