Lightroom for Photo Archiving: Limits and Alternatives

Migration

Two different jobs

Lightroom is a trademark of Adobe. Lightroom Classic is photo development and management software: you import your images, sort them, rate them, develop them, and export them. It keeps that work in a catalog, a .lrcat file, which references the photos on your drives and stores, for each one, its ratings, flags, colour labels, keywords, collections, virtual copies, stacks, and develop settings. For the details, see What Is a Lightroom Catalog, and What Does It Actually Hold?

A development catalog serves the work in progress: choosing, editing, delivering. An archive answers other questions, ones that span decades:

Is this file still intact, bit for bit?
Where are its copies, and are they sound?
Which work does it show, in how many prints, and whose hands has it passed through?
Will this information still be readable without the software that produced it?

These questions are not about development, and answering them is not a development tool’s job. Looking for a “Lightroom alternative” for archiving is therefore less about replacing one program than about setting up, alongside it, what an archive needs.

What an archive requires

Identify each file by its content. A fingerprint such as SHA-256 tells you whether two files are identical, and whether a file has changed since it entered the archive, whatever its name.
Check fixity. A file can degrade without any warning. The only way to know is to read it in full and compare its fingerprint with the one taken on entry. See What Is Fixity in Digital Preservation?
Keep several copies, one of them offsite. That’s the 3-2-1 rule: three copies, on two different media, one of them elsewhere.
Describe works, not just files. A work has a number, an attribution, prints, a provenance. A file is only one representation of it.
Protect what is confidential. Prices, buyers, living people: this data must not leave by accident.
Export in open formats. An archive must be readable without the software that wrote it.

The table: who does what

What a development catalog does well	What an archive needs on top	The suite’s software that handles it
Sorting, rating, flagging, and labelling photos	Keeping that curation readable, with a SHA-256 fingerprint for each original	Obscura Catalog, which carries over ratings, flags, and labels when importing the `.lrcat`
Adding keywords, sometimes in a hierarchy	A thesaurus: hierarchical terms, synonyms, SKOS export	Obscura Catalog
Grouping photos into collections	Telling the work apart from the file; attributions, prints and editions, provenance	Obscura Catalog (catalogue raisonné)
Developing RAW files and keeping the settings history	Keeping those settings for the record, next to the description	Obscura Catalog archives them; it does not develop RAW files
Referencing photos spread across several drives	Knowing where every copy lives, finding exact and visual duplicates, consolidating through verified copies	Obscura Trace
Exporting images for the web or for print	Exporting descriptive data as CSV, LIDO 1.1, or CIDOC CRM, leaving out what is confidential	Obscura Catalog
Giving everyday access to the files	Sealed, verifiable archives, fixity audits, copies on your media and offsite	Obscura Vault

Bringing a Lightroom catalog into Obscura Catalog

The Obscura Catalog guide has a full chapter on this: Import a Lightroom catalog. What matters first: the Lightroom catalog is opened read-only and never modified, nor are the originals and their .xmp files. Catalog references the photos where they are; it does not copy them.

The steps

Choose the catalog. Quit Lightroom, then in Imports, Lightroom tab, choose the .lrcat file. If Lightroom has this catalog open, its very latest changes may be missing, and the report says so.
Read the dry run. Catalog reads the catalog without writing anything and shows what the import would do: photos found, new, likely duplicates, missing originals, keywords, collections. It names any volumes that aren’t mounted: connect them before going further. The dry run is free.
Import. The import requires an Obscura Catalog licence. It fingerprints each original with SHA-256. A missing or unreadable original is recorded as failed, and the import carries on. You can stop it and resume later; what is already imported stays.
Keep the report. It counts the photos imported, skipped, missing, and failed, and lists any catalog data that couldn’t be read. It can be exported as CSV.

The dry run is also where you set the options: whether to include videos, bring keywords into the thesaurus with their synonyms, bring over collections, archive develop settings with the whole history or only the last 50 steps, and skip or import anyway content already in the library. During the dry run, duplicates are estimated by name and size; the import then checks the exact content.

What carries over, and in what form

The full detail is in the guide’s What is carried over section:

ratings, flags, and colour labels: carried over as they are;
title, caption, creator, copyright, and the technical capture data;
keywords: as tags, and into the thesaurus with their hierarchy and synonyms;
collections and collection sets: as nested collections;
smart collections: as frozen collections, with their members at the time of import;
virtual copies: as named versions of the original file;
stacks: as “Stack” relationships between files;
develop settings, history, snapshots: archived for the record.

Worth knowing beforehand

The previews Lightroom stores are not read: Catalog prepares its own thumbnails.
The metadata carried over stays in the catalogue: nothing is written to XMP sidecars or to the files.
Running the import of an already imported catalog again adds only what is missing; photos already imported are skipped. So decide where you will keep the description from then on.

After the import: from file to work

Once the photos are in, the archive work begins. Two tasks first:

Review the vocabulary. A keyword already in the thesaurus is reused, never moved. Merge variants into synonyms, and arrange terms from broad to narrow.
Create the works. A file never becomes a work on its own. Catalog can create works from files not yet linked to any work; nothing is created until you confirm. Each work gets a catalogue number that will never be reassigned.

For an element-by-element reading, see also Migrating from Lightroom Classic: What Actually Carries Over.

Before and after the import: the rest of the suite

Before, if your photos are scattered. Obscura Trace inventories several drives, finds exact duplicates and visually similar images, then consolidates through verified copies. Nothing is deleted without your consent. Bear in mind that Catalog looks for each original where the Lightroom catalog says it is: an original that is no longer there will be recorded as missing.

After, to preserve. From Exports, Catalog prepares a package for Obscura Vault: a backup, a full export without images, and the list of originals. Obscura Vault verifies it, finds the originals it names, and archives the lot. It then verifies the integrity of the files through fixity audits, and keeps copies on your media and offsite.

Where to start

If your work lives in a Lightroom Classic catalog today, start with Obscura Catalog and run the dry run on a representative catalog: it writes nothing and shows you, with figures, what the import would give. To see how Trace, Catalog, and Vault share the rest of the work, visit the software page or the documentation.