From Excel to FLIORE: migration in ordered steps
Updated: 2026-09
Migration from spreadsheets rarely fails on the import but on the state of the data beforehand. The ordered route is: one mandate first, clean up before exporting, run parallel briefly, then sign off and bring the rest across.
The most common reason a practice stays in spreadsheets is not satisfaction but fear of the migration. That fear usually attaches to the technical import — which is the easiest part.
The hard part comes before. Spreadsheets grown over years contain positions with no clear attribution, entities that formally no longer exist, valuations with no as-of date, and formulas whose purpose nobody can confidently name. These questions have to be answered — not because of the new system, but because they are open anyway.
The second mistake is the big leap. Migrating all mandates at once leaves no reference and no way back if something goes wrong. Migrating one mandate first costs barely more time, surfaces the peculiarities of your structure early, and limits the risk to a manageable slice.
How it works
- 01
Choose a pilot mandate
Not the simplest and not the most complex, but a representative one — so the findings transfer to the rest.
- 02
Clean the spreadsheet before exporting
Resolve positions without attribution, mark dissolved entities, give valuations an as-of date. This work is due anyway; migration only makes it visible.
- 03
Export CSV and have columns mapped
FLIORE maps the columns automatically: entities become mandates, holdings become assets. Review the mapping before committing.
- 04
Add structure and beneficial owners
Capture ownership relations between entities, beneficial owners and their jurisdiction — the part a spreadsheet typically never contained at all.
- 05
Run parallel briefly and reconcile
Use both routes for one reporting cycle and compare the results. Discrepancies are almost always informative and usually rooted in the legacy data.
- 06
Sign off and bring the rest across
After signing off the pilot, migrate the remaining mandates — with the findings from the first run it goes considerably faster.
Why it fits here
FLIORE names CSV as the migration path with automatic column mapping; entities become mandates and holdings become assets. Most teams are running the same day.
Data-quality reconciliation shows after import exactly the legacy issues that were invisible in the spreadsheet — missing FX rates, stale valuations, feed errors ranked by severity.
What a spreadsheet never contained — ownership relations, UBO assessment, deadlines, audit trail — is provided for in the data model and need not be improvised.
FAQ
How long does a migration take?
The import itself is quick. Actual duration depends on the state of the legacy data and how many open questions the grown spreadsheet contains.
What happens to our grown formulas?
The product covers the calculation logic. Anything that must stay bespoke should be named before migrating — the most honest checkpoint of any implementation.
Can we migrate mandate by mandate?
Yes, and that is the recommended route. A representative pilot mandate first, then the rest.
Which sources can be imported?
Spreadsheets, and exports from other platforms such as Asora, Kubera, Addepar or Altoo, each via CSV with automatic column mapping.
What if the figures differ after import?
Discrepancies are the most useful part of a migration. They almost always come from the legacy data — missing rates, unclear as-of dates, double entries — and would otherwise have gone unnoticed.
FLIORE
FLIORE names CSV as the migration path with automatic column mapping; entities become mandates and holdings become assets. Most teams are running the same day.
Data-quality reconciliation shows after import exactly the legacy issues that were invisible in the spreadsheet — missing FX rates, stale valuations, feed errors ranked by severity.
What a spreadsheet never contained — ownership relations, UBO assessment, deadlines, audit trail — is provided for in the data model and need not be improvised.