Move Product Photos from Google Drive to a SKU Library

Move product photos from Google Drive to an asset library by SKU destination, not by copying the Drive tree. The files that matter are the current pack shot, lifestyle frame, and crops for a sellable product. Their home is that product's page. Rebuilding Shared drives / Products / Final / Final2 as collections keeps the search problem. You only changed which app opens the same tree.

This is a product-catalog migration. It is a different job from leaving Google Drive for marketing and brand files. That post is logos, guidelines, and campaign art. This one is catalog media: which approved photos belong on which SKU.

If folders still work for a tiny catalog and one owner, stay. The symptom list for when they stop working is in when folder structure fails for product photos.

How this differs from a marketing-files Drive exit

Teams mix these up and then migrate the wrong pile.

	Marketing-files exit	Product-photo migration
What hurts	"Where is the latest logo?"	"Where is the current pack for this SKU?"
What to move	Brand kit, campaign finals	Approved pack, lifestyle, and crops for active products
What to leave	Docs, decks in progress	Scratch selects, RAW rejects, photographer proofing
Success	People stop hunting the wordmark in Slack	People open the SKU instead of a folder path
Wrong finish	Every old Shared Drive dumped into a DAM	The old tree cloned as collections named `Final2`

Read the marketing exit if brand files are the mess. Stay here if the mess is the catalog. A general DAM can hold both jobs. It will not decide for you which file is the navy front on PK-SNW-BIKE.

What to move first

Migrate what the site and marketplaces can ship this month. Leave the rest.

Move:

Active SKUs (in stock, on the roadmap, or still live on a channel)
The approved pack shot, the angles you actually use, and the lifestyle frames merchandising will ask for
Channel crops that differ from the master (Amazon, marketplace, ads) when those files are the ones that go live

Leave:

Unselected frames, RAW, and selects_v3 scratch
Proofing folders the photographer still owns
Dead SKUs and seasonal campaigns you will not republish
Brand PDFs and logo kits (different exit, linked above)

DAM migration write-ups in the ResourceSpace neighborhood (YetOnePro and similar, visible in 2026 search results) say the same practical thing: move active assets first, and turn folder names into metadata instead of cloning the tree. Confirm the current wording on their sites. The catalog version of that advice is stricter. Active means active SKUs, not "every folder someone opened this year."

Prep on Drive before you upload anything

Do this in Drive. Do not start by importing.

List SKUs that exist in the catalog. Use the codes merchandising, the PIM, or the shop already trust. A folder named snowman-bike-final is not a SKU until it matches one.
Mark three buckets per active product: live (approved pack, lifestyle, crops), archive (older approved sets you might need), scratch (do not migrate).
Dedupe the obvious copies. The same hero saved into Products, Shoots/March, and Ads/Q1 is one file with three paths. Pick the approved bytes. Delete or ignore the rest.
Fix names only where it is cheap. PK-SNW-BIKE_front.jpg matches more reliably than IMG_2841.JPG. Do not block the move on a perfect rename of the archive.
Write down who confirms. One owner, or a short list. "Anyone with the link" is how the wrong color becomes official.

If you want the ongoing habit after this project, organize product photos by SKU is the library-side version of the same rule.

Three shapes people actually buy

Search results for this job (checked Oct 2026) cluster into three shapes. They are not the same migration.

1. Layer on Drive (Pics.io-class)

Files stay in Google Drive. A DAM indexes them in place and adds fields, search, and permissions. Pics.io is the usual name for this: bring-your-own Drive or S3, metadata on top, no forced move. The honest case is political or technical: leadership will not move the bytes.

That is a layer, not a migration. SKU can be a custom field. It is not the structure unless your team fills it in forever. Read native asset library vs a Drive DAM layer and Sprout vs Pics.io. Those posts date Pics.io's public pricing (seat-based; checked through Oct 2026). Confirm on pics.io/pricing before you compare bills.

2. Import folders into collections (Stockpress-class)

General DAMs such as Stockpress sell a leave-the-drive story: import from Drive, map folders to collections, detect duplicates, then tag. That fits brand kits, campaigns, and mixed creative libraries. Product photos can live there if you impose the catalog yourself.

The failure mode is subtle. The import succeeds, collections mirror Final and Campaign_Spring, and six months later people still browse folders. You moved storage. You did not map files to SKUs. See Sprout vs Stockpress. That comparison dates Stockpress's public plans (free tier, paid from $99/mo as of Sep 2026). Confirm on Stockpress's pricing page before you buy.

A related narrative (Digitile, StoreConnect, and similar storefront helpers) bulk-attaches Drive URLs to product codes in a shop admin. That can update a PDP. It is not a shared library your team searches next season. Treat it as a channel attach, and only if that vendor's current docs match what you need.

