Introduction

Movebot has comprehensive support for Egnyte through the Egnyte API. Connecting to Egnyte uses OAuth to authorize.

Requirements

To connect to an Egnyte account in Movebot, you will need:

• To have access to an administrator account in Egnyte

• To have sufficient privileges to the content you want to migrate

• The Egnyte tenant must be licensed

Configuration Steps

1. Login to Movebot and create a new project or task

2. When configuring the source or destination, choose to Create new Connection

3. Select Egnyte from the list of available connections and set the connection name

4. Provide your Egnyte subdomain.

1. Click Connect to Egnyte and authorize the connection through the popup window.

2. Click Save and Test connection in Movebot

3. If the connection has succeeded, you can continue

Supported Features

Movebot has comprehensive support for Egnyte and is well-maintained.

Tags: egnyte

Introduction

Movebot supports Microsoft Windows using a lightweight agent that is installed directly on the file server, another server, or on a virtual machine.

The agent uses a shared token for authentication and communicates with Movebot's infrastructure via secure HTTPS calls. The Windows agent does not require any port forwarding or static IP addressing for migrations and is very simple to set up and run.

The agent can be run in a standalone fashion or as a service. For security reasons, we recommend not running the agent as a service during migrations.

Requirements

To connect Movebot to Microsoft Windows, you need:

• A suitable host to install the the agent on

• Remote access via RDP to the host

• An administrator account on the host

For a full list of requirements, see Server Requirements

Configuration Steps

1. Login to Movebot and create a new project or task

2. When configuring the source or destination, choose to Create new Connection

3. Select Microsoft Windows/Apple OSX from the list of available connections and set the connection name

4. Movebot will provide an Agent Connection token. Copy this token and download the agent. This token is only viewable once so be sure to copy it when viewing it.

5. Login to the remote Windows file server as an administrator

6. Install the agent and launch it

7. Paste the identifier token provided in Movebot and click Connect. After a few seconds, the status indicator should change to show it's connected.

8. Return to the Movebot interface, and Click Save and Test

9. If the connection has succeeded, you can continue

Supported Features

Movebot has comprehensive support for Microsoft Windows and is well-maintained.

Common Errors

Movebot supports bi-directional and tenant to tenant migrations with Windows Fileserver's. Below are common errors and questions related to scanning and migrating Windows Fileserver data.

Frequently Asked Questions

Tags: agent

Introduction

We are now recommending connecting to SharePoint with Application Access. This involves setting up a new application in Azure.

Recommendations

For best results when connecting to SharePoint Online in Movebot using Application Access, we recommend the following permissions:

• Licensed account with Application Admin or Global Admin roles.

• SharePoint domain/hostname on hand.

Configuration Steps

To connect to SharePoint you'll need to create an application in Azure, then use that application to connect Movebot and SharePoint.

Creating the application in Azure

1. Login to Movebot and create a new project or task

2. Choose to Create new Connection

3. Select Sharepoint from the list of available connections and set the connection name

4. Provide the non-admin SharePoint domain in the field required

6. Name the application. Keep the other fields as default and click Register.

7. Copy the Application ID from the "Overview" section and paste it into Movebot.

8. In Azure in the Application permissions, click API Permissions --> Add a Permission. Select Microsoft Graph, then Application Permissions.

Enable the following Permissions:

Directory.Read.All
Files.ReadWrite.All
SharePointTenantSettings.Read.All
Sites.Manage.All
User.ReadWrite.All

1. Next add the access, under Azure in the Application permissions, click API Permissions --> Add a Permission. Select Sharepoint, then Application Permissions.

Select the following permissions:

Sites.FullControl.All

1. Grant admin consent and finish the consent process.

Generating the client secret

Under the application configuration:

1. Click Certificates and Secrets -- > Client Secrets -- > New Client Secret. Provide a description and Add. Copy the Secret from the "Value" Field.

2. Return to Movebot and Paste the Secret "Value" into the appropriate field

Upload the certificates from Movebot

Finally, you will need to generate and download the client certificate from Movebot and upload it to Azure for authentication.

1. Under Step 3: click the button Generate and Download Certificate. You should get a PEM file download from Movebot.

2. In Azure - Click Certificates and Secrets -- > Certificates -- > Upload Certificate

3. Upload the file created in step 1

4. The thumbprint in Azure should match the one shown in Movebot

5. Return to Movebot and Click Save and Test connection in Movebot.

6. If the connection has succeeded, you can continue.

Video Guide

Common Errors

Movebot supports migrations to and from SharePoint Online as part of Microsoft 365. Below is a list of common issues users encounter during SharePoint migrations, along with troubleshooting guidance and answers to frequently asked questions.

Frequently Asked Questions

Supported Features

Tags: sharepoint

Introduction

Movebot uses the Google Drive API with delegate access, and we provide everything you need for quick authorization in Google Admin. Connecting to Google Workspace by delegate access provides Movebot access to user data and shared drives in the Google Workspace domain and full support for migrating Google Drive content.

Requirements

To connect Movebot to Google Workspace, you will need:

• A Google Workspace administrator account

• To be familiar with the Google Admin Centre

• To have access to the Shared Drives you wish to migrate

Configuration Steps

1. When configuring a new connection, select Google Workspace from the list of available connection types and give the connection a name

2. Enter your Google administrator account email address

3. Enter your domain (find this under "Manage domains" in Google Admin) .

4. Click "Create Service Account" - this will generate a Client ID

5. Use this Client ID when configuring domain-wide delegation in the Admin console, required to allow Movebot to access necessary data for migrations. Include the following OAuth scopes:

1. Test the connection

Common Errors

Movebot supports migrations of MyDrive and Shared Drive data within Google Workspace tenants. Below are common GWS Drive-specific errors, their resolutions, and answers to frequently asked questions.

Frequently Asked Questions

Supported Features

Movebot has comprehensive support for Google Workspaces and is well-maintained.

Tags: googledrive_domain

We built Movebot to make migrating and transferring data to the cloud simple and fast. Here you will find detailed documentation on how to use Movebot with different platforms.

Discover Movebot

Movebot Overview Video

Introduction

Connecting to Amazon WorkDocs is fast to set up and supported as a source connection in Movebot.

Requirements

To connect Movebot to an Amazon WorkDocs you will need:

• To generate an AWS access key

• To know the organization ID and region for the site you wish to transfer

Configuration Steps In Amazon

1. Login to your AWS Management Console and navigate to applications then IAM

2. Under IAM create a new permissions "migrations" policy and copy over the existing permissions using JSON option.

{ "Version": "2012-10-17", "Statement": [ { "Action": [ "workdocs:Download*", "workdocs:Get*", "workdocs:Describe*", "ds:DescribeDirectories", "ec2:DescribeVpcs", "ec2:DescribeSubnets" ], "Effect": "Allow", "Resource": "*" } ] }

1. Now create a new "migration" user and assign it our new policy using attach policies directly. Make sure this is the only policy assigned to the new user.

2. Under your new user's Summary page, on the right create new access key for an application running outside AWS. Note these down to use later.

3. Go back to the AWS Management Console and under settings on far left go "All services"

4. Click on "Amazon Workdocs" under Business Applications

5. Click on the settings on far left and now select "My sites"

6. Note down your Organization ID and the Amazon region in the url (e.g. us-east-1)

   1. If your Organization ID doesn't show up here - on the top right change your region to where you expect your workdocs to be hosted and repeat steps 5-8.

