A folder appearing inside a shared drive is not enough to prove that all the company files moved successfully. Some items may remain elsewhere, and people who could open the original folder may lose access. Treat the move as a small migration with a record of exceptions.

Before starting, write down the source folder, intended shared drive, responsible business owner and people who need access. Include an external accountant or contractor if they rely on the folder. Record important file links and identify who owns the contents; a folder assembled by several people can contain mixed ownership.

Check the move conditions

Google allows eligible work or school accounts to move content into shared drives. Folder moves require the appropriate manager role. Files owned outside the organisation cannot simply be moved into its shared drive. An administrator may also control whether editors can move files they do not own.

Inherited access needs particular attention. Moving a child folder does not carry over permissions inherited from its old parent. A customer who reached a document through the old parent may therefore need an intentional access arrangement in the destination. Do not grant the whole shared drive broad access just to avoid checking this.

Reconcile a pilot before the main move

Start with a small, non-sensitive test set that represents the ownership and permission patterns in the real folder. Inspect any move warning and download the list of unmovable items when offered. Google may create shortcuts for items it cannot move; a familiar folder tree can therefore conceal files still outside the destination.

Compare the result with the starting list. Open the actual files, inspect their location and ownership, and have an authorised colleague verify the access they need. Record exceptions separately instead of counting shortcuts as migrated originals. Only continue the larger move once you can explain the pilot result and preserve a recovery path for the source data.

References: Google Drive move guidance.