Skip to buyer’s guide
Blog

Museum collection management software compared

By Contxt ·

Which collection management system fits your museum? This guide compares nine products across collection and publishing, licensing and operation, workflows, and authority data. It describes their different approaches and the questions to resolve before choosing a system.

Published by Contxt, one of the suppliers included. Based on the linked product documentation; this is not an independent product test or a ranking.

What to compare

Start with the work your museum needs to do: document collections, manage loans and exhibitions, maintain relationships, publish information and exchange data. The four areas below help structure a shortlist. They are not a complete requirements catalogue: conservation, rights, accessibility, security, migration and support also belong in the assessment.

  1. Collection & publishing

    Compare how objects, people, media and curatorial texts relate to one another, and how approved records reach a public website. Integrated publishing and a separate portal can both work well. Assess the editing process, synchronisation, rights controls and included components.

  2. Licensing & operation

    Separate software licensing from hosting and data portability. Proprietary systems may offer useful exports and APIs; open-source systems offer additional control over code and operation. Check export completeness, licences, maintenance responsibilities and which releases are actually available.

  3. Workflows & automation

    List the procedures your team uses, from acquisitions and loans to reporting and data cleanup. Distinguish configurable steps, batch operations and automated research. Test approval, error handling and change history using your own records.

  4. Authority data & vocabularies

    Identify the vocabularies and authorities your collection needs. Local controlled lists, Getty vocabularies, GND, Wikidata and other identifiers serve different purposes. Check supported sources and whether links are entered manually, imported or suggested automatically; assess how ambiguous matches are reviewed.

Nine systems, different approaches.

Scroll horizontally on smaller screens.

Nine systems, different approaches. Reviewed 9 September 2026
Vendor / productCollection & publishingLicensing & operationWorkflows & automationAuthority data & vocabularies
Axiell CollectionsMuseum, archive and library collections. Public publishing components depend on the offer.Proprietary; managed hosting or in-house installation; documented REST API.Museum procedures; Axiell Intelligence extracts entities and writes reviewed metadata back to Collections.Automated Wikidata linking is documented. Clarify additional authorities and configuration.
CatalogItLinked collection entries and profiles, mobile access and included HUB publishing.Proprietary hosted plans; data downloads and optional API or website integrations.Shared cataloguing and mobile data entry. Clarify bulk operations and research automation.Reusable people and place profiles. Clarify external authority connectors and matching.
CollectionSpaceMuseum records and procedures; Public Browser component for online access.Open-source code available; self-hosting or Lyrasis managed hosting; REST API.Collection procedures, batch import and data tools. Clarify additional automation.Authorities and vocabularies supported. Clarify automated external reconciliation.
ContxtObjects, people, curatorial content and publishing in a connected platform.SaaS with public pricing and open import/export. Contxt Open Source: Announced¹.Research, deduplication and record-linking with staff review, according to Contxt.Contxt describes automated suggestions for GND, Wikidata and Getty ULAN.
Gallery Systems (TMS)Collection records, people, media, loans and exhibitions; eMuseum for public publishing.Proprietary licensing quoted by configuration and concurrent users. Scope hosting and export services.Established loan, exhibition and documentation procedures. Clarify automated research and cleanup.Getty vocabulary support documented. Clarify the required authority sources and automated matching.
Lucidea ArgusCollection records, related content and an integrated public portal with live updates.Proprietary; pricing on request; CSV import/export and API documented.Configurable workflows, bulk search-and-replace, research requests and API imports.Clarify external authority connectors, matching and review; scope is not established by the reviewed page.
museumPro.chMuseum inventory on FileMaker; single-user and online versions, plus a web gallery.Published prices; FileMaker licences included in the stated scope; hosted option.Inventory procedures and hosted updates. Some functions require the FileMaker client.Clarify supported authorities and linked identifiers; automated matching is not established by the reviewed pages.
PastPerfectCollection and contact management; Web Edition with optional Public Access publishing.Proprietary; public package prices; hosted maintenance and export options.Accession, loan and exhibition procedures. Clarify additional research and cleanup automation.Local authority files for consistent cataloguing. Clarify external reconciliation.
Zetcom MuseumPlusObjects, artists, contacts and media; eMuseumPlus for public collections.Proprietary; SaaS or in-house installation; API; scoped implementation quote.Configurable collection, exhibition and administrative workflows. Clarify automated research and deduplication.Clarify supported authority integrations and approval steps in the proposed configuration.

Products appear alphabetically, without scores or an overall ranking. Entries summarise the linked vendor documentation; they are not independent hands-on test results. Additional components and configuration are described without treating them as inherently inferior. “Clarify” identifies information to request from the supplier, not a proven absence of functionality.