Configuration Steps In Movebot

1. Log in to Movebot, choose Create New Connection, select Amazon WorkDocs as the connection, and set a name.

2. Set the Access Key ID, Access Key Secret, the site's Organization ID, and the region it belongs to.

3. Save and Test connection in Movebot

Supported Features

Movebot is currently working on adding comprehensive support as a source for Amazon WorkDocs and is well-maintained

Tags: aws_workdocs

Introduction

Movebot has comprehensive support for Box through the Box API. Connecting to Box uses OAuth to authorize.

Requirements

To connect to Box in Movebot you will need:

• To have either Admin or Co-Admin access rights to Box

• To migrate all users, Admin access is required

• The Box tenant must be licensed

Configuration Steps

1. Login to Movebot and create a new project or task

2. When configuring the source or destination, choose to Create new Connection

3. Select Box from the list of available connections and set the connection name

4. Click Connect to Box and authorize the connection through the popup window

5. Click Save and Test connection in Movebot

6. If the connection has succeeded, you can continue

Common Errors

Movebot supports Box migrations for individual users and entire organizations. Below are common issues and questions related to scanning and migrating data from Box.

Frequently Asked Questions

Supported Features

Movebot has comprehensive support for Box and is well-maintained.

Tags: box

Introduction

Connect to BIM 360 Docs and set it as the source or destination to start migrating your files.

Requirements

To connect Movebot to BIM 360 Docs you will need:

• Account Admin access to BIM360

Configuration Steps

1. Login to Movebot and create a new project or task.

2. When configuring the source or destination, choose Create New Connection.

3. Select BIM 360 Docs from the list of available connections and set the connection name.

4. Provide BIM 360 API access to your BIM 360 Docs account by following these steps:

   • If you have access to more than one account, select an account.

   • Click Settings, and select the Custom Integrations tab.

   • From the Custom Integrations screen, click the Add Custom Integration button.

   • From the Add Custom Integration screen, select Document Management, and click Next.

   • From the Add Custom Integration screen, select I'm the developer option, and click Next.

   • Enter the Forge Client ID 0rY4yx0hc4JJOTxwkxykpZZkxAJip3ayph2CUHrLwLVQHAyt , and the App Name, and select the I have saved the Account ID information securely checkbox. Optionally add an App Description and App Logo.

   • Click Save. The name of the app will appear in the Custom Integrations screen.

5. Click Link to BIM 360 Docs and authorize the connection through the popup window.

6. Save and Test the connection in Movebot.

7. If the connection has succeeded, you can continue.

Supported Features

Movebot currently has partial support for BIM 360 Docs.

Tags: bim360

Introduction

Movebot has comprehensive support for Citrix ShareFile through the ShareFile API. Connecting to ShareFile uses OAuth to authorize.

Requirements

To connect to ShareFile in Movebot you will need:

• To have Admin access rights to ShareFile

• The ShareFile tenant must be licensed

Configuration Steps

1. Login to Movebot and create a new project or task

2. When configuring the source or destination, choose to Create new Connection

3. Select Citrix Sharefile from the list of available connections and set the connection name

4. Click Connect to Sharefile and authorize the connection through the popup window. Enter the account's subdomain prefix and click continue.

1. Click Save and Test connection in Movebot

2. If the connection has succeeded, you can continue

Common Errors

Supported Features

Movebot has comprehensive support for ShareFile and is well-maintained.

Tags: sharefile

Introduction

Movebot has comprehensive support for Dropbox Business and Dropbox Teams through the Dropbox API. Connecting to Dropbox uses OAuth to authorize.

Requirements

To connect to Dropbox Business online in Movebot you will need:

• To have access to the account owner account in Dropbox, or an Administrator

• The Dropbox account must be licensed

Configuration Steps

1. Login to Movebot and create a new project or task

2. When configuring the source or destination, choose to Create new Connection

3. Select Dropbox Business from the list of available connections and set the connection name

4. Provide the email address of your administrator account

5. Click Connect to Dropbox and authorize the connection through the popup window. You will be required to log in to Dropbox. Make sure you log in with the same account that you specified above.

6. Click Save and Test connection in Movebot

7. If the connection has succeeded, you can continue

Common Errors

Movebot supports bi-directional and tenant to tenant migrations with Dropbox Business. Below are common errors and questions related to scanning and migrating Dropbox Business data.

Frequently Asked Questions

Supported Features

Movebot has comprehensive support for Dropbox and is well-maintained.

Tags: dropboxfullbusiness

Introduction

Connecting to Outlook/0365 for Mailbox migrations is fast to set up and fully supported in Movebot. For this type of connection, Movebot uses the legacy EWS API.

Requirements

To connect Movebot to Outlook/0365, you will need:

• To have Global Admin access to Azure

• To be familiar with the configuring applications in Azure.

Configuration Steps

There are two steps to this process. The first is creating the application in Azure with the correct permissions. Next is configuring the connection in Movebot.

Creating the application in Azure

1. First, login to Azure as an administrator for your domain, and navigate to App Registrations.

2. Click New Registration

3. Specify a name for the new application. Leave the remaining fields as default, then click Register.

4. Make a note of the Application (Client) ID. This will be entered into your Movebot configuration.

5. Make a note of the Tenant ID. This will be needed in Movebot

6. Configure the permissions. Click API Permissions --> Add a Permission.

7. Select APIs my organisation uses, then search for Office 365 Exchange Online.

8. Select Application Permissions

9. And then check the permissions detailed below:

1. Click Grant admin consent for Couchdrop Demo and follow the consent process

2. Click Certificates and Secrets --> Client Secrets --> New Client Secret

3. Copy the Client Secret Value

Enable RBAC for listing users across the tenant

The EWS API does not allow access to the user database without an additional role.

2. Find Discovery Management

3. Add your admin user to the role.

Note: This role can take up to 24 hours to be reflected in the API. If you need to move forward immediately you can still do so without this role, you will need to map the users using the prefix manually mailbox:

Configure the connection in Movebot

1. Login to Movebot and create a new project or task

2. When configuring the source or destination, choose to Create new Connection

3. Select Office 365 Outlook (via EWS) from the list of available connections and set the connection name

4. Provide your tenant id. This is a UUID found when configuring the application.

5. Provide the Application Client ID copied from the configuration step above

6. Provide the Application Client Secret from the steps above

7. Provide the admin users email address

Common Errors

Movebot supports migrations too/from Outlook/Exchange Online for Microsoft 365. Below are common errors, causes, and resolutions, along with answers to frequently asked questions.

Frequently Asked Questions

Supported Features

Movebot has comprehensive support for Outlook Online (Office 365) and is well-maintained.

Tags: office365outlook

Introduction

Movebot can connect to any mailbox that supports an IMAP connection, including personal Gmail accounts.

Movebot connects to IMAP servers by you providing the Hostname and Port and a Username and Password combination.

Requirements

To connect Movebot to an IMAP Server you will need:

• Hostname and Port for the IMAP server

• A Username and Password for each source account

Configuration Steps

1. Login to Movebot and create a new project or task

2. When configuring the source or destination, choose to Create new Connection

3. Select IMAP Server from the list of available connections and set the connection name

4. Provide the Hostname for the IMAP server. Update the Port number if required.

