Troubleshooting “Move to Shared Drive” for External Files

Moving assets from personal storage or departmental folders into a Google Shared Drive is standard practice when organizing team projects. However, attempting to drag and drop a file owned by an external client, vendor, or personal @gmail.com account into a Shared Drive routinely triggers an error: “Ownership cannot be transferred,” or “Some items were not moved.” Because Google Shared Drives require that all hosted assets be owned by the hosting organization, direct migration of external files is technically blocked.

Quick Answer

You cannot move externally owned files into a Shared Drive because Google prohibits cross-domain ownership transfers. To place external content into your Shared Drive, right-click the file and select Make a copy (which generates an internally owned version you can move), or create a Shortcut pointing to the external file.

---

Why Google Drive Blocks Moving External Files

To understand why this error occurs, consider the fundamental technical difference between “My Drive” and a “Shared Drive”:

Storage Model Comparison:
My Drive:
[Individual Account A] ──> Owns the file
[Individual Account B] ──> Can view/edit file inside personal folder
(Cross-domain files can coexist in the same folder)

Shared Drive:
[Workspace Organization] ──> MUST own 100% of all hosted files
(External cross-domain accounts CANNOT relinquish ownership to your organization)

In a personal “My Drive,” a folder can contain files owned by ten different people across ten different companies. The folder simply acts as an organizer for direct links.

In a Shared Drive, all individual ownership is stripped. The organization itself becomes the legal and technical owner of every file, byte, and folder. Because Google Workspace does not allow an external account (e.g., contractor@gmail.com or vendor@partner.com) to automatically transfer its file ownership to your company’s domain, dragging an external file into a Shared Drive halts the operation.

---

Common Error Messages Associated with External Moves

Depending on how you initiate the move, Google Drive returns one of several diagnostic alerts:

1. “Ownership of this file cannot be transferred”: Appears when attempting to move an individual external file or reassign ownership in the sharing menu. See Error: “Ownership of this file cannot be transferred”.
2. “Some items were not moved”: Surfaces during bulk folder transfers where internal files migrate successfully, but external files are rejected and left behind in the source folder. See Error: “Some items were not moved” during Bulk Migration.
3. “Google Drive was unable to move your files”: A generic failure notification often caused when moving entire folder trees containing deeply nested external shortcuts or unowned assets. See Fix: “Google Drive was unable to move your files”.

---

Approved Workarounds for Ingesting External Files

Because direct migration is architecturally impossible for external assets, use one of the following methods based on your operational needs:

Method 1: The “Make a Copy” Workflow (Recommended for Static Documents)

Creating a copy generates an entirely new file instance. Because you create the copy within your corporate account, your organization owns the new file, allowing it to move freely into any Shared Drive.

1. Locate the external file in your “My Drive” or “Shared with me” view.
2. Right-click the file and select Make a copy.
3. A new file named “Copy of [Filename]” will appear in your Drive.
4. Drag and drop this new copy into the target Shared Drive.
5. Rename the file to remove the “Copy of” prefix if desired.

Trade-Off: The copy breaks the link to the original document. Any future updates made by the external owner will not reflect on your Shared Drive copy.

Method 2: The “Add Shortcut” Workflow (Recommended for Live Collaboration)

If you must maintain active collaboration with an external partner and need their live edits to reflect inside your directory, use a Google Drive shortcut instead of moving the file itself.

1. Right-click the external file.
2. Select Organize > Add shortcut.
3. In the directory browser, select Shared drives, navigate to the destination Shared Drive, and choose the target subfolder.
4. Click Add shortcut.

Live External Collaboration Model:
[External Domain] ──> Houses live master file (External Owner)
                             ▲
                             │ (Pointer Link)
[Your Shared Drive] ──> Contains .gshortcut pointer (Organized for team access)

Trade-Off: The external partner retains ownership and can revoke access or delete the master document at any time.

---

How to Handle Bulk Folders Containing Mixed Ownership

If you are moving a folder containing hundreds of files from “My Drive” into a Shared Drive, mixed ownership will cause the operation to fail partially:

1. Open the source directory in drive.google.com.
2. In the search box at the top, enter: parent:[FolderID] -owner:me (or simply inspect the Owner column in list view).
3. Select all files owned by other people and move them into a temporary folder labeled “External Assets – Do Not Move.”
4. Migrate the remaining folder (which now contains only files you own) into the Shared Drive. For folder move prerequisites, review Why You Can’t Move Folders from My Drive to a Shared Drive.
5. Create shortcuts inside the Shared Drive pointing back to the external items you isolated.

If files inside the directory appear unowned because the original creator’s account was suspended or deleted, follow the administrative recovery procedures in How to Reclaim Ownership of “Orphaned” Files before attempting migration.