Compatibility
Archivers.ai is not a repository. It is not a collections management system. It is not a preservation platform. It sits in front of those systems and exports into them. Here’s the current list — the specific profile for your instance is tuned during onboarding.
Archival description systems
CSV import profile mapped to AtoM’s description template, preserving ISAD(G) fields, hierarchy, and access conditions.
CSV profile mapped to resource and archival object schemas, with component IDs, hierarchical levels, date expressions, and scope notes.
EAD3 XML finding aids suitable for downstream services and portals that ingest standards-based archival XML.
Collections management systems
SPECTRUM-aligned CSV profile configured during onboarding for Axiell Collections and EMu instances.
CSV profile mapped to Modes-compatible field layouts for document and object collections.
Tested profiles for Adlib and Mimsy XG deployments, tuned to your institution’s field conventions.
Digital preservation
BagIt packages with PREMIS provenance, ready for ingest into Preservica workflows.
Transfer metadata CSVs and BagIt packages compatible with Archivematica’s ingest workflow.
SHA-256 hash manifests, bag-info.txt provenance, and data directories for any system that ingests BagIt.
Not on the list?
If your downstream system isn’t on this list, it doesn’t mean we can’t work with it. As long as it ingests one of the open formats we produce — EAD3, Dublin Core, BagIt, or CSV — we can agree a profile during onboarding. If you’re running something bespoke, tell us during scoping and we’ll work out the mapping together.