Migrating an ELN Without Losing the Audit Trail

Published · updated 6 min read

Quick verdict. Plan on the audit trail not migrating. Experiment data can usually be exported, but the history of who changed what is held in vendor-specific logs, exported as a separate file at best. The workable approach is to migrate the records, export and archive the audit trail separately with integrity checks, and keep the old system readable until your retention period ends.

When a regulated lab changes ELN, the experiments are the easy part. The harder question is the history around them: who created or changed each entry, when, and why. That history is the audit trail, and in most migrations it stays behind.

What the rules expect

21 CFR 11.10(e) calls for secure, computer-generated, time-stamped audit trails, says record changes shall not obscure previously recorded information, and requires the trail to be retained at least as long as the records it covers. Clause 11.10(c) adds that records must stay retrievable throughout the retention period.

EU Annex 11 is consistent. Clause 9 says audit trails should be available, convertible to a generally intelligible form and regularly reviewed. Clause 4.8 says that when data move to another format or system, validation should include checks that they are not altered in value or meaning. Clause 17 asks that archived data be checked for accessibility, readability and integrity. Neither text says the trail must move into the new system. They say it must survive and stay usable.

Why audit trails rarely migrate

An audit trail is tied to the system that wrote it: its object identifiers, its user accounts, its action vocabulary. SciNote’s documentation shows the shape. Its audit trail exports as a CSV file, sent by e-mail link, with an identifier, a timestamp, the user, the object type, identifier and name, the action and the values for each event. That is useful as an archive. It is not an import format for another product, and we found no vendor documenting that kind of import. RSpace states the limit plainly: XML archives can carry revision history into another RSpace server, but signatures, Global IDs and the full audit history cannot be migrated from one server to another. Other exports take the same archival form: CDD Vault adds a CSV of the entry’s full audit trail to the ZIP it exports for each notebook entry, with a PDF and the attachments, and Scispot prints a PDF audit report for each protocol or experiment.

Access can also be restricted. SciNote states the audit trail is part of its Premium plans with the 21 CFR Part 11 add-on, and that only the Owner role sees the full team-level trail; its terms give Premium customers at most 30 days after termination to download their data. In CDD Vault, bulk export of notebook entries is documented as a Vault Administrator function. Genemod’s terms keep data available read-only for three years after termination, without describing an export procedure, and the notebook’s documented output is PDF reports. Labstep exports experiments one at a time, as a ZIP file or a PDF, charges for a bulk export by its team, and may delete content once a subscription ends without renewal; openRDM.swiss, the hosted openBIS service, provides all data for download in a structured form when a contract ends, then deletes them. BIOVIA Notebook renders submitted experiments as PDF records, without a published bulk export or end-of-contract data return, and a Dassault Systèmes support note on BIOVIA applications in general says logins are blocked once a licence file has expired, until it is renewed. Arxspan ELN renders a signed experiment as a PDF and downloads a whole notebook as a ZIP of experiment PDFs once an administrator enables it; the older arxspan.com FAQ describes weekly or monthly archives of all stored data delivered to the customer, without stating their format, and no structured export format is published. Uncountable states that its change log exports alongside the records it affected, and publishes no export format or exit procedure. Check who can export, and by when, before the contract with your outgoing vendor ends.

Benchling’s terms say the customer owns its data and can export it at any time while it has access, and that Benchling may erase it from 60 days after the contract ends. Its SDK documentation describes exporting notebook entries through the API as PDFs in a ZIP file, and its GxP white paper says audit trails and data can be exported to other systems in human-readable and electronic forms. The white paper names no format, which makes the format of the audit-trail export a question to settle with Benchling before notice is given.

The .eln format: useful, but check the scope

The ELN Consortium defines the .eln format as a zipped RO-Crate with JSON-LD metadata, recognised by IANA as a media type. It exists for exchanging experimental data between ELNs: eLabFTW exports and imports it, and RSpace exports it. Neither describes the audit trail as part of that export, and RSpace provides its audit records as a separate CSV report, so treat .eln as a route for records, not for the trail, until you have tested your own export.

A migration plan that keeps the evidence

This is our recommendation, not a regulatory requirement.

StepWhat to doEvidence to keep
1. InventoryList records, signatures, attachments and retention periodsSigned inventory
2. Export recordsExport in the richest format availableExport logs, file hashes
3. Export the trailCSV or PDF, per project or whole workspaceExported files, hashes
4. VerifySample entries: compare source and export, including dates and authorsComparison report
5. ArchiveStore trail and records in controlled, readable storageArchive location, access list
6. Cut overStart the new system’s trail at go-live, with a documented cut-over dateChange control record
7. RetireKeep the old system read-only until the retention period ends, if you canDecommission decision

