What software can manage a museum's collections?
CollectiveAccess is the best-established open-source option for the scholarly management of museum collections. Fourteen linked record types, customisable fields, Getty and Wikidata vocabularies built in, used at municipal, regional, national and private museums for over ten years.
What's the best open-source software for a museum?
For full scholarly cataloguing (works, movements, loans, condition reports, exhibitions), CollectiveAccess is the reference. For simpler projects focused on public publication, Omeka may suffice. For historical archives tied to the museum, ICA-AtoM is more natural. The right choice depends on the depth of curatorial work expected — we run that audit for free.
How does CollectiveAccess compare to proprietary museum software?
CollectiveAccess is open source (GPL licence, public code on GitHub), no per-user fee, your service provider is interchangeable. Proprietary vendors typically charge per user or per module, and the code stays opaque. At equivalent functionality on scholarly management, the cumulative ten-year cost is generally lower on the open-source side — the initial investment being comparable.
How much does a CollectiveAccess base cost for a museum?
It varies widely depending on collection size, level of support and chosen hosting. For a municipal museum with a few thousand objects and a five-person team, the initial investment (configuration, data migration, training, first-year hosting) typically falls between €15,000 and €40,000 net. Subsequent years are stable: no per-user licence, just hosting and maintenance. Ask us for a costed scope for your case.
Can we migrate from another collections management system to CollectiveAccess?
Yes — idéesculture has carried out migrations from FileMaker, Excel, AtoM, Omeka and proprietary museum platforms. The handover relies on the structured exports the source system provides (XML, CSV, SQL dump). For older or heavily customised bases, an upfront audit defines what is migrated as-is, transformed or re-keyed. See our dedicated migration page for the method.
Does CollectiveAccess scale from small museums to national institutions?
Yes. We support sites with a few hundred objects (small thematic museums) up to several hundred thousand records (national collections, multi-site institutions). The MySQL backend and the modular architecture allow the same software to fit both ends of the spectrum, with hosting sized accordingly.
Who maintains CollectiveAccess and what's the long-term outlook?
CollectiveAccess is developed by Whirl-i-Gig (New York) since 2003, distributed under GPL v3, with a public roadmap on GitHub and an active community of integrators in Europe and North America. The code is exportable to standard MySQL at any time — your data is never locked in, regardless of who maintains your instance.
Can CollectiveAccess be used as a photo library or image collection for our museum?
Yes. CollectiveAccess natively stores high-definition images (up to 100 MB per file, RAW formats accepted), generates IIIF manifests, embeds the Mirador viewer and allows image annotations (regions, zooms). Each photograph stays linked to its context — depicted artwork, photographer, rights, capture date, intended use. The scholarly photo library (work shots for publication, restoration documentation) lives in the same base as the historical image collection (older photographs documenting the collection itself, photographer fonds). Real cases: Charleroi Museum of Photography (collection of historical and contemporary prints, institution dedicated to photography), Musée Malartre (vehicles photographed + 3D scans integrated into the records), Institut pour la Photographie des Hauts-de-France (documentary base on the history and practice). No need for a dedicated DAM (Phraseanet, Cumulus) alongside — the photo library is integrated into collection management.