You bought the book. Now you have to integrate it.
If you're growing by acquisition, the risk isn't the price you paid — it's the months that follow. Every book arrives in a different system, with different files, and renewals don't wait for your migration. Amparo reads whatever files the acquired firm hands over, in whatever format, and tags every policy with the acquisition it came in on — so two years later you can answer whether that deal worked.
If this sounds familiar
- Every firm you buy runs a different system — or a spreadsheet.
- Migration takes months, and renewals keep falling due throughout.
- Nobody can say how the book you bought two years ago is performing.
- Commission terms for the acquired firm's agents were negotiated case by case.
What Amparo does in this case
The acquired book arrives however it arrives — PDF, CSV, an export from an old system. It gets read, not hand-converted. Every line keeps what was written and how confident the reading was, so someone can check before trusting it.
Every policy knows which acquisition it came in on. The book can be analysed by origin — premium, commission, claims, retention — without cross-referencing spreadsheets. This has to be stamped at import: once policies have been edited, it can't be recovered.
The moment policies land, their end dates land with them. Renewals surface by urgency with the premium at risk, including suspended policies — which still lapse, and are the easiest to lose.
Acquired agents keep their own percentages. Splits cascade down the real chain with per-agent overrides, rather than one global rate applied to everyone.
How it runs
- 01Receive the files
Whatever the acquired firm has. There's no format to demand and no converter to build.
- 02Read and stamp the origin
Policies, clients and terms are extracted and tagged with the acquisition.
- 03Review what isn't clear
Low-confidence lines go to review. Nothing enters the book as fact without being looked at.
- 04Work the renewals
The expiry list is ready before the migration is finished.
What Amparo doesn't do for you
- Acquired-book import is on the roadmap, not built — statement reading works today, but the dedicated migration tool doesn't exist yet.
- We don't do due diligence or book valuation for deal negotiation.
- There's no integration with the acquired firm's system; we work from whatever files it can export.
We say this on the product page because finding it out in the third meeting is worse for both of us.
Questions
It depends on the state of the files, and we won't invent a number we haven't measured with a customer. What we can say is what it replaces: there's no connector to build per source system, because the file is read rather than mapped. Human review of the doubtful lines is still work, and that's where the time goes.
Bring a month of statements. We'll compare against your system.
If we don't find differences that justify the cost, you'll know that in a week — without spending a project to find out.