Legacy photo catalogs · Practical preparation

Moving on from iView MediaPro: preserve your metadata first.

A migration starts with understanding where your archive’s information lives. The original photographs and the catalog may hold different parts of the record.

Published and reviewed October 12, 2026 · By MediaWarden

Can iView MediaPro metadata be migrated?

There are documented migration paths through XML catalog exports and metadata written into media files. NeoFinder documents importing iView, Expression Media and Media Pro XML, while Photo Supreme documents a metadata-export workflow for Phase One Media Pro 2.x. These establish possible routes; they do not establish that every field will transfer from every version.

Before choosing a replacement, distinguish three things: preserving the original source information, mapping it into the new catalog, and reproducing familiar behavior such as browsing catalog sets.

Find the catalog as well as the photographs

Copy the native catalog, original media, available XML exports and sidecar files. Record the application version and whether the existing installation still opens the catalog. A folder of photographs may not contain the captions, keywords or custom annotations that were only saved in the catalog.

For agency archives, include a sample of the information staff actually use: project names, locations, photographer credits, copyright notes, custom fields and collection membership. A small, varied sample is more useful for validation than a large set of simple records.

What can be recovered from each source?

Potential migration sources and their limits
SourceWhat to check
Original images and sidecarsRead available EXIF, IPTC and XMP metadata. Catalog-only edits may not have been written back to these files.
XML catalog exportInspect exported fields, file references, annotations and included previews. Verify collection relationships separately.
Native catalogKeep an untouched copy. A compatible legacy application may be needed to produce an export; direct import into a new product cannot be assumed.
Catalog with missing originalsMetadata and available previews may still be useful. Preserve records with a missing-file status; a preview cannot replace the missing full-resolution original.

Give custom fields and catalog sets their own checks

Standard keywords are only part of the job. NeoFinder documents support for custom annotations in XML and XMP, but also distinguishes its XML import from the XMP route used to recreate catalog sets as albums. Photo Supreme documents additional conversions for Media Pro ratings, color labels and catalog sets.

The lesson is to test your chosen route with your own data. Do not infer complete preservation from a successful import message or a matching image count.

A practical migration checklist

  1. Preserve the source. Work from copies of the catalog and files. Writing annotations back to originals is a change to those files; keep untouched copies first.
  2. Prepare a representative export. Include records with custom fields, multiple keywords, nested collections and missing-file references. Export settings depend on the version and destination importer.
  3. Compare both sources. Check catalog values against embedded metadata. Retain conflicting dates or descriptions with their source until someone resolves them.
  4. Check relationships. Verify collection membership, hierarchy, ratings, labels and file locations, as well as individual text fields.
  5. Review exceptions. Require a list of missing files, unsupported fields, ambiguous matches and encoding problems.
  6. Test the way staff work. Find a known project, retrieve a credited photograph, open an original and export its metadata. Preserve the legacy archive until the results have been accepted.

What MediaWarden is developing

Our initial focus is digital asset management for public agencies with neglected photo archives. We are developing an approach that preserves source metadata, makes collections searchable and reports migration exceptions. We are also exploring assisted review for ongoing photo backlogs.

Supported catalog versions, file formats and storage connections remain to be confirmed. We cannot promise complete metadata preservation before inspecting and reconciling a representative catalog.

Explore MediaWarden’s direction

Sources and compatibility notes

This guide draws on the migration documentation below. Each describes its own product and supported route; the settings and conversion steps are not universal instructions for every importer.

MediaWarden is independent and is not affiliated with iView, Microsoft, Phase One, Capture One, NeoFinder or Photo Supreme. Product names identify the migration tools discussed.