Moving away from Adobe Lightroom Classic, or just adding a second way to browse your library, raises one practical question before anything else: what happens to the catalog you have spent years building? Your ratings, your keywords, your folder structure, and your edits all live inside Lightroom, and a good migration protects that work instead of throwing it away. This guide walks through exactly what a Lightroom catalog contains, what carries over when you move, what does not, and a safe step by step process to bring your library into a local, AI powered photo manager like Memora without risking your originals.
If you are still deciding whether to switch at all, it helps to see the options side by side first. Our roundup of free Lightroom alternatives and the detailed Memora vs Lightroom comparison cover pricing and features. This article assumes you have made the decision and now want to migrate cleanly.
Before you start: back up your catalog and photos
Migration should never be your first and only copy of anything. Before you touch a single setting, make sure you have a complete backup of two things: your photo files, and your Lightroom catalog file. Lightroom stores its database in a file ending in .lrcat, usually alongside a .lrcat-data folder and a previews package. Copy the entire folder that contains your catalog to a second drive or an external disk.
This matters because everything described below is non destructive when done correctly, but a backup means a mistake costs you nothing. Lightroom can keep running exactly as it is during and after the migration. You are not deleting Lightroom, and you are not converting your catalog into something Lightroom can no longer open. You are reading a copy of your existing data into a new tool.
A quick checklist before migrating
- Back up your photo files to a separate drive.
- Back up the full folder containing your .lrcat catalog.
- In Lightroom, write metadata to files if you rely on XMP sidecars (Edit or Library menu, Save Metadata to Files).
- Note where your photos physically live on disk, since folder paths are what most tools rely on.
What is actually inside a Lightroom catalog
People often assume their photos are "inside" Lightroom. They are not. Lightroom Classic keeps your image files wherever they already sit on disk, and the catalog is a database that points to those files and records everything you have done to them. Understanding this split is the single most important idea in any migration, because it explains what can move and what cannot.
A Lightroom catalog stores references to each photo's location, plus the metadata you have added: star ratings, flags, color labels, keywords, titles and captions, collections, and the develop adjustments you have applied. The pixels of your edited photos are not saved as new files. Instead, Lightroom records your edits as a list of instructions and re applies them every time you view an image. That is why a catalog can be small compared with your photo library, and why your edits look invisible to other programs that only see the original file.
The catalog itself is a SQLite database. That is a widely used, open database format, which is why a modern photo manager can read the structured data inside a catalog directly. If you want to go deeper on the file format itself, a companion article covers how to read a .lrcat file without Lightroom.
What transfers when you migrate, and what does not
This is where expectations need to be precise. Migration is not magic, and any tool that promises a perfect one click clone of Lightroom is overstating things. Here is an honest breakdown.
What carries over cleanly
- Your photo files. Originals stay exactly where they are. Nothing is moved or rewritten.
- Folder structure. The way your images are organized on disk comes across because it is part of the file system, not Lightroom.
- Ratings, flags, and labels. These are stored in the catalog and, if you saved metadata to files, in the files themselves.
- Keywords, titles, and captions. Standard metadata fields map across tools well.
What needs care
- Develop edits. Lightroom records adjustments in Adobe's own format. A different application cannot reproduce Adobe's exact rendering, because the math behind each slider is proprietary. Your ratings and keywords still help you find images, and you keep Lightroom for editing whenever you need its full develop module.
- Collections and smart collections. Manual collections may import as folders or albums depending on the tool. Rule based smart collections often need to be recreated.
- Virtual copies and stacks. These are Lightroom specific concepts that do not always have a direct equivalent elsewhere.
A deeper companion article explains what metadata is preserved when importing Lightroom catalogs, breaking each field down in detail. The short version: the organizational work that took you the most time, your ratings and keywords and structure, is exactly the part that travels well.
Step by step: bringing your catalog into Memora
Memora is built around this exact situation. Instead of forcing you to re import and re tag thousands of photos, it reads your existing Lightroom Classic catalog directly and layers local AI search on top. Here is the process.
Step 1: install Memora and point it at your photos
Download and install Memora for Windows. On first run you can add the folders where your photos already live, or you can import a catalog. Because Memora works on the files already on your disk, you are never duplicating your library.
Step 2: import your Lightroom catalog
Choose the option to import a Lightroom catalog and select your .lrcat file. Memora reads the catalog's database and maps your folders, ratings, and keywords so your organization is preserved. Your Lightroom catalog is opened read only, so nothing in Lightroom changes.
Step 3: let the local AI index run
Once your library is mapped, Memora builds a local AI index of the visual content of your photos. This is what lets you later search by describing a scene in plain language rather than relying only on the keywords you typed by hand. All of this processing happens on your computer, and your photos never leave your machine.
Step 4: start searching and organizing
After indexing, you can type natural language queries such as "sunset over mountains" or "kids on the beach" and Memora returns matching images, even ones you never tagged. You also get AI smart albums that group photos automatically. For a full walkthrough of importing and searching, see the Memora tutorial, which includes a short video.
Lightroom catalog versus a local AI catalog
It is worth understanding how the two catalog models differ, because it explains why you might run both. A Lightroom catalog is optimized for a develop centric workflow: it tracks edit history, virtual copies, and a rendering pipeline. A local AI catalog like Memora's is optimized for finding and browsing: it builds a semantic index of image content so search understands meaning, not just typed keywords.
These are complementary strengths, not competing ones. Many photographers keep editing in Lightroom and add Memora as the fast way to search and browse the same library. A separate companion article on Lightroom catalog versus Memora catalog goes into the technical differences in depth.
If you are leaving Adobe entirely
Some people migrate because they want to stop the subscription completely. If that is you, plan for the parts of Lightroom you will no longer have, mainly the develop module. A common approach is to finish and export any in progress edits from Lightroom first, so your finished versions exist as standard image files, then rely on Memora for organization and search and a lighter editing tool for future adjustments. Because Memora reads RAW files and supports non destructive basic adjustments, a large share of everyday work is covered, while specialized retouching can move to a dedicated editor.
If you also keep photos in other tools, Memora reads Capture One catalogs and any folder on disk as well, so it can act as a single search layer across a library that is spread across more than one application. The Lightroom integration feature page explains how the catalog reading works in more detail.
Common migration mistakes to avoid
A few avoidable errors cause most of the frustration people report when moving away from Lightroom. Knowing them in advance saves time and protects your work.
- Treating the move as your only copy. Always migrate from a backup, never from your single working copy. If anything looks wrong, you simply go back to the backup and try again.
- Expecting develop edits to look identical elsewhere. Different engines render RAW files differently. Plan to keep finished edits as exported files, or keep Lightroom available for editing, rather than assuming a perfect pixel match.
- Moving photo folders during migration. Reorganize files before or after, not in the middle. Catalogs point to file paths, so moving files while importing can break those links.
- Skipping a metadata save. If you rely on XMP sidecars, write metadata to files in Lightroom first so ratings and keywords are stored with the images, not only in the database.
After you migrate: how daily browsing changes
The biggest day to day difference after migrating to a local AI library is how you find images. In Lightroom you mostly locate photos through folders, collections, and the keywords you remembered to add. With a semantic index, you can describe what you are looking for and get results even for photos you never tagged. That shifts a lot of manual upkeep off