Not “Which is best?” but “What do I need?”

Order first, Lightroom second

If you subscribe to Lightroom, you certainly did not buy it merely to unload memory cards. Yet you probably unload cards all the time — which is worth thinking about. If every offload leaves you renaming folders, moving files to other locations or drives, creating subfolders by hand, or building Lightroom collections just to understand your own archive, why not automate that routine and let Lightroom receive material that is already organized, sorted, and intelligible? The archive remains useful without Lightroom too — if you move to Capture One one day, for example. And if your work spans non-Adobe applications — editing video in DaVinci Resolve or opening darktable for especially delicate processing — a clear physical archive is not a luxury but a necessity.

An excellent importer — still not quite enough

Capture One does far more with cards than Lightroom: it can build a genuinely flexible token-based subfolder tree and create a backup at the same time. But is an extremely detailed tree always an advantage? It looks impressive in a diagram, yet walking through it every day may become tiresome. Depth alone does not create order. ShotPorter can send independent flows to different folders and drives, then keep each individual structure short and clear. Capture One routing remains confined to a branching tree inside one target folder: a single import cannot distribute separate groups to different base folders on different drives. There is also no documented checksum validation of either the primary or backup copy. For a protected physical archive, those are two substantial limitations.

Good import — for photographs only

ON1 Photo RAW organizes photographic imports better than Lightroom: it understands tokens and even creates a backup. But it knows nothing about video and sends every selected image down one branching route. Distributing different groups across different folders and drives, processing video and arbitrary files, and verifying copies by checksum all remain outside its capabilities.

Anything is possible. If you write it yourself.

darktable can be taught almost anything — that is its unique strength. Every application, however flexible and convenient, embodies a particular logic that may not match your vision. The Lua API lets you build highly specialized solutions exactly as you imagine them. But at that point, you are no longer configuring import: you are creating and maintaining your own ingest system.

Photo Mechanic is the venerable patriarch of photographic ingest applications. It can do a great deal, including sophisticated sorting scenarios through its extensive token system and Code Replacement. Yet configuring those scenarios is obscure and difficult, requiring an engineer’s mindset and deep knowledge of the application — and even then it cannot, for example, send different file types to different drives in one pass.

Heavyweights for big business

On a set where media reaches editorial with a multi-volume report, a naming system fixed by protocol, formal acceptance paperwork, and five backup copies in two impact-resistant cases, OffShoot Pro is stronger than ShotPorter — and both its power and price are justified. For a small business, freelancer, content creator, or personal archive, however, it is obvious overkill. This is OffShoot Pro’s native territory, where perhaps only ShotPut Pro — another titan of big business — can match it in both capability and price.