Move a Family Photo Library Between Cloud Services Without Duplicates

Moving a family photo library is less about copying files than preserving the information around them. The pictures may survive an ordinary download, while albums, dates, captions, faces, favorites, edits, and shared access can be lost or rearranged.

A minimalist migration aims to preserve what your family actually uses without creating several confusing copies of every image. The safest approach is to keep one temporary local staging area, export deliberately, import into the new service in manageable groups, and verify the result before canceling anything.

Decide what needs to move

Start by defining the library’s essentials. You may need the original photos and videos, capture dates, location data, captions, ratings or favorites, and a small number of important albums. You may not need every automatically generated highlight, search category, thumbnail, or temporary edit.

Separate the library into three broad groups: items that must be preserved, items that are useful but reconstructable, and items that can be left behind. Original files and videos usually belong in the first group. A “2022 beach holiday” album may be worth recreating, but an automatically generated “Best of the year” collection may not be.

This decision matters because cloud services don’t all represent the same information in the same way. One service may store an album as a collection that points to a single photo. Another may export the album as a folder containing another copy. A third may not include shared-album membership in its standard export at all.

Write down the albums, people, and date ranges your family cares about most. This gives you a verification list later and prevents the migration from becoming an attempt to preserve every piece of service-specific behavior.

Confirm the handoff rules: Before exporting, check the current help pages for both services to see which file types, metadata fields, albums, shared items, edits, and account permissions their transfer or export tools preserve. These capabilities and limits can change.

Use local storage as a temporary staging area

Don't make one cloud service download directly into another unless the services provide a transfer method you understand and trust. Direct transfers can be convenient, but they may hide which items were copied, how albums were interpreted, or whether a transfer stopped partway through.

Instead, use a local staging folder on a computer or external drive with enough free space for the export and some working room. Photos and videos may occupy more space than the cloud service’s rounded storage display suggests, and an export can contain several files for one item. Leave room for the archive files, extracted files, logs, and a second temporary copy if you need to retry an import.

If the library is large, export it in logical batches such as year, family member, or album. Smaller batches are easier to inspect and repeat. Keep the original downloaded archive files until you have confirmed that the extracted files and the new cloud library are complete. Don’t rename everything during this stage; unnecessary changes make comparison harder.

A clear temporary structure is enough:

Photo migration/
  Original exports/
  Extracted media/
  Import batches/
  Verification notes/

Your local staging area isn't necessarily a permanent backup. It is a controlled workspace for the move. If the family has no other backup of important photos, consider retaining a separate copy rather than deleting the export immediately after a successful import.

Export originals and metadata together

Use the old service’s official export or download function where possible. Look for options that include original-quality photos and videos, not only optimized previews. If you have edited images, determine whether the export includes the edited result, the untouched original, or both. Some systems treat an edit as instructions applied inside the service rather than as a separate file.

Metadata may appear in several places. Capture date, camera details, and location are often embedded in the image or video file. Captions, ratings, faces, and album membership may be stored in an accompanying file or in the service’s database. An export may therefore contain a photo file plus a metadata file, such as a sidecar or structured data file.

Keep related files together. Don’t discard unfamiliar files simply because they aren’t photos. If an export contains documentation, index files, or metadata records, retain them until you know whether the destination service can use them. A destination may ignore them during import, but they can still help you reconstruct dates, captions, or albums manually.

Videos deserve special attention. Check that the export includes the original video files and not only still frames or previews. Motion photos, live photos, bursts, panoramas, and paired audio may be represented as multiple related files. Preserve those relationships until you understand how the new service imports them.

Rebuild albums instead of blindly copying folders

Albums are usually the part of a migration that requires the most judgment. A folder named “Christmas 2018” may be a real folder in one system, an album label in another, and a downloaded collection of duplicate files in a third.

If the destination can import album information from the source export, test that capability with a small, unimportant album first. Check whether the imported album contains links to the existing photos or new copies. Also check whether its dates, captions, and ordering remain sensible.

If albums don’t transfer reliably, create a short reconstruction list and rebuild only the ones your family uses. Import the underlying photos once, then add those items to destination albums. This avoids creating one physical copy per album. The same photo can usually belong to several albums without being uploaded several times, although the exact behavior depends on the service.

