05b Service · Migration
FROM

Flora

WE MIGRATE YOUR DATA TO

CollectiveAccess

Flora is a solid archival management product, full-web and responsive since 2017 (v3.5), now in v4.5 — historically published by Ever Team, then taken over by Decalog in 2016, and an independent company since 2024. For thirty years it has equipped archive services across France, Belgium, Spain and Switzerland; it supports ISAD(G), ISAAR-CPF, EAD/EAC-CPF, OAI-PMH (DC, EAD, EAC), Z39.50/SRU, UNIMARC. Some institutions wish to join the CollectiveAccess ecosystem — for source code sovereignty, to remove licensing, or to bring museum + archives + library together on a single open source platform. We migrate your base — fonds, descriptors, digitisations, vocabularies, hierarchies — to a free, full-web, standard MySQL platform.

LOCK · LICENCE OPEN
Flora licence + maintenance
0€
OPEN CODE · FREE
CollectiveAccess is GPL-licensed: no publisher royalty, MySQL database exportable at any time, international community developing the software core. You pay for managed hosting, support and development — not for a right of use.
BEFORE
Proprietary software
LICENCE + MAINTENANCE
AFTER
Open source platform
BROWSER ONLY·OPEN SOURCE·API REST
— Process
01

A migration guided, never endured.

5 steps · 8 to 16 weeks
STEP 01 · 1 TO 2 WKS

Audit

We study your data: volume, custom fields, hierarchies, linked media, access rights. Delivered as a report and a target mapping.

DELIVERABLES
  • Field inventory
  • Data mapping
  • Migration plan
STEP 02 · 1 TO 3 WKS

Mapping

Design of the target CollectiveAccess structure — projection of the Flora model (fonds / sub-fonds / files / items, ISAD(G)/ISAAR-CPF descriptors, digitisations) into CA hierarchies aligned with EAD/EAC-CPF, validated with your archivists.

DELIVERABLES
  • Customised CA profile
  • Reference lists
  • Correspondence tables
STEP 03 · 2 TO 6 WKS

Migration

Extraction from Flora (EAD/EAC-CPF XML export, OAI-PMH, SQL dump, linked DAM media), transformations (hierarchies, archival dates, vocabularies), import into CollectiveAccess with native EAD mapping. HD digitisations copied and re-indexed.

DELIVERABLES
  • Acceptance-ready database
  • Migrated media
  • Quality report
STEP 04 · 2 TO 4 WKS

Acceptance

Cross-checks: your reference users validate the migrated records, we adjust, we document. Iterations on a pre-production environment.

DELIVERABLES
  • Test plan
  • Issue tracking
  • Acceptance report
STEP 05 · 1 WK

Training & switch-over

Team training on their own migrated database. Switch to production, support during the first days, managed hosting included.

DELIVERABLES
  • Training sessions
  • Production rollout
  • 30-day follow-up
— Comparison
02

Eleven concrete reasons to migrate.

Flora → CollectiveAccess
AXIS
FLORA
COLLECTIVEACCESS
Business model
Proprietary — licence + annual maintenance paid to Decalog
Open source (GPL) — no licence, no per-user royalty
Source code
Closed — only Decalog evolves the software core
Open — Whirl-i-Gig (NY), European integrators, idéesculture, community
Architecture
100% web and responsive since 2017 (v3.5), currently v4.5
100% web — Providence for cataloguing, Pawtucket for publication
Community & ecosystem
Centred on Decalog — users in France, Belgium, Spain, Switzerland
International CollectiveAccess community — Mémorial 11/9 (NY), Villa Médicis, Musée d'Orsay, INRAP…
Archival standards
ISAD(G), ISAAR-CPF, EAD, EAC-CPF, UNIMARC, ISO 2709 — native
EAD, Dublin Core, VRA Core, MARC, PBCore, muséesDeFrance profile — native; archives + museum + library on the same platform
Public website
Flora Web module included depending on contract — customisation via Decalog
Pawtucket included — faceted browsing, IIIF, ready to theme
API / interoperability
OAI-PMH (DC, EAD, EAC), Z39.50, SRU — archival protocols
Open REST API + OAI-PMH, RDF, Linked Data, Z39.50 — documented and free
Multimedia / IIIF
Built-in DAM for digitisations; no native IIIF
Three.js 3D viewers, native IIIF, interactive annotations, HD mosaics
Domain scope
Specialised in archives — additional Decalog modules for library or museum
14 record types as standard — archives, objects, people, places, events unified
Long-term viability
Tied to Decalog's commercial longevity (independent since 2024)
GPL code — exportable at any time, independent of any single publisher
Reversibility
EAD/EAC-CPF, OAI-PMH export via Decalog tools
Standard MySQL database — SQL dump, readable with any tool

★ Two gains change the game: moving away from proprietary software and open source code. Everything else — durability, openness, interoperability — flows from there.

— Guarantees
03

Four safety nets.

Included
01 INTEGRITY

Data preserved

No loss. Every Micromusée field finds its equivalent — including hierarchies, controlled vocabularies and media links.

02 ACCEPTANCE

Tested round-trip

Before going live, you work on a copy of your real database, in pre-production. Adjustments are free of charge.

03 SOVEREIGNTY

You stay in control

The server is hosted by us, but the database and the media belong to you. Full export available at any time, in an open format.

04 COST

No hidden licence

Once migrated, no more purchase or extension fees. You pay for hosting and support, that's it.

— FIRST STEP IS FREE

Send us a Flora export.
We send back a costed migration plan.

Launch an audit

Our specialised sites