¹ Contxt Open Source is announced and will ship in Q1 2027. Hosted automation is not implied to be included in every core module. Contxt pricing and release status

Vendor profiles

Axiell Collections

Axiell combines established museum workflows with support for archive and library collections, making it a strong candidate for mixed holdings. Proprietary; managed hosting or in-house installation; documented REST API. Automated Wikidata linking is documented. Clarify additional authorities and configuration.

Product documentation

CatalogIt

CatalogIt makes shared, mobile cataloguing approachable and includes HUB publishing, with a product designed for museum teams as well as other collectors. Proprietary hosted plans; data downloads and optional API or website integrations. Reusable people and place profiles. Clarify external authority connectors and matching.

Product documentation

CollectionSpace

CollectionSpace offers established, genuinely available open-source software and a museum community with a choice of self-hosting or managed support. Open-source code available; self-hosting or Lyrasis managed hosting; REST API. Authorities and vocabularies supported. Clarify automated external reconciliation.

Product documentation

Contxt

Contxt connects collection records, people, curatorial content and publishing, with automated research and record-linking described in its workflow materials. Hosted pricing is public. Contxt Open Source is announced and will ship in Q1 2027; the scope of each edition still needs to be checked.

Contxt collection management

Gallery Systems (TMS)

TMS has a substantial museum community and mature tools for loans, exhibitions and collection documentation. Proprietary licensing quoted by configuration and concurrent users. Scope hosting and export services. Getty vocabulary support documented. Clarify the required authority sources and automated matching.

Product documentation

Lucidea Argus

Argus offers a configurable museum platform with an integrated public portal and connected multimedia content. Proprietary; pricing on request; CSV import/export and API documented. Clarify external authority connectors, matching and review; scope is not established by the reviewed page.

Product documentation

museumPro.ch

museumPro offers museum-focused inventory tools, published prices and a hosted option with a public web gallery. Published prices; FileMaker licences included in the stated scope; hosted option. Clarify supported authorities and linked identifiers; automated matching is not established by the reviewed pages.

Product documentation

PastPerfect

PastPerfect offers accessible collection and contact management, with public pricing and continuity for institutions using its desktop editions. Proprietary; public package prices; hosted maintenance and export options. Local authority files for consistent cataloguing. Clarify external reconciliation.

Product documentation

Zetcom MuseumPlus

MuseumPlus has a large museum installed base and broad operational coverage, with configurable records, exhibitions, contracts and media. Proprietary; SaaS or in-house installation; API; scoped implementation quote. Clarify supported authority integrations and approval steps in the proposed configuration.

Product documentation

Compare responsibilities as well as capabilities

Compare total costs over the same period and for the same scope: software, editing and read-only users, hosting, migration, training, interfaces, public access, maintenance and support. Published prices are a starting point; quotations can cover different services. Open-source licensing does not remove operating costs, and a bespoke quote does not establish that a product is more expensive.

For each offer, establish hosting location, access rights, backups, updates, service levels and a usable export for a later move. A hosted product and self-hosted software assign these responsibilities differently. Have suppliers state which responsibilities remain with your institution.

Use the same demonstration brief for every supplier

Give each supplier a representative object, related people, an image, a curatorial text and a sample loan. Ask the team to import and link them, handle a duplicate, prepare a publication and export the result. Record which steps are included, which need configuration and which remain manual. Include permissions, accessibility and staff training in the discussion.

Choose by requirements, not by institution size alone

Collection type, working procedures, existing data and available technical support can matter more than the size of the museum. A specialist database, a broader museum suite or a configurable open-source platform may each be appropriate. Establish essential requirements before comparing optional features.

Document what every shortlisted system meets, what needs configuration and what remains unresolved. Request a written scope for migration, publishing, interfaces, support and ongoing operation. The most suitable choice is the one your team can use and maintain with confidence.

Common questions

Which collection management system is best?

There is no overall winner in this guide. Define your collection procedures, data standards, publishing requirements, integrations and operating responsibilities, then test the shortlisted systems against the same brief.

Does missing documentation mean a feature is unavailable?

No. Product pages do not describe every configuration or integration. Ask the supplier to demonstrate the required function and include its licence, dependencies and implementation in the written proposal.

Is open-source software the same as free operation?

No. An open licence and available source code allow independent use under the licence terms. Hosting, updates, migration, configuration and support still require resources. Distinguish a published release from an announced one.

What should a product demonstration cover?

Use representative collection data and a real procedure, such as a loan or a publication. Include import, editing, permissions, vocabulary use, duplicate handling, export and recovery from an error. Compare the work left to your team as well as the visible features.

Sources and product documentation · Reviewed 9 September 2026