5. Provide a Test/Default Username and Password. Note that IMAP credentials can be overridden per transfer, which allows you to configure and manage projects with multiple user accounts

6. Save and Test connection in Movebot

7. If the connection has succeeded, you can continue

CSV Formatting for IMAP Credentials for Multiple Users

When moving to/from an IMAP server, you can provide credentials for each user directly in the CSV file by specifying a "source_secret" and/or "destination_secret" column.

To add a CSV file with multiple users, within a project click Add Transfer and then Import Transfer from CSV in the dropdown.

The format for these columns shown below.

Example (IMAP source):

Supported Features

Movebot has comprehensive support for IMAP servers and is well-maintained.

Tags: imap

Introduction

Movebot connects to Exchange Servers using service account credentials and the server hostname.

Connecting Movebot to the Exchange Server requires giving Movebot permissions to access data.

Requirements

To connect Movebot to Exchange, you will need:

• Exchange Server credentials and server hostname

• Service account with Discovery Management Role

Configuration Steps

1. Login to Movebot, choose Create New Connection, choose Microsoft Exchange (EWS), and set the connection name.

2. Enter your Exchange Server EWS hostname. Example: exch01.mydomain.com note: please do not include the https:// prefix.

3. Provide the username for the service account, typically in the format of <username>@<exchange_domain>, e.g. Administrator@<exchange_domain>

4. Provide the password for the service account.

5. Provide Discovery Management permissions to the service account following these steps.

   1. Log in to your Exchange Admin Center (Exchange Control Panel), which can be accessed through the web at <domain_hosting_exchange>/ecp

   2. Log in to the administrator account

   3. Select the 'permissions' tab within the Exchange Control Panel

   4. Under Admin Roles select Discovery Management and click the '+'. button.

   5. Under members, add the user you are using on the Movebot configuration, then click save. It will take a few minutes for the new changes to reflect.

      • If permissions are incorrectly configured, Movebot will show the error message "The caller has not assigned any of the RBAC roles requested in the management role header".

6. Click Save and Test connection in Movebot

​

Common Errors

Movebot supports migration from Exchange On-Prem environments. Below are common errors users may encounter, along with troubleshooting steps and frequently asked questions.

Frequently Asked Questions

Supported Features

Movebot has comprehensive support for Exchange and is well-maintained.

Tags: exchange

Introduction

Connecting to pCloud is fast to set up and supported as a source connection in Movebot.

Requirements

To connect to pCloud in Movebot you will need:

• Username and password for the pCloud account or be able to connect via OAuth

Configuration Steps

1. When configuring a new connection, select pCloud from the list of available connection types and give the connection a name.

2. Connect to pCloud by clicking 'Link to pCloud' button, and log in to pCloud in the popup that comes up

3. After a successful login, click Save and Test Connection in Movebot

Transferring Multiple Users

In pCloud, it is only possible to connect a single user per connection, and impersonation via an admin user is not supported within pCloud. In order to transfer multiple users, a separate pCloud Storage Connection and project will need to be created for each user.

Supported Features

Movebot has comprehensive support for pCloud and is well-maintained.

Tags: pcloud

Introduction

Movebot supports moving files and folders to and from Wasabi.

Requirements

To connect to Wasabi in Movebot you will need:

• To have access to a Wasabi account with the AmazonS3FullAccess policy

• The name of the Wasabi Bucket and its region name

• An Access Key from Wasabi and Wasabi Access Secret Key

Configuration Steps

1. When configuring the source or destination, select Wasabi from the list of available connections and set the connection name

2. Provide the region that your Wasabi bucket is located in and the bucket name

   • This can be found in Wasabi under Buckets

3. Provide an access key and secret key from Wasabi. To do this the user will need to have the AmazonS3FullAccess policy

   • In Wasabi, navigate to Access Keys and select 'Create Access Key'

   • Copy and paste the access and secret key from Wasabi into Movebot

4. In Movebot, select Save and Test Connection

Supported Features

Movebot has comprehensive support for Wasabi and is well-maintained.

Tags: wasabi

Introduction

Movebot supports moving files and folders to and from Google Cloud Storage.

Requirements

To connect to Google GCS in Movebot you will need:

• To have access to a Google GCS account with Storage Admin access

• The name of the Google Cloud bucket

Configuration Steps

1. When configuring the source or destination, select Google Cloud from the list of available connections and set the connection name

2. Provide the name of your Google Cloud bucket

   • This can be found under Cloud Storage -> Buckets within Google Cloud

3. Upload your JSON service account file

   • This can be found in Google Cloud under IAM & Admin -> Service Accounts -> [Service Account Name] -> Keys

   • Ensure the Service Account has Storage Admin access so that Movebot has all the necessary permissions to migrate files

   • Select Add Key, and ensure the type is JSON

   • Upload this JSON document to Movebot

4. After uploading the JSON document, select Save and test the connection

Supported Features

Movebot has comprehensive support for Google GCS and is well-maintained.

Tags: gcloud

Introduction

Connecting to Google Workspaces for Mailbox migrations is fast to set up and fully supported in Movebot. Movebot uses the Google API with Delegate API Access.

Connecting to Google Workspaces by Delegate access provides access to User Data and Shared Drives in the Google Workspace Domain and full support for migrating Drive content.

Requirements

To connect Movebot to Google Workspace Gmail, you will need:

• To have a Google Workspaces Administrator Account

• To be familiar with the Google Admin Center

Configuration Steps

1. Login to Movebot and create a new project or task

2. When configuring the source or destination, choose to Create new Connection

3. Select Google Workspaces Gmail from the list of available connections and set the connection name

4. Provide an email address for an administrator account.

5. Provide the primary domain for your Google Workspace tenant

6. Click "Create Service Account"

7. Copy the identifier for the service account (created as part of the process above)

9. Search for "API Controls" in Google Admin

10. Click "Manage Domain Wide Delegation"

11. Click Add New

12. Provide the "client id" copied from Movebot as the client id

13. Provide the session scopes, (copy-paste from below)

https://www.googleapis.com/auth/gmail.readonly, https://www.googleapis.com/auth/gmail.insert, https://www.googleapis.com/auth/gmail.labels, https://www.googleapis.com/auth/gmail.modify, https://www.googleapis.com/auth/admin.directory.user, https://www.googleapis.com/auth/admin.directory.user.security, https://www.googleapis.com/auth/contacts, https://www.googleapis.com/auth/calendar

1. Save the new client connection in Google and return to Movebot

2. Click Save and Test connection in Movebot

3. If the connection has succeeded, you can continue

Common Errors

Movebot supports Google Workspace Mail migrations, including user mailboxes and calendar events. Below are common errors and frequently asked questions related to GWS Mail.

Frequently Asked Questions

Supported Features

Movebot has comprehensive support for Google Workspaces and is well-maintained.

Tags: googleworkspaces_gmail

Introduction

Movebot supports moving files to and from Amazon S3 buckets, as well as moving data between S3 buckets.

Requirements

To connect to Amazon S3 in Movebot you will need:

• To have access to an S3 account

• S3 Access Key and S3 Access Key Secret

Configuration Steps

1. When configuring a new connection, select Amazon S3 from the list of available connection types and give the connection a name.

3. In Movebot, select Save and Test Connection

Supported Features

Movebot has comprehensive support for Amazon S3 and is well-maintained.

