# Sharing and Ownership

Google Drive provides a high level of flexibility in its sharing model in comparison to other storage providers. This additional flexibility creates issues when migrating to a new Google Tenant or another storage provider like Dropbox.

&#x20;

### Team drives vs Shared folders

There are some subtle differences between Team Drives and Shared folders.

|                            | Team Drives             | Shared Folders                                                                                                                        |
| -------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Who owns the content       | The organisation        | The individual user who created each file or folder.                                                                                  |
| Can permissions be removed | No                      | <p>Permissions can be customised at any level.</p><p>The sharing user, can be removed from subfolders created by external users. </p> |
| File limitations           | 400,000 files per drive | None                                                                                                                                  |
| Content can be orphaned    | No                      | Yes                                                                                                                                   |

&#x20;

The most important thing to remember here is around ownership. In a **Team Drive**, the **organization** owns the content, not individual users. In a **Shared Folder**, the **individual** that creates the content owns it. This means, <user1@google> shares a folder with <user2@google,> and then <user2@google> creates a file or folder, it is owned by <user2@google> and <user2@google> can revoke <user1@googles> access to it.&#x20;

This flexibility can cause data loss and orphaned data, whereby the parent folder has been deleted and the child no longer has a parent and so cannot be found.&#x20;

This approach to ownership is great for individual users, but a nightmare for organizations, as organizations lose control over their data.&#x20;

&#x20;

### Migrating MyDrive data with Movebot

Movebot takes a pragmatic approach to solving this problem and normalizes the ownership model so that it works for organizations and is compatible with other content systems like Dropbox, Box, and Office365.&#x20;

During a migration, content discovered under a particular user's root becomes their content in the destination. Permissions can still be assigned, and that content can be shared with anyone, but the ownership stays under the migrating user.&#x20;

This ensures that the organization has control over the data.

&#x20;

### Migrating invisible data in MyDrive

If users have created complex sharing rules in shared MyDrive folders, then the migrating user may not be able to see data that lives in their shared folders.&#x20;

Movebot can detect this, by enabling "Search for unreachable content"

![Screen\_Shot\_2022-04-05\_at\_9.11.53\_AM.png](https://community.movebot.io/hc/article_attachments/4618761899919/Screen_Shot_2022-04-05_at_9.11.53_AM.png)

Unreachable data will then be flagged.&#x20;

{% hint style="warning" %}
Note: Enabling this option does slow down the calculating stage, but disabling the option can lead to data loss, as any files that meet the criteria won't be moved.&#x20;
{% endhint %}

If you are unsure about enabling this option, contact support at <support@movebot.io>.

\
Tags googledrive
