CALM Alternatives for UK County Record Offices:
AtoM and ArchivesSpace Compared

CALM (Axiell) has dominated UK county record offices for decades. It is a mature, well-supported system that most local authority archivists know how to use. This article is not arguing that CALM is bad software. It is written for archivists who are approaching a renewal decision and want to understand — honestly — what the open-source alternatives actually offer before they sign another multi-year contract.

The pressure to look at alternatives is real. Annual licence costs are substantial and have increased over time. CalmView, the public web catalogue, is a chargeable add-on rather than a built-in feature. Axiell's roadmap is directing users toward Axiell Collections, which represents a further investment and a more significant platform change than a simple upgrade. Local authority IT budgets are under sustained pressure. These factors together are prompting more county archivists to ask a question they would not have asked five years ago: is there a credible alternative?

There are two: AtoM (Access to Memory) and ArchivesSpace. Both are free, open-source, and actively developed. Both are used by archives in the UK and internationally. They are not identical, and the right choice depends on your specific situation.

What CALM gives you

To assess an alternative honestly, you need to be clear about what you would be giving up. CALM has genuine strengths that matter for county record offices:

• Location management — CALM's physical location tracking is well developed. You can record where boxes are shelved, track moves, and manage strong room capacity.
• Conservation modules — condition recording, treatment history, and conservation tracking are built in.
• Accessions management — accession records, deposit agreements, and transfer workflows are mature features.
• Familiarity — most UK archivists have been trained on CALM. There is a large professional community who know it.
• Axiell support — there is a commercial support arrangement with a named vendor who is responsible for the software.

If any of these are critical to your operation and non-negotiable, that shapes the comparison significantly. Keep them in mind as you read on.

AtoM (Access to Memory)

AtoM is developed by Artefactual Systems with backing from the International Council on Archives (ICA). It is built natively on archival standards — ISAD(G) for descriptions, ISAAR(CPF) for authority records, ISDF for functions, ISDIAH for institution descriptions. It is used by archives worldwide, from national institutions to small parish archives, and it has a growing UK user base.

What AtoM does well

• Descriptive cataloguing — this is AtoM's core strength. Hierarchical description, authority records, and the ISAD(G) data model are first-class features. If your primary need is a well-structured public catalogue of your holdings, AtoM delivers it cleanly.
• Public catalogue included — the Public User Interface is built in, not an add-on. Researchers can search your full catalogue online, browse by creator, subject, and reference code, and filter by date or level of description. This is what CalmView costs extra for.
• IIIF integration — AtoM can be integrated with IIIF image delivery and viewers such as Mirador or Universal Viewer, enabling digital objects to be displayed directly alongside catalogue records.
• EAD export — EAD 2002 and EAD 3 export is included, supporting submission to TNA Discovery and other national aggregators.
• REST API and import/export — programmatic access and command-line import/export workflows are available. Integrations should be planned against AtoM's supported APIs and import/export tools.
• Zero software licence — AtoM is free. You pay for hosting and support, not for the software itself.

AtoM's weaknesses for county record offices

• Location management is limited — AtoM does not have CALM's depth of physical location tracking. There is a basic physical storage location field, but if detailed strong room management is important to your operation, AtoM will feel thin here.
• Accessions module — AtoM has an accessions module but it is less mature than CALM's. It covers the basics but may not map cleanly to complex local authority transfer workflows.
• Conservation recording — minimal. Not a system for conservation management.
• Smaller UK public sector user base — AtoM is well established in religious archives, university archives, and international institutions, but less common in county record offices specifically. There is less of a peer community to draw on locally.

ArchivesSpace

ArchivesSpace is developed by an international community and governed by the ArchivesSpace membership programme. It is the standard system in US research libraries and is growing in UK universities. Its architecture reflects the priorities of large institutional archives with active accessions workflows and complex physical holdings.

What ArchivesSpace does well

• Accessions management — richer and more workflow-oriented than AtoM. Transfer records, donor information, extent tracking, and deaccession processes are well developed.
• Physical location management — ArchivesSpace has a dedicated locations module that maps containers to shelving locations, supports barcoded location management, and tracks moves. This is closer to CALM's depth than AtoM offers.
• Assessment module — built-in collection assessment recording, useful for prioritising cataloguing and conservation work.
• REST API — comprehensive and well-documented. Widely used for integration with library discovery systems.

ArchivesSpace's weaknesses

• Steeper learning curve — the staff interface is more complex than AtoM's. Training overhead is real.
• Steeper installation and maintenance requirements — ArchivesSpace requires more substantial server infrastructure than AtoM (Java, Solr, more RAM). This is managed by a hosting provider, but it means the underlying stack is more complex to administer.
• Public access portal — ArchivesSpace's public interface is functional but less polished than AtoM's. Some institutions supplement it with VuFind or Blacklight overlays.
• IIIF — ArchivesSpace does not have native IIIF support to the same degree as AtoM. External integration is possible but requires additional configuration.

Side-by-side comparison

Feature	CALM (Axiell)	AtoM	ArchivesSpace
Software licence	Annual fee (substantial)	Free (open-source)	Free (open-source)*
Public web catalogue	CalmView — chargeable add-on	Included as standard	Included (less polished)
ISAD(G) compliance	Yes	Native — built on ISAD(G)	Yes (via DACS/EAD)
Location management	Strong	Basic	Good
Accessions module	Strong	Basic	Strong
IIIF support	Limited	Native	Via integration
API access	Restricted	Full REST API	Full REST API
EAD export / TNA Discovery	Yes	Yes (included)	Yes (included)
Conservation module	Yes	No	Basic (assessment only)
UK GDPR / DPA	Axiell terms	Depends on hosting provider	Depends on hosting provider

*ArchivesSpace software is open-source. No software licence fee — cost is hosting and support only.

Which is right for a county record office?

The honest answer depends on what you actually use CALM for day to day.

If your primary need is a public-facing catalogue of your descriptive records — AtoM is the more natural fit. The data model maps cleanly from CALM, the public interface is strong, IIIF support is built in, and the cost savings are immediate. For county record offices where the core operation is hierarchical description and researcher access, AtoM does everything CALM does in this area, and does some of it better.

If you rely heavily on CALM's accessions management, location tracking, and conservation recording — ArchivesSpace is worth serious consideration, because it comes closer to CALM's depth in these areas than AtoM does. The learning curve is steeper and the staff interface more complex, but for archives where strong room management and workflow tracking are central, the trade-off may be worth it.

It is also worth knowing that some archives run both: ArchivesSpace as the staff-facing back-end for accessions, location, and workflow management, and AtoM as the public-facing catalogue. The two systems can be kept in sync via their respective APIs or through periodic export and re-import. This is not a trivial setup to maintain, but it is a recognised pattern in larger institutional archives that want ArchivesSpace's operational depth without sacrificing AtoM's stronger public interface and IIIF support.

If you are currently paying for CalmView separately — this changes the economics significantly. Both AtoM and ArchivesSpace include a public interface as standard. If your current annual total is CALM licence + CalmView + IT hosting overhead, the comparison looks very different from just the headline licence cost.

What about staying on CALM?

This article is not a case for abandoning CALM. For many county record offices, CALM continues to be the right choice — particularly those with complex accessions workflows, well-integrated conservation recording, or long-standing Axiell support relationships. The argument for open-source alternatives is strongest at licence renewal time, when you have leverage to demand a transparent cost comparison, and for institutions where the public catalogue add-on cost is a significant factor.

If you are not at renewal and your current system is working well, the disruption cost of migration probably outweighs the benefit. If you are approaching renewal and want to understand your options before committing, this is exactly the right moment to look.