Direct Answer: How Do Enterprise Teams Import Assets From Google Drive and Legacy Cloud Storage Into a DAM Without Breaking Permissions or Creating Duplicates?
To migrate or ingest campaign files from Google Drive into an enterprise DAM without opening public sharing links or creating duplicate files, teams use an App-User OAuth Connector (driveBrowse, scanDriveLink, importDriveFiles) paired with Automated Folder Hierarchy Resolution (resolveUploadFolders), SHA-256 Deduplication (AssetDuplicatesDialog / dedupeStorageCleanup), and background AI Vision Auto-Tagging.
In 2026, almost every external creative agency, freelance retoucher, and production house still stages raw shoot selects inside Google Drive folders. The traditional workflow for bringing those files into the corporate DAM is painful and insecure: a producer downloads a 15 GB ZIP archive onto their local laptop hard drive, unzips 300 files, manually recreates the subfolder structure inside the DAM, and re-uploads everything over their home Wi-Fi connection.
Key Takeaways
- Cloud-to-Cloud Ingestion Eliminates the "Laptop Bottleneck": Using an authorized Google Drive connector (
GoogleDriveImportDialogandDriveLinkImport) transfers files directly from Google's servers into your private DAM storage without downloading gigabytes to a local laptop first. - App-User OAuth Preserves Least-Privilege Security: Each user connects their own Google account via OAuth (
driveBrowse), ensuring they can only browse and import Google Drive folders they actually have permission to view—never exposing a company-wide super-admin Drive token. - Preserve Nested Folder Structures Automatically (
resolveUploadFolders): Whether dragging a nested local directory tree (DragDropUpload) or importing a Drive folder, automatic folder path resolution maps or creates the matchingFolderhierarchy inside your workspace. - Deduplicate Before Storage Bloat Accumulates: Automated duplicate detection (
AssetDuplicatesDialogandStorageDedupPanel) identifies identical files across folders so migrations never double your storage bill.
Comparison: Manual ZIP Download/Re-Upload vs. Cloud-to-Cloud Drive Ingestion
| Migration & Ingestion Step | Manual Download & Re-Upload | Mediasphere Cloud-to-Cloud Drive Import |
| :--- | :--- | :--- |
| Network Path | Drive → Producer's Laptop → Home Wi-Fi → DAM | Direct server-side ingestion (importDriveFiles) |
| Permission Model | Often requires setting Drive links to "Anyone with link can view" | Scoped App-User OAuth connector + scanDriveLink |
| Folder Hierarchy | Flattened or manually recreated one folder at a time | Automated resolveUploadFolders preserves parent/child Folder trees |
| Metadata & Tagging | 100% manual entry after upload | Automatic AI vision tagging (autoTagAsset) on ingestion |
| Duplicate Prevention | None—same logo/font uploaded 15 times across project folders | AssetDuplicatesDialog & dedupeStorageCleanup |
Step-by-Step: Executing a Zero-Downtime Google Drive to DAM Migration
Step 1: Connect via Scoped App-User OAuth (GoogleDriveImportDialog)
Instead of asking IT to hand over a global service account key, individual producers or DAM librarians click Import from Google Drive in the Assets workspace.
- If not yet connected, they complete a one-click Google OAuth consent flow scoped strictly to read-only Drive file selection.
- Using
driveBrowse(or pasting a folder/file URL intoDriveLinkImport/scanDriveLink), they inspect folders, file sizes, and MIME types directly inside Mediasphere (DriveFileRow).
Step 2: Map Target DAM Folders & Security Classifications (resolveUploadFolders)
Before starting the import, the user selects:
- The target destination
Folderin Mediasphere (or letsresolveUploadFoldersmirror the source subfolder structure). - The default
security_classification(Public,Internal,Confidential, orRestricted). - Baseline
tagsorcustom_fields(such asClient,Campaign, orShoot Date) to apply across the entire batch.
Step 3: Server-Side Ingestion & Format Normalization (importDriveFiles)
When the user clicks Import Selected Files:
importDriveFilesvalidates workspace storage capacity (validateStorageQuota), streams the binary files from Google Drive into Mediasphere's private storage, and creates theAssetrecords.- Specialized format helpers (
heicConvert.jsx,heicEmbeddedJpeg.js,normalizeImagePreview,extractDesignPreview) ensure that iPhone.HEICshoot photos and design files generate crisp web-viewable thumbnails (thumbnail_url) automatically.
Step 4: Background AI Vision Enrichment (autoTagAsset)
As each imported asset lands in the DAM, the background AI vision pipeline extracts ai_description, ai_tags, ai_categories, and dominant_colors. Within minutes, thousands of legacy files that used to be named IMG_4021.HEIC are searchable by visual content, color palette, and scene type.
Step 5: Deduplication & Legacy Storage Hygiene (dedupeStorageCleanup)
During large migrations from shared drives, teams inevitably discover that the same master brand logo, product cutout, or B-roll clip was copied into 12 different campaign folders over the years.
- Open the Asset Duplicates Dialog (
AssetDuplicatesDialog) or the admin Storage Dedup Panel (StorageDedupPanel) to identify duplicate files by size, name, and checksum, and consolidate redundant copies while preserving collection and project references.
Handling Apple .HEIC, Design Files & Multi-Format Conversions
Modern creative workflows involve far more than standard JPEGs:
- iPhone & On-Set
.HEICPhotos: Mediasphere automatically extracts embedded previews (heicEmbeddedJpeg.js) and converts.HEICfiles (heicConvert.jsx) so Windows and web reviewers never see broken image icons. - On-Demand Format & Resolution Transformation (
convertAssetFormat/transformAsset): Need a high-res.TIFFor.PNGproduct asset converted to a lightweight.WEBPor.JPGfor a landing page? Authorized users can transform and export derivatives without opening Photoshop.
Frequently Asked Questions (FAQ)
If an agency shares a Google Drive folder link with us, can we import it directly?
Yes. Using the Drive Link Import tab (DriveLinkImport and scanDriveLink), you can paste a shared Google Drive folder or file link, preview the contents, and import selected assets directly into your target Mediasphere folder.
Does importing from Google Drive modify or delete the original files in our Google Drive?
No. Mediasphere's Google Drive connector operates strictly as a non-destructive read-and-copy ingestion pipeline. Your original files in Google Drive remain completely untouched.
How does Mediasphere handle nested folder drag-and-drop from a Mac Finder or Windows Explorer window?
When you drag an entire multi-level folder tree from your desktop into DragDropUpload, Mediasphere inspects the relative file paths, calls resolveUploadFolders to create or match every parent and child Folder record in your workspace, and places each asset into its exact corresponding subfolder automatically.