Tags: s3 s3_compatible

Introduction

Movebot supports connecting to an SFTP server as a source and destination.

Requirements

To connect to an SFTP server in Movebot you will need:

• The hostname and port of the SFTP server

• An SFTP username with password or private key

Configuration Steps

1. When configuring the source or destination, select SFTP from the list of available connections and set the connection name

2. Provide the hostname and port for your SFTP server

3. Provide your username

4. Provide your password or private key (or both)

5. Select Save and Test Connection

Supported Features

Movebot has comprehensive support for SFTP and is well-maintained.

Tags: sftp

Tags: sharepoint

Introduction

Movebot supports moving files and folders to and from Backblaze B2.

Requirements

To connect to Backblaze B2 in Movebot you will need:

• To have access to a Backblaze B2 account

• An application key with read and write permissions

Configuration Steps

1. When configuring the source or destination, select Backblaze B2 from the list of available connections and set the connection name

2. Provide your Backblaze Key ID and Master Key

   • In Backblaze B2, this can be found under Application Keys. You may need to generate another key to view the Master Key. Copy both the Key ID and the Master Key into Movebot

   • When generating your key, ensure your key has 'Read and Write' permissions. This will allow Movebot to have access to your bucket and move data.

3. Provide your Backblaze Bucket ID

   • In Backblaze B2, this can be found underneath Buckets

4. In Movebot, select Save and Test Connection

Supported Features

Movebot has comprehensive support for Backblaze B2 and is well-maintained.

Tags: backblazeb2

Introduction

Movebot supports moving files and folders to and from Azure Files.

Requirements

To connect to Azure Files in Movebot you will need:

• To have access to an Azure account with the Storage File Data Privileged Contributor Role

• Access Keys for the Azure Storage Account

• The file share name from Azure

1. When configuring a new connection, select Azure Files from the list of available connections and set the connection name

2. Provide the Azure account name and account key

   • In Azure, you can find this by navigating to Storage Accounts and selecting the Storage Account you want to connect to. Then navigate to Access Keys. There you can copy the storage account name, and one of the access keys

3. You also need to provide the file share name of the file share that you want to use

   • In Azure, you can find this inside the Storage Account you want to connect to, and then navigate to File shares

4. Ensure your Azure Storage Account has the necessary permissions for Movebot to access your data

   • This can be found in Azure by selecting Access Control (IAM) and assigning the role Storage File Data Privileged Contributor to your account to allow Movebot to read and write your file shares

5. In Movebot, select Save and Test Connection

Supported Features

Movebot has comprehensive support for Azure Files and is well-maintained.

Tags: azure

Introduction

Movebot takes an unusual approach to mail migrations, using the same mechanics of Storage Migrations for mail, calendar, and contacts. Because of this, we recommend that you read through Data Migrations with Movebot as a precursor to reading this.

Supported Systems

Movebot currently has support for:

• Email from individual users and shared mailboxes

• Private and shared calendars

• Contacts

In the following platforms:

• Google Workspaces Gmail

• Exchange Server

• Outlook Online (Office 365)

• IMAP Server

Key Concepts in Movebot for Mailboxes

When configuring a mailbox migration in Movebot, there are a couple of key concepts that we have adopted to help make the process simple. It's useful to quickly skim through them to understand how we approach mailbox transfers differently.

Mailboxes are Built on Movebot

Using Movebot to perform email, calendar, and contact migrations uses the same process as with Data Migrations with Movebot.

Migrate Mail the Same Way as Files and Folders

Movebot extracts email, calendars, and contacts so that they behave like files and folders. This approach is a bit unusual, but has some key benefits. One benefit is that mailbox migrations support delta migrations natively, another is that mailboxes can be transferred to normal file storage, allowing you to back up mail with Movebot.

A major advantage to our approach is that Mailboxes can be cherry-picked. Because Movebot works with your mailbox as if it's a filesystem, you can pick and choose what content you move and use Movebot to reorganize and ignore certain folders inside mailboxes. This means you can include/exclude based on a filter or move mail between labels, users, and inboxes.

Delta Migrations

The delta functionality in Movebot is an overlooked gem. Most migration tools require a hard cutover, but with Movebot, the cutover process can be managed by the admin in a way that best suits them.

In Movebot, delta migrations iteratively migrate changes that have occurred since the first transfer using the modification time and other metadata by looking at a scan of both the source and the destination.

During a delta migration, Movebot will only transfer emails that have either been updated or newly created in the source.

Deltas can be ran as many times as needed, including months after the project was initially set up.

Quick Start Guide

Because transferring or migrating mailbox data uses the same process as files, simply follow the existing guide for Data Migrations with Movebot.

Frequently Asked Questions

Introduction

Movebot takes an unusual approach to calendar migrations, using the same mechanics of storage migrations for mail, calendar, and contacts. Because of this, we recommend that you read through Data Migrations with Movebot as a precursor to reading this.

Supported Systems:

• Google Workspaces Gmail

• Outlook Online (Office 365)

• Exchange Server

• IMAP Server

Quick Start Guide

Because transferring or migrating calendar data uses the same process as emails and contacts, simply follow the existing guide for

Important Additional Steps

1. To begin transferring calendars, you need to enable calendars. You can do this by clicking on a project, navigating to settings, then content options. There you will see checkboxes to include calendars/contacts. Make sure these are checked to be able to move calendars/contacts.

2. If you enable calendars, some more options for migrating your calendar pop up.

1. Configure Event Attendee Mapping (Optional)

Transferring an event re-invites the current attendees on that event when it is created in the destination.

Configuring Events Attendee Mappings allows you to provide mappings for the attendee emails on those events, so that for example all emails ending in @movebot.io are mapped to @newmovebot.io in the destination, and event invites are sent there instead.

Calendar FAQ

What properties get maintained when transferring a calendar event? - We aim to maintain as many properties on events as possible. These properties include the name, description, start/end times, recurrence information, attendees, the time the event was created & last updated, reminders, location, status, event type and original start time.

Introduction

Movebot supports connecting to a personal Dropbox account through the Dropbox API. Connecting to Dropbox uses OAuth to authorize.

Requirements

To connect to Dropbox Personal in Movebot you need:

• To be the account owner or have access to the Dropbox Personal Account

• The Dropbox account must be licensed

Configuration Steps

1. Login to Movebot and create a new project or task

2. When configuring the source or destination, choose to Create new Connection

3. Select Dropbox Personal from the list of available connections and set the connection name

4. Click Connect to Dropbox and authorize the connection through the popup window. You will be required to log in to Dropbox. Make sure you login with the same account that you specified above.

5. Click Save and Test connection in Movebot

6. If the connection has succeeded, you can continue

Supported Features

Movebot has comprehensive support for Dropbox and is well-maintained.

Tags: dropbox

Introduction

Connecting to Google Workspaces is fast to set up and fully supported in Movebot. Movebot uses the OAuth to authorize the connection.

Requirements

To connect to a Google Drive personal drive in Movebot you need:

• To be the account owner or have access to the Google Drive account

• The Google Drive account must be licensed

Configuration Steps

1. Login to Movebot and create a new project or task

2. When configuring the source or destination, choose to Create new Connection

3. Select Google Drive (Personal) from the list of available connections and set the connection name

4. Click to Link to Google

5. Click Save and Test connection in Movebot