Step 7 is the one most often dropped, and the most useful: a read-only legacy instance answers inspector questions that an exported CSV cannot.

Trade-offs and limits

Keeping the old system costs licences or hosting. Dropping it saves money but turns your CSV archive into the only evidence. If your quality unit accepts that, document the risk assessment. We have not tested any migration end to end; this guide rests on vendor documentation and the regulations. For comparison of vendors’ compliance evidence, see our Part 11 guide and the vendor profiles listed below. A wider look at lab software and AI sits on our sister site, Lab Software Guide.

Conclusion

Assume the trail will not travel. Export it, hash it, verify it and keep it for as long as the records, and keep the legacy system readable if you can. We have no commercial relationship with any vendor named here, and none reviewed this guide.

Related ELN vendors

FAQ

Can an audit trail be migrated into a new ELN?

We found no documented case of one vendor's audit trail being imported as the native audit trail of another, and RSpace states that signatures and the full audit history cannot move even between two RSpace servers. The practical option is to export the old trail as a file, archive it with the records, and let the new system start its own trail at go-live. Confirm this with your quality unit before you begin.

Does the .eln file format carry the audit trail?

The .eln format is a zipped RO-Crate with JSON-LD metadata, built for exchanging experimental data between ELNs. eLabFTW and RSpace both export it, and neither describes the audit trail as part of that export, so test an export from your actual system before relying on it.

How long must the old audit trail be kept?

21 CFR 11.10(e) says audit trail documentation must be retained at least as long as the subject electronic records and be available for agency review and copying. If your records have a ten-year retention period, the trail needs the same, wherever it lives.

What should we check after exporting?

Open a sample of exports and confirm that titles, authors, dates, modification history and attachments are present. Some exports leave content out by design: RSpace's PDF exports leave out attached files, LabArchives' PDF exports give attachments as download links, and its offline HTML copy leaves out files over 250 MB.

Sources

  1. 21 CFR 11.10, Controls for closed systems (eCFR) (accessed 2026-10-01)
  2. EudraLex Volume 4, Annex 11: Computerised Systems (accessed 2026-10-01)
  3. The ELN Consortium, ELN file format specification (accessed 2026-10-01)
  4. How to access and export the Audit Trail in SciNote? (accessed 2026-10-13)
  5. SciNote — Terms of Service (accessed 2026-10-13)
  6. RSpace Community, Team and Enterprise Editions (accessed 2026-10-07)
  7. Export Formats - RSpace Help (accessed 2026-10-08)
  8. Benchling Terms of Service (accessed 2026-10-13)
  9. benchling_sdk.services.v2.stable.export_service module (Benchling SDK documentation 1.4.1) (accessed 2026-10-13)
  10. Considerations for Using Benchling as a GxP System (accessed 2026-10-14)
  11. Downloading a Notebook to PDF (accessed 2026-10-12)
  12. Creating an Offline Notebook (accessed 2026-10-12)
  13. Import / Export (eLabFTW documentation 6.0) (accessed 2026-10-13)
  14. Exporting ELN Entries - CDD Vault Support (accessed 2026-10-15)
  15. Create audit reports on Scispot (accessed 2026-10-15)
  16. Genemod Terms of Service (accessed 2026-10-15)
  17. Reports | Genemod (accessed 2026-10-15)
  18. Exporting your data (accessed 2026-10-16)
  19. Labstep Terms & Conditions (last updated October 31, 2024) (accessed 2026-10-16)
  20. Standard Service Level Agreement for openBIS Services (openRDM.swiss), version 1.3 (accessed 2026-10-16)
  21. T26-2026 - Notification regarding BIOVIA Notebook 2026 SP1 release (accessed 2026-10-19)
  22. T65-2025 Impact of License files and licenses on BIOVIA Applications (accessed 2026-10-19)
  23. Signing an ELN Experiment - Arxspan Knowledge Base (accessed 2026-10-19)
  24. Download Notebook PDF - Arxspan Knowledge Base (accessed 2026-10-19)
  25. Electronic Laboratory Notebook (ELN) FAQ (legacy arxspan.com) (accessed 2026-10-19)
  26. Configurable Lab Software Your Super Users Own | Uncountable (accessed 2026-10-19)