A practical walkthrough of moving a Lightroom Classic library into Luminar —what transfers automatically, what needs rebuilding by hand, and where the process still breaks.
The question that always comes to mind when changing editors is: will the years of folders, ratings, and edits make it across the line? Luminar, in part the answer to that question, introducing a direct Lightroom catalog import. This guide covers the steps, the limits, and what to check before deleting anything.
Don’t feel like reading the whole breakdown? We’ve pulled together a quick summary below.
Key Takeaways
- Direct catalog import now exists: Luminar 1.27.1 added File > Catalog > Import Lightroom Catalog, which reads a Lightroom Classic .lrcat file directly.
- The original catalog stays untouched: Migration copies data into a new Luminar Catalog Imported file rather than modifying the Lightroom library.
- Folders come over whole, not selectively: Lightroom’s selective-import option has no equivalent in Luminar, so an entire folder migrates even if only part of it was originally imported.
- Basic edits transfer, complex ones do not always: Exposure and tone adjustments generally carry over. Local brush work, gradient masks, and custom presets usually need to be rebuilt inside Luminar.
- Colors can shift on import: Luminar renders raw files through a different engine than Lightroom, so migrated photos may look slightly different in white balance and contrast.
- Presets do not convert automatically: Lightroom’s .lrtemplate and .xmp presets are not compatible with Luminar’s .lnpc Look format and have to be recreated or purchased separately.
Preparing for the Migration from Lightroom to Luminar
A clean migration starts with two checks before opening Luminar at all. First, make sure you have Lightroom 15.0 or higher, and if you have an older catalog, you must first update Lightroom in place.
Second, save backup copies of .lrcat itself: If a corrupted or partially indexed catalog causes errors when importing, those errors will occur during import as well. Anyone weighing whether the switch is worth making at all can start from a Luminar vs Lightroom comparison before touching a single file.
Free disk space matters more than most guides mention. Migration duplicates preview data rather than moving raw files, so a 200GB Lightroom catalog needs roughly that much additional space again during the import, less once previews finish generating.
A test run on a small folder is worth the extra twenty minutes. Copying 50 representative images into their own catalog, running the migration on that subset first, and checking the results against the originals catches version mismatches and rendering surprises before committing an entire archive to the process.
Exporting Photos and Metadata from Lightroom
Two migration routes exist, depending on the Lightroom version. Catalog import directly imports folders, collections, ratings, basic edits, and more from the .lrcat file with Lightroom Classic 15.0 and later.
If you don’t use the classic version of Lightroom, but instead use the web-based version, you’ll need to do the manual work: Save Metadata to File > libphotomerka > Rating and Keywords > Save To File, and then ratings and keywords will be preserved even if you don’t have the catalog reader.
XMP sidecars carry star ratings, color labels, keywords, and basic tone adjustments, but not local brush strokes or gradient masks, which are only supported within the proprietary catalog format. Anyone with heavy local retouching across a library should expect to redo that work regardless of which route gets used.
Raw files themselves need no conversion for either route. With Luminar, you can export from your supported camera files with basic metadata and edit instructions, without having to create new image files. If you have a large archive of images, you can save time and disk space by not re-exporting entire JPEGs or TIFFs.
Importing Images into Luminar
The direct catalog route follows a fixed sequence:
- Close Lightroom completely before starting; the catalog file cannot be read while Lightroom has it open.
- In Luminar, go to File > Catalog > Import Lightroom Catalog.
- Let Luminar search the Pictures folder automatically, or click Browse to point at a catalog stored elsewhere, including an external drive.
- Select the correct .lrcat file from the detected list and click Start Import.
- Wait out the process; a catalog in the tens of thousands of images can take well over an hour.
- Check the new Luminar Catalog Imported entry under Folders and Albums once it finishes.
For a smaller or more selective move, dragging files straight into Luminar’s import panel works without touching the catalog at all. That path skips collections and ratings but avoids importing folders wholesale, which suits anyone who only wants a subset of an archive in the new app.
Import speed scales roughly with photo count rather than file size, since Luminar builds previews for every image regardless of raw resolution. A library of 5,000 images typically finishes in fifteen to twenty minutes on a current machine with a solid-state drive; a mechanical hard drive roughly doubles that.
Preserving Edits During the Transition
Basic development settings—exposure, contrast, white balance, crop—generally survive catalog import and land close to their Lightroom appearance. Local adjustments do not travel the same way. Radial filters, linear gradients, and the adjustment brush are Lightroom-specific tools with no matching data structure in Luminar, so those effects either disappear or need to be rebuilt using Luminar’s own masking tools.
The surprise people get is the color change. Since Luminar uses its own raw rendering engine, separate from Adobe’s, a photo edited to be correct in Lightroom may appear slightly warmer or cooler upon import, even if the exposure numbers are the same. Conducting quality control inspections or tests on a few representative images before relying on the entire lot is early enough.
Camera profile differences drive most of that shift. Lightroom applies a camera-specific profile before any manual adjustments appear, and Luminar’s equivalent profile for the same body does not always match tone-for-tone. Photos shot on well-supported current cameras tend to migrate closer to their original look than files from older or less common bodies.
Adjusting to Luminar’s Interface and Tools
The Luminar Edit workspace roughly corresponds to Lightroom’s Develop workspace, but the tools are grouped differently, and sliders from one panel in Lightroom often end up in two or three in Luminar.
Photographers who are not yet ready to cut over to Lightroom completely, but do want to run both applications simultaneously during the transition, can continue to use Lightroom Classic as their catalog application and use the Luminar Lightroom plugin for specific edits, without making a hard cutover.
| Lightroom term | Luminar equivalent | What changes |
| Catalog (.lrcat) | Luminar Catalog | Created automatically on import, separate file |
| Collections | Albums | Same grouping logic, different name |
| Develop module | Edit workspace | Sliders reorganized by tool category, not a single panel |
| Presets (.lrtemplate / .xmp) | Looks (.lnpc) | Not interchangeable; Looks need to be rebuilt or bought separately |
| Flags and star ratings | Ratings and color labels | Transfer during catalog import |
| Local adjustment brush | Masking AI / manual masks | The selection method differs; masks are not ported automatically |
Managing Catalogs and Libraries in Luminar
Luminar’s catalog holds folders and albums rather than a single master library with virtual copies, which is the closest Lightroom concept to Luminar’s approach. Anyone running multiple catalogs in Lightroom for different projects should migrate each one separately rather than trying to merge them beforehand, since Luminar’s import reads one .lrcat file per operation.
Storage location deserves a second look after migration. Luminar keeps its catalog file separate from the original images by default, so raw files can stay on their existing drive structure without a forced reorganization, though moving a folder outside Luminar afterward still breaks the link the same way it would in Lightroom.
Photographers running a network drive or a shared storage setup across a small team should migrate from a local copy first, rather than pointing the import at a live network path. Catalog reads over a network connection are noticeably slower and more prone to interruption than the same operation run against a local SSD.
Tips for Optimizing Workflow Post-Migration
A few habits keep the new library from drifting into disorder. Rebuild core presets as Luminar Looks early, rather than recreating them one at a time under deadline pressure.
Run a full-catalog spot check on color rendering before archiving the old Lightroom catalog anywhere out of easy reach. Keep the original .lrcat file for at least one full project cycle, since it remains the only complete record of local adjustments that were not preserved in the move.
https://skylum.com/luminar/pricing
Troubleshooting Common Migration Issues
Unsupported camera models are the most common hard failure. If a raw format is not yet recognized by Luminar, the file appears in the imported catalog but will not open correctly until camera support catches up in a later update, so checking supported cameras against the specific body used is worth doing before migrating a full archive.
Duplicate folders after import usually trace back to Lightroom’s selective-import behavior, in which only part of a folder was originally imported into the catalog. Since Luminar imports folders in full, images that were present on disk but never selected in Lightroom can appear as new additions.
Missing local adjustments are expected, not a bug, and the fix is manual: rebuild the mask in Luminar rather than searching for a setting that would port it over automatically, since no such setting currently exists.