6. If the connection has succeeded, you can continue

Supported Features

Movebot has comprehensive support for Google Workspaces and is well-maintained.

Tags: googledrive

Introduction

Movebot was built for data migrations and transfers. Our product has been specifically built to provide fast, simple, and cost-effective migrations.

Performing a data migration in Movebot is a relatively simple process that can be set up in a few minutes. This guide will give you an overview of how a migration is modeled and executed in Movebot with an explanation of some key concepts to help you navigate the project, along with an overview video demonstrating how Movebot works.

Video Overview

Key Concepts in Movebot

When configuring a migration in Movebot, there are a couple of key concepts that we have adopted to help make the process simple. It's useful to quickly skim through them to understand how we approach migrations.

#1 Copy vs Migrate

Movebot perhaps should have been called CopyBot as that's essentially what it does 99% of the time. Moving data infers that the content is no longer available at the source. Movebot doesn't move the data out of the source as in most cases this is not ideal and can be downright dangerous.

For this reason, Movebot copies the data and does not delete it or remove permissions during the migration process. For us, that is the job of the team running the migration, not the machines.

#2 The Project

Projects in Movebot are a collection of transfers that relate to the same source and destination. When configuring a migration, regardless of its size and scope, you must create a project. Projects use the same configuration settings and connect to the same source and destination systems.

In Movebot, you can create as many projects as you like and storage connections can be shared between them. For example, you can create a Google Workspace connection for a Google Workspace to SharePoint migration, then later create a project for Dropbox to Google Workspace and use that already-configured Google Workspace connection.

Projects include:

• A source and destination connection configuration

• Permission migration configuration

• Project-wide content inclusion and exclusion options

• Project-wide sanitization options

• Platform-specific options

• Ignored files

#3 Transfers and Jobs

Transfers and jobs are children of projects. They can be thought of as an individual job or folder mapping between the source and destination locations.

Transfer Mappings are analogous to Jobs, Transfers, Migrations.

• They are executed in relative isolation to other transfers

• They are composed of a single source folder to a destination folder

• All types are mapped with Transfer Mappings. Users, Team Drives, Servers, Network Drives, External Servers etc.

Launching migrations is done by starting transfers.

Transfers can be launched and executed more than once. Each time a transfer is executed, Movebot executes a scan and builds a picture of the migration.

#4 Files and Folders

When executing transfers, transfer mappings include child Files and Folders.

During the scan stage of a transfer, the scan will build out a complete picture of child folders and files under the transfer, including all targeted files and folders under this transfer.

#5 The Scan Stage

The first thing Movebot does when executing anything is run a scan.

Scanning is a fundamental step in the process and a tool in itself. The scan stage maps out and identifies files that are going to be moved, and how those files can and should be transferred to the destination.

The scan identifies and resolves a lot of issues before the transfer process begins and generates a snapshot of what we see in the source and how it will appear in the destination.

The scan functionality in Movebot is used internally as part of the migration, but it is also exposed as the Discovery Scan function on a project level. A discovery scan is purely informational and provides a high-level overview that can be used to scope out and plan your migration.

#6 The Transfer Stage

After confirming the scan results, you can initiate the transfer. Movebot handles all of the infrastructure management and scaling for you and automatically optimizes for best results.

While the transfer is ongoing you have access to the Performance Advisor. This gives you real-time stats about the transfer that is currently in progress.

Once the transfer is complete, Movebot will generate a post-transfer report so you can review your migration results.

#7 The Delta Migration

The delta functionality in Movebot is an overlooked gem. Most migration tools require a hard cutover, but with Movebot, the cutover process can be managed by the admin in a way that best suits them.

In Movebot, delta migrations iteratively migrate changes that have occurred since the first transfer using the modification time and other metadata by looking at a scan of both the source and the destination folders.

During a delta migration, Movebot will only transfer and update files that have either been updated or newly created in the source.

Deltas can be run as many times as needed, including months after the project was initially set up.

Quick Start Guide

Transferring or migrating data with Movebot generally comes down to the following process.

We recommend that you run a small test migration before proceeding with a large number of transfers. This will allow you to familiarise yourself with Movebot and gain confidence in configuration.

Step 1: Creation of a project

Projects in Movebot are a logical unit of separation. Projects have a source and destination connection, configuration settings, and child transfers.

To create a project, visit Movebot and Click Create Project. During the configuration stage, you will need to select or create a source and destination connection. You can find detailed information on setting up various connections under

Step 2: Project Discovery Scan

With any large migration, we recommend executing a project scan before adding folders. This step is completely optional, but very useful as it provides a high-level overview of the source and highlights potential issues with moving the data to the destination, before you get started.

The project scan is also a useful tool for adding folder mappings. On each folder or user, it provides:

• A hierarchical view of files and folders

• Totals and summary data

• File and folder sizes

• Conflicts and issues

• Overview of mapping status

• Sharing and permission information

Step 3: Mapping/Add Transfers

Before any data will be transferred, you will need to configure Transfer Mappings. Transfer mappings tell Movebot to move data from one location to another. They form the base unit of operations in Movebot and live under a project.

Creating transfer mappings is done from the project dashboard and can be done by selecting the source and destination folders individually or by uploading a CSV file of the mappings.

Step 4: Launch Transfers

Once transfers are created, they can be launched. Launching transfers stages them for execution.

Step 5: Investigate Failures

Movebot attempts to remedy all failures automatically, but there are often edge cases that we can't accommodate. Failures are shown under a job and can occur for various reasons.

Errors caused by intermittent issues will most likely be resolved in the next stage.

Step 6: Deltas and Cutover

The final and often most frequent stage in a migration with Movebot is running Deltas. With a full migration/transfer like what you launched in Step 4, Movebot will move all data from the source to the destination. With a Delta, we will only move files that have changed or are new in the source and not yet moved to the destination.

If files have changed or failed during the transfer in Step 4, they will be picked up with a delta.

Conclusion

Getting Help

Our support rocks, really it does, and it's free. Reach out to the team with any questions and we are always more than happy to lend a hand.

To run a scan, create a new Movebot project, connect your platforms, and follow the wizard. Once done, select Save and Exit.

You will find yourself at your migration project dashboard. Click on Run Discovery Scan.

From the Discovery Scan page, you can then click on Launch Scan Now.

You will be asked whether you wish to run a scan over the entire source platform or a specific location. We recommend scanning the entire source for cloud platforms and selecting the specific drive you wish to scan if you're working with on-prem servers.

Finally, you can click Launch Scan to kick off your pre-migration scan.

Introduction

Movebot supports moving files and folders to and from Azure Blob storage.

Requirements

To connect to Azure Blob in Movebot you will need:

• To have access to an Azure account with the Storage Blob Data Contributor role

• Access Keys for the Azure Storage Account

• The container name from Azure

Configuration Steps

1. When configuring a new connection, select Azure Blob from the list of available connections and set the connection name

2. Provide the Azure account name and account key

   • In Azure, you can find this by navigating to Storage Accounts and selecting the Storage Account you want to connect to. Then navigate to Access Keys. There you can copy the storage account name and one of the access keys

3. You also need to provide the container name that you want to use

   • In Azure, you can find this inside the Storage Account you want to connect to, and then navigate to Containers