Shared albums need a separate plan. Record their names, members, important comments, and whether they contain contributions from other people. A shared album may include photos that aren’t in the main account’s private library, or it may grant access without transferring ownership. Ask contributors for original files if the family needs to preserve them independently.

Treat family access as a permission decision, not merely an album setting. After importing, invite people again through the destination service and review whether they can view, add, download, or delete items. Avoid assuming that a shared link has the same privacy and editing controls as the old one.

Prevent duplicates before and after import

The simplest duplicate-prevention rule is to choose one canonical import set. Don’t import the same library from both a complete export and several album folders unless you’ve confirmed that the album folders contain references rather than additional media files.

Before importing, compare batches by filename, file size, and capture information. These checks are useful but imperfect. Two copies can have different filenames while being identical, and the same photo can have different sizes after editing or re-encoding.

A stronger duplicate check uses a cryptographic hash of each file. Identical files produce the same hash, even when their filenames differ. Hashing won’t identify two visually identical images that were resized, exported again, or saved with different metadata, so it should be combined with dimensions, duration, capture time, and visual review where necessary.

Destination services may offer duplicate detection during upload. If so, read how it defines a duplicate before accepting its decisions. It may recognize identical files but treat an edited version as a separate photo, or it may merge items based on visual similarity. Keep the original staging export until you know what was skipped or merged.

If duplicates already appear in the new library, pause rather than deleting in bulk. First determine whether they are genuine duplicates, an original and an edited version, a motion-photo pair, or a photo that belongs in multiple albums. Deleting from a shared library can also affect other family members.

Import in a small test batch

Choose a test batch containing several ordinary photos, a video, an edited image, a photo with a caption or location, and one album if possible. Include an item that matters enough to reveal a problem, but not the only copy of something irreplaceable.

Import the batch and inspect it on the web and on the family’s usual phones or computers. Check image quality, orientation, dates, time zones, captions, location, video playback, edits, album placement, and sharing behavior. If the service creates a separate “recently added” view, use that to identify exactly what entered during the test.

Only continue when you understand the result. If metadata is missing, determine whether the destination supports it, whether it needs a particular export format, or whether you’ll have to preserve it in a separate local archive. If the test produces duplicates, correct the import method before scaling up.

Import the remaining batches consistently. Avoid changing filenames, moving items between folders, or editing metadata while a large upload is still in progress. Those changes make it more difficult to distinguish an import problem from a later organization change.

Verify before canceling the old service

Verification should compare more than the total number of photos. Counts can differ for legitimate reasons: unsupported file types, duplicate merging, shared items, deleted items, or separate versions of edits. Use several checks together.

Confirm that the destination contains the important date ranges and that a sample from each batch opens at full quality. Test several videos, including longer or less common formats. Search for captions, locations, and dates that you know should exist. Open priority albums and check their membership rather than relying only on their names.

Review shared access with each family member who needs it. Confirm that they can sign in, find the expected albums, and perform only the actions you intend to allow. Check the destination’s privacy settings and make sure old shared links, public galleries, or former collaborators are no longer granting access if you don’t want them to.

Keep a short migration record containing the export dates, batch names, any skipped items, and unresolved differences. This is especially useful if the old service uses a delayed deletion period or if you discover a missing album months later.

Run the final family check: Before ending the old subscription or deleting its library, open the destination on the devices your household actually uses. Test important albums, original-quality downloads, videos, search, and sharing, then keep the old account available until any waiting or recovery period has passed.

Close the old service carefully

Don’t cancel the old service just because the upload indicator says “complete.” A completed upload only tells you that the destination received files; it doesn’t prove that every important property or shared relationship survived.

Once verification is satisfactory, turn off automatic photo backup from the old service on family devices so new items don’t continue arriving there. Update phones, tablets, computers, and any automated upload tools to use the destination service. Otherwise, the family may slowly create two libraries again.

Keep the local export or another independent backup if the photos are important. Cloud synchronization isn't the same as a backup: deletions, account problems, corrupted files, or unwanted changes can propagate. A second copy stored separately is a modest safeguard against losing the library while trying to manage it.

The cleanest migration is usually the least elaborate one: one verified export, one controlled import, a small set of rebuilt albums, and carefully restored family access. Preserve the original files and the albums people truly use, document the exceptions, and postpone cancellation until the new library has proved itself in everyday use.