3. Match files onto SKU pages

The destination is the product. You upload the approved set, the library suggests a SKU from the filename and the catalog, and a person confirms. Pack, lifestyle, and crops for that item sit on one page. Empty products are allowed. Orphan folders are not the goal.

This is the path when the question you hear is "what is on this SKU?", not "which collection did we import?"

Question	Layer on Drive	Folders to collections	Match onto SKUs
Do bytes leave Drive?	No	Yes, into the DAM	Yes, into the product library
What is the unit?	File, plus fields you maintain	Collection (often the old folder)	SKU
Who stops a bad match?	Your tagging discipline	Whoever cleans collections later	A confirm step before the file is on the product
Done when?	Search on Drive is good enough	People browse the new collections	People open the SKU for the live set

Checklist: SKU-path migration

Use this if you chose shape 3. Shapes 1 and 2 have their own setup; do not mix the steps and call it one project.

Export the live catalog (SKU, name, and the variant key you actually sell).
Create those products in the library first, including shells with no files yet.
From Drive, pull only the live bucket for a bounded set. Start with your top sellers or one category, not the whole Shared Drive.
Upload that set. Keep scratch and RAW out of the batch.
Review suggested matches. Filename plus catalog is a shortlist. Fix the SKU when the guess is wrong. A lifestyle frame named for a campaign needs a human more often than a pack shot named for the code.
Confirm. Nothing should show up as the product's media until that confirm.
Open ten SKUs at random. You should see pack, lifestyle, and crops together, or a conscious gap (no lifestyle yet), not a mystery folder.
Tell the team the new rule in one sentence: current product photos live on the SKU. Drive still holds docs, drafts, and anything you marked scratch.
Repeat for the next category. Archive and dead SKUs wait until someone has a real reason.

The handoff for a new studio drop, after this backlog is moving, is the same confirm habit: from studio shoot to SKU library.

Mistakes that waste the migration

Importing everything. Ten years of rejects make the new library as noisy as the Shared Drive. Small and trusted beats complete and polluted.
Cloning Final / Final2. If the folder name was a joke in Drive, it is still a joke as a collection. Map to SKUs that exist.
Trusting filenames with no confirm. Auto-match is useful. Blind trust is how color A lands on color B. Camera-roll names (IMG_2841) should not score as a SKU on their own.
Calling it done while folders are still search. If Slack still asks "which Drive folder?" the migration is a second copy, not a home. Point people at the SKU and stop adding new approved files to the old tree.
Inventing SKUs from folder names. bike-new-NEW is not in the catalog. Attach the file to the real code or leave it out.
Treating a shop URL attach as the library. Linking a Drive file to a product code can update one channel. The team still needs one place that holds pack, lifestyle, and crops together.

How Sprout handles this migration

Sprout at usesprout.app is a SKU-centric library for this job:

Open a SKU and see pack shots, lifestyle, and crops together.
Drop a shoot, or upload the approved product media you exported from Drive.
Suggestions come from the filename and the catalog.
A person confirms before the file enters the library.

There is no Drive connector to turn on. Sprout does not sync a Shared Drive, and it does not run an automated import of every folder. You choose the files, you upload them, you confirm the match. Publishing to Shopify or a marketplace is a separate step. This guide does not claim that push.

If you need the bytes to stay in Drive, use a layer (shape 1), not Sprout. If you need a general brand library with folder import, look at shape 2. For the wider Drive comparison, see DAM vs Google Drive for a small business.

Next step

Pick one category of active SKUs. Upload the approved pack and lifestyle. Confirm the matches. Leave the rest of the Drive tree where it is until that category is a place people trust.

usesprout.app

FAQ

Is moving product photos the same project as leaving Drive for brand files?

No. Brand files are logos, guidelines, and campaign art. Product photos have to land on a SKU. You can do the brand exit and still have catalog chaos, or the reverse. Split the work.

Do I have to copy the whole Shared Drive?

No. Move approved media for active SKUs. Leave scratch, RAW, and dead products. A full import feels productive and usually recreates the mess.

Is a folder-to-collection import enough?

Only if you then map those files onto real SKUs and stop using the old folders as search. Importing Final2 as a collection is a storage move. It is not a catalog.

What if filenames do not contain the SKU?

Upload them anyway if they are approved. Expect more manual matches. Suggestions help when the name or the catalog text is close. A person still confirms. Do not wait for a perfect rename of the archive before you move the obvious pack shots.

Can we keep a DAM layer on Drive instead of migrating?

Yes, when the hard rule is that originals stay in Drive. That is a layer: metadata and search on the files you already have. It is a different decision from hosting product media on SKU pages. Pick one system of record for current catalog photos so people are not checking both.