4. Ensure your Azure Storage Account has the necessary permissions for Movebot to access your data

   • This can be found in Azure by selecting Access Control (IAM) and assigning the role Storage Blob Data Contributor to your account to allow Movebot to read and write your blob containers

5. In Movebot, select Save and Test Connection

Supported Features

Movebot has comprehensive support for Azure Blob and is well-maintained.

Tags: azureblob

Scans provide a list of warnings and issues that have been identified with the migration. These warnings are useful for highlighting issues before kicking off the migration.

To view warnings and predicted issues from a scan, open Content Options under the scan overview.

Clicking on an issue will provide a detailed description and a list of files/folders that are impacted.

You can also use Explorer/Navigator tab to see a tree view of all files and folders discovered by the scan. Clicking Show Simulation View will show an expected destination view of the migration.

Discover Movebot Features

Click an item below to learn more about Movebot features.

Data discovery is an important aspect of migrations and data lifecycle management. If you don't have the full picture in terms of your data, it is very hard to be able to perform any management tasks on that dataset. Movebot provides a fundamental tool to help solve this problem and provide detailed visibility into your dataset.

What information does a scan provide

Scans provide an aggregate and tree view of your connected storage engine. You are then able to navigate through that tree to view:

• File and folder counts

• Largest file and folders

• File types

• Duplicate files

• Sharing and permission information

• Empty folders

• Recently modified files and folders

• Potential migration issues

You can also use the scan to search for files and folders that match certain conditions.

Scan types

Scans can be executed on a single transfer or a complete project. Project discovery scans are useful as they provide the basis for a migration project and can be used to assist in reorganising data during the migration.

Transfer mapping are the building blocks for migrations in Movebot. After configuring a project, you will most likely want to add transfer mappings to it.

Transfer mappings tell Movebot which files and folders to move. Each transfer mapping is an isolated migration task that can be launched in isolation.

Example of Transfer Mappings:

Each user, team drive or folder that you want to transfer in Movebot needs to be covered by a transfer mapping.

Mappings can be added in a variety of ways. Learn more about how to add transfer mappings below:

Movebot provides a bunch of standardized reports, but it is also possible to create your own reports using the search console under the files/folders view and search for files or folders.

Under Files/Folders you can see all files and folders discovered in the scan. You can then use the filter to search for files/folders to find specific items.

You can manually use search expressions as below.

You can join queries together with an "and" operator:

{files.modtime > 1602629811} and {files.size > 1024}

Spaces and character cases are important and currently there is limited error handling.

Movebot is designed to be simple to use, but as expected, migrations carry a lot of complexities and nuances. When using Movebot to migrate small or large volumes of data, there are generally a few main stages outside of the initial configuration.

Stages of a Migration

User-to-user transfers are the simplest form of migration with Movebot. Movebot allows you to migrate all files and folders under one user's account to another. Additionally, you can configure it to only migrate cherry-picked folders from the source to the destination.

Adding a simple user to user mapping

Under the Project manager, click Add Transfer. select the source user and destination user then hit Save and Finalize.

You can also add customization options like filtering to only include/exclude specific files and folders.

By default, Movebot will always migrate data into a separate folder in the destination with a "migrated from" prefix. This is to prevent accidental data clashes and make reorganizing data after the migration easy for users. You can disable this by clicking "Migrate folder contents".

Configuring user to user via CSV

For scale, CSV files can be used to import large numbers of users. The CSV file should be in the format shown below.

source,destination
user:user1@couchdrop.io,user:newuser1@couchdrop.io
user:user2@couchdrop.io,user:newuser2@couchdrop.io

Movebot supports adding transfers directly from the scan results. This allows you to use the Explorer feature of the discovery scan to analyze the content and easily create mappings for multiple transfer projects using the same source and destination.

Adding Transfers from Explorer

After running a scan, check the Discovery Scan tab and choose Explorer to review the files and folders that Movebot has scanned. You'll also see an overview of errors and warnings, such as if you are attempting to map a drive in the source that is too large for the destination. If you click on one of these errors or warnings, the results will only show results that have that specific issue.

To add a Transfer from the scan results, simply highlight beside a folder, click the checkbox, and click Add Transfers. You can also pick to Ignore File, which can be useful for isolating objects that you do not want to move to the destination. If a folder or its subfolders are used in a transfer, Movebot will inform you with an icon beside the file name.

Mapped sub-folders

In the above screenshot, you may notice that one folder has a Mapped sub-folders notice. This means that while the folder at this level has not been mapped as a transfer, at least one sub-folder below has been.

This is useful to keep track of which folders you have mapped to both make sure you move all the data across and avoid moving the same folders multiple times.

Ignore subfolders mapped in other transfers

As a further safeguard from moving the same folder in multiple transfers, Movebot has the the option to ignore subfolders mapped in other transfers as part of the Content Options when setting up a transfer. When this default option remains checked, Movebot will ignore subfolders that have previously been mapped within the same project so that you don't have to manually exclude them one at a time.

This method allows you to run transfers much quicker, but keep in mind that if you intentionally want to transfer a folder to multiple locations, you will need to leave this option unchecked so that it won't be ignored.

Movebot supports Team Drives and Shared Drive migrations to and from any platform. Mappings can be created by simply selecting the Team Drive in the source and where you would like files and folders to be transferred to in the destination.

Team Drives show up in the root along with users.

Adding a Team Drive mapping

Click Add Transfer from the project overview and navigate through the source and destination selecting the folders on the source and the destination.

Migrating Permissions

We recommend using mapped network drives when migrating from a Windows file server as they are more robust than direct UNC mappings, but Movebot supports both methods.

UNC shares can only be configured manually and require a bit of syntactical magic. When adding a mapping from the project, click Configure folder paths manually then specify the UNC path to the remote server using the format shown in the example below.

For clarity, see the breakdown below:

/SERVER2/SharedFolder

The easiest way to add mappings to a project at scale is via a CSV file. CSV mappings are added to a project as individual transfers/move jobs and you can then treat them like any other mappings.

Uploading a CSV file

Within your project, click + Add Transfer. Select Import Transfers from CSV.

CSV Formatting

When executing a file migration, the CSV uses a simple source, destination format.

source,destination
/user:michael@couchdrop.io/Files,/user:donald@newdomain.io/Files
/sharepointsite:/sites/Accounting:/Documents,/teamdrive:Accounting

CSV prefixes can target special objects like users, drives, on-premises agents, or mailboxes.

CSV Formatting - IMAP Credentials

When moving to/from an IMAP server, you can provide credentials for each user directly in the CSV file by specifying a "source_secret" and/or "destination_secret" column.

The format for these columns are shown below.

Example (IMAP source):

source,source_secret,destination
/mailbox:michael@couchdropdemo.com,michael@couchdropdemo.com:P@ssw0rd1,/mailbox:michael@newdomain
/mailbox:chris@couchdropdemo.com,chris@couchdropdemo.com:P@ssw0rd2,/mailbox:chris@newdomain.com

Normally, Movebot will migrate all files and folders from the source folders to the destination with the exception of a few file types that are not supported by the destination. However, files can be manually excluded as well.

Movebot allows administrators to extend this functionality and define exclusion and inclusion rules. This can be done on a project level or on an individual transfer level.

Project Level Exclusion Rules

Project exclusion rules will apply to all migrations in a project. Administrators can define these rules under Content Options.

Individual Migration/Transfer Level Rules

