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

Omeka

WE MIGRATE YOUR DATA TO

CollectiveAccess

Omeka (Classic or S) is an excellent CMS for heritage publishing — but first and foremost it is a publishing tool, not a collections management base. No loan management, little inventory management, a data model centred on Dublin Core. When the need for a real documentary management tool arises — inventory, inventory check, movements, exhibitions, conservation — we move your Omeka into CollectiveAccess, which also handles the back office.

Request a free audit Detailed comparison ↓
LOCK · MANAGEMENT OPEN
Omeka publishing only
2-in-1
BACK OFFICE + PUBLIC SITE
CollectiveAccess handles inventory, inventory checks, loans and exhibitions — and publishes via Pawtucket. You keep the visitor-side comfort of Omeka, plus the rigour of a real base.
BEFORE
Publishing CMS
WEB FRONT-END ONLY
→
AFTER
Full platform: back office + Pawtucket
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 Omeka items / collections / sites into CA types, validated with your scholarly teams.

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

Migration

Extraction from Omeka (REST API, SQL dump, linked media), transformations (Dublin Core → CA model, Omeka S exhibitions → sets), import into CollectiveAccess with the DC mapping preserved.

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.

Omeka → CollectiveAccess
AXIS
OMEKA
COLLECTIVEACCESS
Business model
Open source — same open source family
=
Open source — likewise, no licence
Tool purpose
Publishing CMS — putting things online above all
★
Management + publishing tool — inventory, inventory check, loans, exhibitions, public site
Data model
Items / Collections / Sites — Dublin Core only
✓
14 types: objects, collections, places, occurrences, exhibitions, loans, media, authorities
Metadata standards
Native Dublin Core — EAD, VRA, MARC via plugins
✓
Native mappings: Dublin Core, EAD, VRA Core, MARC, PBCore, muséesDeFrance profile
Remote access
Already web
=
Already web
Public website
Excellent publishing — the heart of Omeka
=
Pawtucket — faceted public site, more collections-oriented
Inventory management
No structured inventory numbers, no inventory check
★
Full inventory, ten-yearly inventory check, deaccessioning — Musées de France compliant
Loans & movements
No native management — handled outside Omeka
★
Built-in loans, exhibitions and movements module — condition reports, conservation
Joconde / muséesDeFrance export
External plugins, poorly maintained
✓
Official plugin: inventory, ten-yearly inventory check, deaccessioning
Long-term viability
Open source — already viable
=
Open source — likewise viable, standard MySQL base
Sovereignty & hosting
Already in hand — depending on your current hosting
=
Hosted in France (OVH), GDPR-native, automated backups

★ Three gains change the game: a real management tool (and not just a publishing one), an inventory compliant with Musées de France, and the handling of loans and movements. 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 Omeka export.
We send back a costed migration plan.

Launch an audit
— Coming from somewhere else?

We can migrate your data.

DESKTOP →

FileMaker Pro / Server

Bases relationnelles propriétaires Claris/Apple
DESKTOP →

Excel tableur

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

AtoM open source

Access to Memory — archives ICA
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

Our specialised sites