LogoLogo
Movebot HomeLogin
  • Welcome
  • CONNECTIONS
    • SharePoint Online
    • Google Workspace Drives
    • Windows File Server
    • Dropbox Business
    • Egnyte
    • Box
    • BIM 360 Docs
    • Amazon WorkDocs
    • Citrix ShareFile
    • Google Workspaces Gmail
    • Outlook Online (Office 365) EWS
    • Exchange Server
    • IMAP Server
    • pCloud
    • Block Storage
      • Amazon S3
      • Azure Files
      • Azure Blob
      • Google GCS
      • Backblaze B2
      • Wasabi
    • Other Connectors
      • SFTP Server
      • Google Drive (Personal)
      • Dropbox Personal
      • SharePoint via Application Access
  • Features
    • Overview
    • Data Migrations with Movebot
    • Mail Migrations with Movebot
    • Calendar Migrations with Movebot
  • Using Movebot
    • Overview
    • Scan and Discovery
      • Project Discovery Scan
      • Searching Scan Results
      • Adding Transfers from Scan
      • Warnings and Issues
    • Transfer Mapping
      • Add User Mappings
      • Add Team/Shared Drives
      • Add Network Mappings
      • Import CSV Mappings
      • Excluding Content
    • Permissions and Metadata
      • Mapping Permissions
      • Scanning permissions
      • Manual Permissions
    • Transfer Execution and Cutover
      • Deltas and Changes
      • Failures and Errors
      • Pausing/Resuming
      • Scheduling
      • Data Localization
  • Platforms Guides
    • Overview
    • Google
      • SharedWithMe content
      • Sharing and Ownership
      • Performance and Limits
      • Deduplication of files/folders
      • Delegating Domain Wide Authority
      • Mail ingestion methods
    • SharePoint
      • Granting OneDrive Access
      • Performance Limits and SharePoint Ludicrous Mode
    • Windows Fileservers
      • Server Requirements
      • Proxy Configuration
      • Non-GUI Environments
      • Running the Movebot Agent as a Service
      • Logging and Debugging
    • Dropbox
      • Namespaces and Limitations
    • Others
      • Exchange Web Services (EWS)
        • How to disable EWS throttling
  • Troubleshooting
    • Performance and Speed
    • Errors and Failures
      • Common Errors
        • Error: user-not-active
        • Error: token-expired
        • Error: unknown-error
        • Error: user-not-found
        • Error: file-not-found
        • Error: invalid-filename-characters
        • Error: duplicate-file-name
        • Error: permissions-mapping-incomplete
        • Error: access-denied
        • Error: uploaded-size-mismatch
    • Hipaa Regions
  • Login to Movebot
Powered by GitBook
On this page
  • Team drives vs Shared folders
  • Migrating MyDrive data with Movebot
  • Migrating invisible data in MyDrive

Was this helpful?

Export as PDF
  1. Platforms Guides
  2. Google

Sharing and Ownership

Learn about Sharing and Ownership within Google Drive platforms.

Last updated 11 months ago

Was this helpful?

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.

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

Permissions can be customised at any level.

The sharing user, can be removed from subfolders created by external users.

File limitations

400,000 files per drive

None

Content can be orphaned

No

Yes

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, shares a folder with and then creates a file or folder, it is owned by and can revoke access to it.

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.

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

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.

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.

This ensures that the organization has control over the data.

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.

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

Unreachable data will then be flagged.

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.

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

Tags googledrive

Screen_Shot_2022-04-05_at_9.11.53_AM.png
user1@google
user2@google,
user2@google
user2@google
user2@google
user1@googles