The same options are available on an individual migration/transfer. These options extend what was already configured at a project level.

Additionally, you can change an individual transfer to only include files matching a certain set of rules. This is useful for carving up your project into chunks by file types or size.

Available Rule Types

Keeping Your Data Up to Date

In active environments, it’s common for files to be added or updated during a migration. Movebot’s Delta Migration feature helps keep your destination up to date by copying only the files that have been added or modified since the last transfer.

How Delta Migrations Work

Delta Migrations compare the source and destination using each file’s modification time (modtime). Only files that are new or have a more recent modtime on the source will be transferred. This reduces duplication and speeds up the process by skipping files that haven't changed.

Important: Movebot does not delete or move files at the destination. If you rename, move, or delete files or folders in the source, those changes will not be reflected in the destination. To avoid duplication or confusion, we recommend avoiding major restructuring during the migration process.

Enabling "Always Use Delta"

To enable Delta Migrations across all runs:

1. Go to Step 4 in your project settings.

2. Enable the “Only Include Changed Files/Objects” option.

This ensures Movebot will compare the source and destination before each transfer and skip any files that haven’t changed. Note: This option may increase scan time, but reduces transfer time by focusing only on what’s changed.

Running a Delta Migration Manually

You can manually launch a Delta Migration at any time. Here’s how:

1. Open your project.

2. Select the job(s) you want to run a Delta for.

3. Click Launch Scan or Transfer.

4. Choose Start Delta Migration.

Delta runs may take slightly longer to scan but are much faster during the transfer stage than full migrations. They can be run as often as needed and are particularly helpful for:

• Catching files that were created or updated during a prior transfer

• Cleaning up certain error types, such as:

  • Unknown errors

  • File-not-found

  • Checksum-mismatches

Mapping permissions allow you to configure translations between source and destination users and groups. This is used when migrating between two domains or from On-Prem to the cloud.

Example mapping syntax

Importing mappings from a CSV file

For situations where the username format is changing, you can add explicit mappings for each user. When migrating a large organization, you can create a CSV file of mappings that can be imported.

An example CSV file is:

source,destination
michael@couchdrop.io, michael.lawson@couchdropdemo.com
chris@couchdrop.io, chris.roy@couchdropdemo.com

Other Options

Tweak the permission migration further

As part of a scan, permissions will be scanned from the source. You can then use the scan results to inspect the permissions on the source. Make sure check Enable File/Folder Permission Preservation during setup to use this feature.

To check the permissions on an individual file or folder, go to Discovery Scan within your project, highlight your target item, and click *Details, then Sharing.

Downloadable reports

Additionally to the reporting available in the front end, you can download two reports on file permissions:

Permissions can be manually configured from a CSV file, or the Box collaborators report. When enabled, Movebot will not query for permissions in the source system, rather it will look for permissions in the provided CSV file.

CSV File Format

If you are not using the Box collaborators report, the format of the permissions CSV file is as shown in the example below.

filename,collaborator permission,collaborator login
/Case Studies,Editor,jack@couchdrop.io
/FolderX/Case Studies,Editor,jack@couchdrop.io

Box Collaborators Report

From your Box admin console, go to Reports > Create Report and click Select Filters on the row for the collaboration report.

If you want to migrate your entire organisation, you can leave the filters blank, or you can generate the report for specific users you wish to migrate.

Handling Failures with Confidence

While Movebot is designed to be reliable, occasional failures can happen—especially when dealing with varying cloud platforms and environments. The good news? Most issues are easy to fix, and failures are nothing to be afraid of.

We’re here to help you handle them with ease.

First Step: Resume Job / Rerun Failures

If you have a finished transfer with outstanding failures, your first action should be to Resume Job / Rerun Failures. This simply resets the status of any failed files and tries again. This action does not require a re-scan of the source data.

To rerun failures:

1. Open your project and select any jobs that have failures.

2. Click Launch Scan or Transfer.

3. Select Resume Job / Rerun Failures.

This often clears up transient or permission-based issues with minimal effort.

Secondary Option: Start a Delta Migration

If some failures persist—particularly with error types such as unknown errors, file-not-found, or checksum-mismatch—running a Delta Migration can be helpful.

Delta migrations scan for and retry transferring files that have changed, or failed previously, without reprocessing files that have already migrated successfully.

To start a delta migration:

1. Open the project and select any jobs that have failures.

2. Click Launch Scan or Transfer.

3. Select Start Delta Migration.

This is a safe and efficient way to retry specific problem files without restarting the entire job.

Investigating Persistent Failures

Movebot displays detailed failure information in the admin interface, including the original error message returned from the cloud platform. This can help pinpoint the reason a file failed to transfer.

Still Need Help?

If the reason for failure remains unclear, we’re happy to assist.

📩 Contact support at support@movebot.io Our team can review the issue and guide you to a solution.

Movebot uses dynamically launched and managed dedicated worker nodes to execute your migration when you launch it. Your data does not leave these nodes and they are terminated as soon as your migration is complete. Nodes are never shared between customers.

By default, we use compute resources within our San Francisco data center. You can adjust the geographic location of your migration to meet your performance or data sovereignty requirements.

You can find Data Localization options in any project under Settings --> Options in the section Migration Geographic Region.

Current available regions

Pausing and Resuming Transfer Jobs

Transfer jobs in Movebot can be safely paused and resumed at any time, giving you full control over the migration process.

How to Pause and Resume a Job

• To pause a job that is currently running, click Cancel/Pause Migration in the job menu.

• To resume, open the same job and click Resume Job / Rerun Failures.

When resumed, Movebot will pick up where it left off.

You can pause and resume migrations as often as needed without affecting already transferred data.

⚠️ Keep in Mind

If you click Start Full Migration, Start Delta Migration, or Start Data Only Migration instead of Resume Last Action / Rerun Failures, the job will start from scratch, requiring a re-scan of all previously scanned data.

Always use Resume Last Action / Rerun Failures to avoid unnecessary duplication and preserve your job's progress.

Movebot offers two distinct scheduling features for managing job execution. Scheduling can be used to perform a daily delta migration at a certain time, or to restrict the time a particular migration job will transfer data.

Scheduling Daily Execution

Migration jobs can be scheduled to launch daily at a certain time.

This feature is useful for syncing where the source dataset is still active and you want to perform a daily sync. Scheduling daily executions requires setting a daily start time and we recommend enabling Always Use Delta so Movebot is not migrating the same files every day without changes.

Scheduled Data Transfer Window

Movebot supports the ability to specify a time window when Movebot can move data in the transferring stage. Scheduling a data transfer window is done by specifying a start and end hour in UTC time.

Unlike when Scheduling Daily Executions, scheduling a data transfer window does not start the migration automatically; you must still start the migration. Once the migration reaches the transferring stage, Movebot will check to make sure we are inside the scheduled data transfer window. If outside the defined window, we pause the transfer.

.

Movebot has comprehensive support for Google Workspaces and Personal Google Drives through a variety of connectors.

Quick Start Guides

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.

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.

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

Tags googledrive

Like most cloud storage providers, Google Drive has limitations that impact migration performance.

Team drives are limited to 500,000 objects

Google limits Team drives to a maximum of 500,000 objects. Once you reach this limit, you are unable to add new objects to the team drive.

Folder nesting limit

