NOS PRESTATIONS
YOU'RE COMING FROM →
FileMaker Excel AtoM Omeka Encyclia S-Museum Flora Micromusée Pallas Dublin Core
05b Service · Migration
FROM PRO / SERVER

FileMaker

WE MIGRATE YOUR DATA TO

CollectiveAccess

Your collections live in a FileMaker database designed ten or fifteen years ago by a developer who is no longer around, and every seat costs you an annual subscription. We pick up the schema, the relations, the media — and we install a web platform, open source, with no per-user licence.

Request a free audit Detailed comparison ↓
LOCK · USERS OPEN
FileMaker ×subscriptions
∞
CONCURRENT USERS
With CollectiveAccess, only the server's capacity matters. No per-user licence, no workstation to provision.
BEFORE
Installed application
1 PC = 1 LICENCE
→
AFTER
Web platform — accessible everywhere
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 FileMaker tables into CA record types and relations, validated with your scholarly teams.

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

Migration

Extraction from FileMaker (DDR XML, CSV exports, container export scripts), transformations (relations, dates, vocabularies), import into CollectiveAccess. HD media and containers 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.

FileMaker → CollectiveAccess
AXIS
FILEMAKER
COLLECTIVEACCESS
Business model
Claris per-user subscription (FileMaker Cloud / Server) — billed annually, per seat
★
Open source — no licence, no seat to provision
Concurrent users
Capped by the number of seats purchased
★
Unlimited — only the server's capacity matters
Data model
Proprietary « linked tables » base, schema often frozen by the first developers
✓
Open relational model (MySQL), 14 record types, native hierarchies
Metadata standards
Ad-hoc fields — no Dublin Core / EAD / VRA alignment
✓
Native mappings: Dublin Core, EAD, VRA Core, MARC, PBCore, muséesDeFrance profile
Remote access
FileMaker Pro thick client or WebDirect — variable performance
✓
Modern web application, accessible from any browser
Public website
To be developed separately (CWP, WebDirect, external integration)
✓
Pawtucket included — faceted public site, ready to theme
API / interoperability
Claris Data API, paid subscription, capped by seat
✓
Open REST API + OAI-PMH, RDF, Linked Data, Z39.50
HD multimedia / 3D / audio
FileMaker containers — practical limits on HD and 3D
✓
HD, RAW, video, audio, 3D OBJ, IIIF — embedded viewers
Joconde / muséesDeFrance export
To be re-developed bespoke
✓
Official plugin: inventory, ten-yearly inventory check, deaccessioning
Long-term viability
Dependent on Claris's roadmap (no guarantee on formats)
✓
Open source — the database runs on standard MySQL, exportable at any time
Sovereignty & hosting
Often FileMaker Cloud — hosted outside the EU
✓
Hosted in France (OVH Roubaix / Strasbourg), GDPR-native

★ Two gains change the game: an unlimited number of concurrent users and zero per-seat licence. 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 FileMaker export.
We send back a costed migration plan.

Launch an audit
— Coming from somewhere else?

We can migrate your data.

DESKTOP →

Excel tableur

Tableurs Microsoft Excel utilisés comme base de collections
WEB →

AtoM open source

Access to Memory — archives ICA
WEB →

Omeka Classic / S

Plateforme web de publication patrimoniale
DESKTOP →

Encyclia

Logiciel de gestion documentaire
DESKTOP →

S-Museum Skinsoft

Solution propriétaire pour collections (Skinsoft Museum)
DESKTOP →

Flora

Suite de gestion documentaire et archives
DESKTOP →

Micromusée v6 / v7

Logiciel propriétaire historique des musées de France
WEB →

Pallas BruDISC

Logiciel documentaire conçu au CegeSoma, maintenu par l'asbl BruDISC (ULB/VUB)
STANDARD →

Dublin Core standard

Dump générique Dublin Core (XML / CSV / OAI-PMH)
— Continuer la visite

Les autres métiers d'idéesculture.

01 →

Formation

Prise en main, autonomie, montée en compétence
03 →

Hébergement

Serveurs dédiés, infogérance, sauvegardes
04 →

Musées de France

Inventaire, récolement, export Joconde
05 →

Développement

Plugins, intégrations, sur-mesure