AI-generated editorial illustration. Not a Southlake Vision client project.
Treat media migration as a product mapping task
For an Ecommerce Manager, Shopify product media migration is not simply a transfer of image folders. Files must remain connected to the right products, variants and information roles. An archive can contain good photography but still be difficult to migrate if its names and relationships reflect years of changing internal habits.
Start with the destination catalogue and stable product identifiers. Map the existing media to that structure before moving files. A hypothetical home goods brand might discover that a product title changed while its internal code remained stable. The code can help preserve the connection, while the old title alone could lead to duplicate products or an incorrectly assigned photograph.
Inventory media before choosing what to move
Create a record of the files actually in use and those stored elsewhere. Include photographs, video and any other media the destination will need, along with their current placement and approval status. Distinguish a source master from a compressed storefront copy, and identify files for which the original cannot be located.
Do not automatically import every historical asset. Working previews, superseded packaging and obsolete campaign images can create confusion in the new system. Mark each item as retain, replace, archive or investigate. That decision should involve someone who understands the product version, not only the person performing the technical migration.
Map image roles and intended order
Record what each image contributes: identification, alternate angle, material detail, use, contents or comparison. This helps preserve the gallery's logic when filenames are inconsistent. It also reveals gaps that might otherwise become visible only after publication, when the new page looks polished but no longer explains the product adequately.
For a hypothetical lamp, a room view may be visually appealing while the gallery lacks an image of the switch. Label both the existing context image and the missing handling view. Review the home product portfolio as a presentation reference, then plan any replacement photography against the identified information gap rather than commissioning an unrelated catalogue refresh.
Verify variant relationships separately
Build a product-and-variant matrix that connects each selectable option to the correct media. Colour, size and pack differences can be lost when migration relies on matching similar filenames. Use a verified sample or approved product record to resolve uncertain relationships, rather than judging a variant solely from a thumbnail.
Pay particular attention to shared images. A material detail might legitimately apply to several variants, while a contents photograph applies only to one configuration. Document that distinction. After transfer, test option selection in the actual storefront so that the visual result agrees with the matrix instead of assuming that a successful file upload proves the assignment is correct.
Review rights and remove private material
Confirm that retained media can be used in the new destination and planned context. Keep a record of relevant talent, third-party image and other usage permissions where applicable. A file being present in an old folder does not establish unrestricted reuse, especially when the original commissioning history is unclear.
Keep operational documents and sensitive information outside public media storage. Shopify's media guidance distinguishes public storefront files from confidential material. A migration is a useful moment to separate product assets from supplier correspondence, internal pricing and personal records. The media register can note where an approval record exists without uploading that record alongside customer-facing photographs.
Define delivery before commissioning missing images
If the audit reveals gaps, give the studio the intended media roles, product identifiers and export needs. Specify how the new files should join the migration register. This is easier than commissioning fresh photography under a different naming system and expecting the ecommerce team to reconcile it later.
Southlake Vision can plan product photography around an existing catalogue structure. Share a representative sample of the register and explain which images are replacements, which add missing information and which support a new destination. The scope should make the migration more understandable, not introduce another disconnected collection of attractive files.
Rehearse the migration on difficult products
Choose a small test group with meaningful variation: several colours, a bundle, mixed media and a product with a long gallery. Transfer these first into a draft environment. Check the displayed order, variant behaviour, crops, mobile interaction and any supported video presentation in the chosen theme.
Use the rehearsal to discover problems in both the register and the process. A missing field may need to be added; an unclear naming rule may need revision. Keep a record of the correction and repeat the affected check. Fixing one visible page is insufficient if the same mapping issue will recur across hundreds of products during the main transfer.
Audit publication and retain a rollback reference
Compare the published product pages with the approved register after migration. Check selected variants, image order, broken references, alternative text and the presence of obsolete files. Prioritise products whose contents or options are easy to confuse. Record the completed checks so another team member can distinguish verified pages from those still awaiting review.
Retain the pre-migration mapping and approved source files according to your operating needs. They provide a reference if a later correction is required. For a media audit and replacement scope, send the catalogue structure and a representative product sample with the planned migration date, known gaps and the people responsible for product accuracy and publication.
Frequently asked questions
Is a successful media upload enough to confirm a Shopify migration?
No. Upload success confirms that a file reached the system, but not that it belongs to the correct product, appears in the right order or follows the intended variant selection. Test representative draft pages and inspect the published result against an approved product-to-media register before treating the migration as complete.
Should old product images be deleted during migration?
Separate the public catalogue decision from the archive decision. Remove superseded assets from active use after verifying replacements, while retaining the references your team needs for traceability. Do not delete uncertain source material simply to tidy a folder. Resolve its product version, approval status and potential future use first.
Related reading
Official resources
Platform resources checked on 18 October 2026. Confirm current category and account requirements before publishing your assets.