Move your book in weeks, not a quarter.
The question every firm asks first, so here is the whole answer: what comes across, how, how a migration runs, and what we agree before a single record moves.
The ways in that exist today.
Nothing on this list is planned or promised. Each one is in the product now, under Settings, Import, or Integrations.
| From | What Bloom reads | How |
|---|---|---|
| Your cashflow tool | Clients and partners with addresses and contact details, and their pensions and investments. | If it is one Bloom links to directly, connect it from Integrations and choose the households to bring across; provider names are recognised and filled in. Otherwise export and upload. |
| Your back-office system | Clients, with the fields the export carries. | Export your clients as a CSV and upload it. Bloom shows what will be imported before anything is saved. |
| Any CRM, by spreadsheet | Clients, policies, assets and liabilities, addresses and review dates. | Five separate imports from CSV or Excel. Map the columns, check the validation, resolve duplicates, then import. Re-importing updates values instead of creating a second record. |
| Provider statements | Pensions, ISAs and GIAs with their current values. | Drop the statement on the client, scanned or handwritten. Bloom reads it and proposes the policy; you tick what is right. |
| Gmail and Outlook | Client emails, filed against the record. | Connect the mailbox once. Emails match to clients by address, and soft facts can be proposed from the history. |
| AJ Bell, Transact, Aviva | Live valuations after the move. | Platform feeds keep the imported policies current, so the first review after switching uses today's figures. |
Using something else? Every CRM exports a spreadsheet, and the spreadsheet imports take any column layout. Send us a sample export and we will tell you what maps before you start.
Five steps, with you on the call.
The imports are self-serve, so a one-adviser firm can do all of this alone in an afternoon. Larger books, we do with you.
- 01
Agree the source and the scope
Which system is the source of truth, which clients come across (all, or active only), and what stays behind. One call, about an hour.
- 02
A sample first
Five clients, imported and checked together against the old system: names, dates of birth, policies, values. Anything odd is fixed in the mapping before the full book moves.
- 03
The full book
Clients first, then policies, then assets and liabilities. The imports ask who each client belongs to, flag repeated names, and report what really happened.
- 04
Feeds and mailboxes on
Platform feeds and Gmail or Outlook connected, so values and emails start arriving before anyone has to type anything.
- 05
Go-live checks
Client and policy counts compared with the old system, a handful of records opened side by side, then a date on which the old system goes read-only.
What is settled before any record moves.
Most migration trouble comes from decisions nobody made. These are written down on the first call.
- The source of truth during the overlap. Until the old system goes read-only, one of the two is the record, and everyone knows which.
- Who owns each imported client. The imports ask, so no client lands without an adviser.
- What happens to duplicates. Repeated names are flagged for a decision, never merged by guesswork.
- What stays behind. Archived clients, dead leads, and documents that no longer need to be kept.
- The read-only date. The day the old system stops being written to, so the overlap has an end.
Export any time. No lock-in.
Your client data can be exported whenever you want it. It is stored in London, each firm's data walled off from every other firm's at the database level. Read the security page.
Send us a sample export.
We will tell you what maps, what needs a decision, and how long your book would take, before you commit to anything.