A folder in a Shared Drive in Google Workspace can have up to 100 levels of nested folders. If a folder in the source has more than 100 subfolders, the data folder architecture will need to be restructured to fit in Google Workspace.

Google docs export limit

Google does not allow Documents/Sheets/Presentations greater than 11MB in size to be exported into standard Microsoft formats via their API. Files exceeding this limit must be manually exported directly from the Google web frontend.

Daily upload limit per user

For individual users, Google has a daily upload limit of 750GB per user. Once this limit is hit, rate limiting prevents new objects from being uploaded

Daily download limit per user

Depending on the tenant, there is an undisclosed download limit. We believe this limit is around 13TB per day, but it varies between tenants.

Rate limiting

Google rate limits API queries. This creates an ultimate bottleneck during migrations that we cannot surpass. Movebot has very high quota limits, so generally rate limiting does not impact the performance much beyond what is described above.

Tags: googledrive

When users share a MyDrive folder with another user, this folder shows up under "Shared With Me" in Google Drive.

Movebot does not migrate shared folders by default. If you want to include shared folders for a user migration/transfer, you can enable this under Content Options.

Migrating Shared With Me Content

To transfer shared folders as part of the migration, disable the Exclude SharedWithMe Content under Content Options in the project configuration.

With Exclude SharedWithMe Content disabled, Movebot will transfer all files owned by the migrating user in shared folders to the destination. You can expand this to include all files and folders with the options below.

Migrating into and out of SharePoint with users requires the SharePoint admin registered with Movebot to have access to users' OneDrive accounts. In SharePoint, admins do not have access by default to individual OneDrive accounts so access will need to be granted.

Granting Access to an Individual User

As long as you are a licensed Microsoft 365 Global Administrator, you can take ownership of a user’s OneDrive by following these steps:

1. Log into the Microsoft 365 Admin Center for your tenant

2. Open Active Users under the Users tab and search for the user whose files you need

3. Click on the Display name of the user

4. Open the OneDrive settings tab

5. Click Create link to files

Once the link appears, no further action is required.

Granting Access to all Users

For larger organizations, you can use PowerShell to automate granting permissions at scale.

1. Ensure you have the SharePoint PowerShell utilities installed:

Open PowerShell as Administrator and run:

Install-Module -Name Microsoft.Online.SharePoint.PowerShell

2. Create a new PowerShell Script in Notepad, substituting the fields as appropriate for your domain

#Set Runtime Parameters
$AdminSiteURL="https://couchdrop-admin.sharepoint.com"
$SiteCollAdmin="michael@couchdrop.onmicrosoft.com"

#Connect to SharePoint Online Admin Center
Connect-SPOService -Url $AdminSiteURL -Credential $SiteCollAdmin

$OneDriveSites = Get-SPOSite -Template "SPSPERS" -Limit ALL -IncludePersonalSite $True
Write-Host -f Yellow "Total Number of OneDrive Sites Found: "$OneDriveSites.count
​
ForEach($Site in $OneDriveSites)
{
	Write-Host -f Yellow "Adding admin to: " $Site.URL
	Set-SPOUser -Site $Site.Url -LoginName $SiteCollAdmin -IsSiteCollectionAdmin $True
}

Write-Host "Site Collection Admin Added Successfully!"

3. Run the PowerShell script. Once it has been completed, your SharePoint admin account should have access across the organization.

4. Be sure to include the -admin part of the URL when configuring $AdminSiteURL 5. If your account has 2FA configured, the -credential argument should be removed. Tags: sharepoint legacy_sharepoint onprem_sharepoint onedrive

There are two different options for ingesting mail for Google Workspace Accounts, the Import and INSERT method.

Import is the default method. This method imports mail with standard scanning and delivery functionality.

The INSERT method is an alternative method that bypasses scanning for older messages, and can increase transfer speeds. When enabled, you can choose to use INSERT for messages sent a minimum of 15 days earlier, and up to 120 days as the maximum start point.

Enabling the INSERT method for a project

To enable the INSERT method, execute the following steps:

• Login to Movebot and choose or create a project with Google Workspace Gmail as the destination.

• Go to the Content Options tab, and under Google Workspace Mail Options check the option for Use INSERT method for old emails. The default setting is for emails older than 30 days but this can be adjusted from 15 days up to 120 days.

Overview

When migrating between SharePoint Online (SPO) sites—whether across tenants or within the same tenant—preserving metadata like custom columns can be critical. Movebot now allows you to retain these metadata values during your migration, improving post-migration usability and data continuity.

What It Does

This allows you to transfer:

• Custom columns from SharePoint Document Libraries

• Metadata values associated with files

How to Enable

1. Open the "Options" tab from within your Project Settings

2. Check the box to enable "Include SharePoint Column Metadata"

Limitations

• Not supported in Ludicrous Mode

• Slower performance due to additional API requirements

• Beta feature– edge cases may not be fully supported

Recommendations

• Test first in a non-production environment

• Review sample files post-migration to verify metadata

• Only use in scenarios where metadata accuracy is more important than speed

Summary

The "Include SharePoint Column Metadata" option helps retain custom metadata during SPO migrations, enhancing the fidelity of your data. While in beta, it’s a valuable tool for more accurate and context-rich SharePoint transfers.

Introduction

To connect a Google Workspace account to Movebot, you need to delegate domain wide authority so Movebot can access your users and migrate them automatically.

Requirements

Delegating Domain-Wide Authority requires the following:

• A Google Workspace Administrator Account to access the Admin Console

• Familiarity with the Google Admin Console

• Client ID for Google generated in Movebot when configuring a Google Workspace connection

Configuration Steps

2. Select the Security tab. If you don't see Security, select Show More from the bottom of the menu list.

3. Choose Access and data control and then API controls.

4. In the Domain wide delegation section, choose MANAGE DOMAIN WIDE DELEGATION.

5. In the API clients section, click Add new. Paste the Client ID generated from Movebot into the Client ID field.

6. In the OAuth scopes (comma-delimited) field, paste the following:

https://www.googleapis.com/auth/drive,https://www.googleapis.com/auth/drive.file, https://www.googleapis.com/auth/admin.directory.user, https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.user.security

1. Click Authorize. Test that the connection in Movebot is successful to complete your configuration.

Google Drive allows users to create (mostly by accident) duplicate folders and files.

Which is the real "folder1"?

Google is the only platform that allows users to create this sort of mess.

How Movebot deals with duplication

Duplicated data creates two main issues for Migrations.

1. Most destination systems do not allow duplicate files and folders.

2. Tracking changes is impossible with files that are named the same.

To facilitate safe data transfer, Movebot will rename files and folders that have duplicate names.

This deduplication ensures files are not lost and the folder structure is maintained.

What Is Ludicrous Mode?

Ludicrous Mode is a high-performance migration mode that leverages SharePoint’s Migration API. This is a lesser-known, batch-based ingestion API designed to reduce the number of calls via the standard Microsoft Graph API. It offers significantly improved throughput, especially for migrations containing larges number of small files.

Key Benefits

Ludicrous Mode is ideal for:

• Projects involving high file counts and small files

• Reducing the likelihood of significant throttling during large-scale transfers

Filename Sanitization Differences

Ludicrous Mode requires stricter character sanitization than the Graph API. Specifically:

• Ampersands (&) and single quotes (') will be removed from file and folder names

• This behaviour is different from standard Graph-based migrations, which may preserve these characters