Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Learn how to schedule transfer jobs.
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.
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.
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.
Note: When outside the transfer window, the migration will remain in the Transferring state, but no data will be migrated
.
Learn about logging and debugging with regards to Windows file servers.
The Windows agent has a collection of logfiles that can be useful for debugging issue. Our support team might also ask for them from time to time.
You can find these logs under C:\Users\%username%\AppData\Local\CouchdropCloudConnector
Tags: agent
Learn how to connect to SharePoint online via Application Access
Tags: sharepoint
This page has moved to
Connections
Learn how to connect Movebot to different storage engines.
Features Overview
Learn about using Movebot for different data lifecycles and management tasks.
Using Movebot
Learn about the different stages and capabilities of Movebot.
Platform Guides
Learn about the intricacies of common cloud platforms and how to manage them.
Troubleshooting
Troubleshoot Movebot. Learn about common issues and errors.
Learn how to connect to an IMAP server.
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.
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
Login to Movebot and create a new project or task
When configuring the source or destination, choose to Create new Connection
Select IMAP Server from the list of available connections and set the connection name
Provide the Hostname for the IMAP server. Update the Port number if required.
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
Save and Test connection in Movebot
If the connection has succeeded, you can continue
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):
source,source_secret,destination
/mailbox:[email protected],[email protected]:P@ssw0rd1,/mailbox:michael@newdomain
/mailbox:[email protected],[email protected]:P@ssw0rd2,/mailbox:[email protected]
For help with CSV mappings, get in touch with support via [email protected]
Movebot has comprehensive support for IMAP servers and is well-maintained.
Email Messages and Folders
Fully Supported
Tags: imap
Learn about how Movebot scans permissions.
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.
Additionally to the reporting available in the front end, you can download two reports on file permissions:
Permissions Report
A CSV export of all permissions detected on the source by file and folder.
Applied Permissions Report
A CSV export of applied permissions
Movebot supports all of the major data platforms, learn about the details of them in relation to data migrations and Movebot
Movebot has two options for mail ingestion for Google Workspace Accounts
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.
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.
Error Type
user-not-active
Relevant Store
All
A user not active error occurs when attempting to move an inactive user account. What 'activated' means in each platform can differ, but typically will mean that the user license has been disabled or deactivated from within the platform.
The user may not be licensed
The user is not enabled or expired
Activate the user in the storage platform by ensuring the user is not disabled and has an active license.
Learn about the scan tool in Movebot
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.
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.
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.
Learn about 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.
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.
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.
This feature is currently in beta and may change. Use with caution in production and test thoroughly in staging environments.
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.
This allows you to transfer:
Custom columns from SharePoint Document Libraries
Metadata values associated with files
Open the "Options" tab from within your Project Settings
Check the box to enable "Include SharePoint Column Metadata"
Not supported in Ludicrous Mode
Slower performance due to additional API requirements
Beta feature– edge cases may not be fully supported
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
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.
Learn about general performance and speed in Movebot
Movebot has been built architecturally to be optimized for speed. In most cases, this means you will not need to make any adjustments to settings for your migration to perform quickly. There are however a few details that are useful to understand when trying to determine how quickly your migration will run.
For most migrations, rate-limiting is going to be the number #1 bottleneck. Rate-limiting is a mechanism used by API providers to prevent abuse and to limit the impact of buggy API consumer applications on other customers.
Most cloud storage providers implement some level of rate-limiting and it's important to be aware of this as a limiter of your migration's performance.
Identifying rate-limiting
If your migration is being impacted by rate-limiting, it will be visible in the Performance Advisor graphs. The Performance Advisor provides a project-level summary of performance metrics.
What can be done about rate-limiting
Generally, we are at the mercy of the cloud platforms in terms of rate-limiting, but there are a few tricks with each platform if things are not progressing as quickly as you would like.
If you believe rate-limiting has become a problematic bottleneck in your migration project, reach out to our team via [email protected] and we can take a look at your project.
Learn about how Movebot handles Failures and Errors.
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.
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:
Open your project and select any jobs that have failures.
Click Launch Scan or Transfer.
Select Resume Job / Rerun Failures.
This often clears up transient or permission-based issues with minimal effort.
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:
Open the project and select any jobs that have failures.
Click Launch Scan or Transfer.
Select Start Delta Migration.
This is a safe and efficient way to retry specific problem files without restarting the entire job.
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.
If the reason for failure remains unclear, we’re happy to assist.
📩 Contact support at [email protected] Our team can review the issue and guide you to a solution.
Learn about how to use Movebot to customise and manage your migration
Learn how to add team/shared drives to transfers.
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.
Click Add Transfer from the project overview and navigate through the source and destination selecting the folders on the source and the destination.
Movebot supports moving both team/shared drives and the associated permissions. To find out more about migrating permissions, see our section on Permissions and Metadata.
Learn how to manually map 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.
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,[email protected]
/FolderX/Case Studies,Editor,[email protected]
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.
Learn how to connect to Sharepoint Online with Application Access
We are now recommending connecting to SharePoint with Application Access. This involves setting up a new application in Azure.
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.
To connect to SharePoint you'll need to create an application in Azure, then use that application to connect Movebot and SharePoint.
If you're migrating data within a single tenant, create separate application registrations for the source and destination connections to avoid rate limiting.
Login to Movebot and create a new project or task
Choose to Create new Connection
Select Sharepoint from the list of available connections and set the connection name
Provide the non-admin SharePoint domain in the field required
Name the application. Keep the other fields as default and click Register.
Copy the Application ID from the "Overview" section and paste it into Movebot.
In Azure in the Application permissions, click API Permissions --> Add a Permission. Select Microsoft Graph, then Application Permissions.
Enable the following Permissions:
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:
Grant admin consent and finish the consent process.
Generating the client secret
Under the application configuration:
Click Certificates and Secrets -- > Client Secrets -- > New Client Secret. Provide a description and Add. Copy the Secret from the "Value" Field.
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.
Under Step 3: click the button Generate and Download Certificate. You should get a PEM file download from Movebot.
In Azure - Click Certificates and Secrets -- > Certificates -- > Upload Certificate
Upload the file created in step 1
The thumbprint in Azure should match the one shown in Movebot
Return to Movebot and Click Save and Test connection in Movebot.
If the connection has succeeded, you can continue.
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.
Tags: sharepoint
Learn to connect to an Egnyte account.
Movebot has comprehensive support for Egnyte through the Egnyte API. Connecting to Egnyte uses OAuth to authorize.
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
Login to Movebot and create a new project or task
When configuring the source or destination, choose to Create new Connection
Select Egnyte from the list of available connections and set the connection name
Provide your Egnyte subdomain.
Click Connect to Egnyte and authorize the connection through the popup window.
Click Save and Test connection in Movebot
If the connection has succeeded, you can continue
Movebot has comprehensive support for Egnyte and is well-maintained.
Tags: egnyte
Learn how to connect to Autodesk BIM 360 Docs.
Connect to BIM 360 Docs and set it as the source or destination to start migrating your files.
To connect Movebot to BIM 360 Docs you will need:
Account Admin access to BIM360
Login to Movebot and create a new project or task.
When configuring the source or destination, choose Create New Connection.
Select BIM 360 Docs from the list of available connections and set the connection name.
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.
Click Link to BIM 360 Docs and authorize the connection through the popup window.
Save and Test the connection in Movebot.
If the connection has succeeded, you can continue.
Movebot currently has partial support for BIM 360 Docs.
Tags: bim360
Learn how to connect to a pCloud account
Connecting to pCloud is fast to set up and supported as a source connection in Movebot.
To connect to pCloud in Movebot you will need:
Username and password for the pCloud account or be able to connect via OAuth
When configuring a new connection, select pCloud from the list of available connection types and give the connection a name.
Connect to pCloud by clicking 'Link to pCloud' button, and log in to pCloud in the popup that comes up
After a successful login, click Save and Test Connection in Movebot
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.
Movebot has comprehensive support for pCloud and is well-maintained.
Tags: pcloud
Learn how to connect to an Amazon S3 account
Movebot supports moving files to and from Amazon S3 buckets, as well as moving data between S3 buckets.
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
When configuring a new connection, select Amazon S3 from the list of available connection types and give the connection a name.
In Movebot, select Save and Test Connection
Movebot has comprehensive support for Amazon S3 and is well-maintained.
Tags: s3 s3_compatible
Learn how to connect to Google GCS (Google Cloud Storage)
Movebot supports moving files and folders to and from Google Cloud Storage.
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
When configuring the source or destination, select Google Cloud from the list of available connections and set the connection name
Provide the name of your Google Cloud bucket
This can be found under Cloud Storage -> Buckets within Google Cloud
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
After uploading the JSON document, select Save and test the connection
Movebot has comprehensive support for Google GCS and is well-maintained.
Tags: gcloud
Learn how to connect to Wasabi
Introduction
Movebot supports moving files and folders to and from Wasabi.
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
When configuring the source or destination, select Wasabi from the list of available connections and set the connection name
Provide the region that your Wasabi bucket is located in and the bucket name
This can be found in Wasabi under Buckets
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
In Movebot, select Save and Test Connection
Movebot has comprehensive support for Wasabi and is well-maintained.
Tags: wasabi
Learn how to connect to an SFTP server
Movebot supports connecting to an SFTP server as a source and destination.
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
When configuring the source or destination, select SFTP from the list of available connections and set the connection name
Provide the hostname and port for your SFTP server
Provide your username
Provide your password or private key (or both)
Select Save and Test Connection
Movebot has comprehensive support for SFTP and is well-maintained.
Tags:
Learn how to connect to a personal user's Google Drive account.
Connecting to Google Workspaces is fast to set up and fully supported in Movebot. Movebot uses the OAuth to authorize the connection.
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
Login to Movebot and create a new project or task
When configuring the source or destination, choose to Create new Connection
Select Google Drive (Personal) from the list of available connections and set the connection name
Click to Link to Google
Click Save and Test connection in Movebot
If the connection has succeeded, you can continue
Movebot has comprehensive support for Google Workspaces and is well-maintained.
Tags: googledrive
Learn how to run a project discovery scan.
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.
Learn how to Movebot's scan results.
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:
Spaces and character cases are important and currently there is limited error handling.
Learn about how Movebot gives Warnings and Issues.
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.
Learn about transfer mappings in Movebot
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:
Learn how to add User Mappings.
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.
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".
For scale, CSV files can be used to import large numbers of users. The CSV file should be in the format shown below.
Learn how to add network mappings for file servers
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
Learn about how to exclude content from transfers.
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 exclusion rules will apply to all migrations in a project. Administrators can define these rules under Content Options.
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
Learn about Data Localization options
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
Learn how Movebot deals with deduplication of content in Google
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.
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.
Although Google to Google transfers would support duplication, Movebot does not allow this behavior as it creates a risk of data loss.
Connect Google Workspace to Movebot with a Client ID and domain-wide delegation
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.
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
Select the Security tab. If you don't see Security, select Show More from the bottom of the menu list.
Choose Access and data control and then API controls.
In the Domain wide delegation section, choose MANAGE DOMAIN WIDE DELEGATION.
In the API clients section, click Add new. Paste the Client ID generated from Movebot into the Client ID field.
In the OAuth scopes (comma-delimited) field, paste the following:
Click Authorize. Test that the connection in Movebot is successful to complete your configuration.
Learn about working with proxy configuration for file servers.
In networks where internet access is only allowed behind a proxy server some additional manual configuration is needed.
Steps:
1. Install and run the agent
2. Set the token
3. Stop the agent and then add the proxy configuration manually
You will need to locate the Movebot configuration file, normally it's located in the directory, C:\Users\%username%\AppData\Local\CouchdropCloudConnector.
Open the file with Notepad, or something similar, and you will find a JSON with a base config.
4. Edit the "proxies" section, adding an HTTP and HTTPS proxy with the syntax below:
5. Save the file, and start the agent again.
Proxy URL syntax examples:
To debug connection issues, check the log files located in the same directory as the configuration files and feel free to contact support for help at [email protected]. Tags: agent
Learn about connecting the Movebot agent in a Non-GUI enivronment
First, you need to install and configure the Movebot agent (Couchdrop Cloud Connector) on your workstation.
On your workstation, browse to the folder
Copy configuration.conf to a location you can access on the new server and also copy the Couchdrop Cloud Connector installer. Now you can uninstall the Agent from your workstation.
On the server, you will need to open the command prompt as an administrator. Once you have done that, you will need to locate where you copied your installer and configuration.conf file on the server.
Below is an example command of how to install silently, but your path may vary on your location.
Once this is complete, you need to apply the configuration to the server. To do this, copy your configuration.conf.
On the server, you will need to browse to this location. You may need to create the CouchdropCloudConnector folder under your Appdata\Local as the agent has not run yet.
Once you have completed installing the agent as a service and the service is running, you can check your Couchdrop Cloud Connector configuration folder and it should look similar to the image below
Learn how to run the Movebot Agent as a Service for file server transfers.
The Movebot Agent (Couchdrop Cloud Connector) can be run as a Windows service.
Installing the agent as a service requires some understanding of how Windows services work and the service must be configured to run as the same user that is performing the configuration.
Next in a command line, open the Couchdrop Cloud Connector folder located under Program Files and run the following command.
Next, open the service manager:
Find the service for "Couchdrop Cloud Connector" and open it.
Adjust the Log On configuration specifying the user account that you are logged in as the account to run the service under. This step is important as the agent configuration is stored under the user's profile. Without configuring the correct user, the service will not properly connect.
Finally, you can start the service. Once it's running, you can reopen the Couchdrop Cloud Connector configuration application and it should show the service as Running in Background.
Tags: agent
Here are the articles in this section
Uploaded Size Mismatch error is due to the file size not matching expectations after uploading to the destination.
There is a mismatch in the size of the downloaded file and the file we uploaded. This could indicate corruption of the file during upload or that we couldn't get all of the file to the storage provider.
Rerun failures or a new delta migration
Access Denied error means that Movebot does not have access to the file or folder
Access denied on folders can result in loss of data.
The account used to connect the Storage Connection does not have the appropriate permissions to access the file or folder
Reconnect the Storage Connection using an account with higher permission levels such as an Administrator account.
Provide the connected user appropriate permissions within the storage platform settings.
After attempting a fix, rerun failures or run a new delta migration to try to move the affected files or folders.
Learn about using Movebot with HIPAA data
Movebot supports HIPAA data through the use of a dedicated region. The HIPAA region is not enabled for all customers as it requires a BAA agreement with us first.
Reach out to sales or your account manager for this
When working with HIPAA data, Movebot customers are required to select the HIPAA region from the project settings.
To enable:
Login to Movebot
Select the Project
Click Settings --> Options
Change the default region from San Fran to "HIPAA Compliant Region"
You will need to change the region for each project. Not selecting the HIPAA will result in your migration not being strictly HIPAA compliant.
You can also follow our .
Login to Entra with Appliciation Admin or Global Admin account and register a new application at and create a new App Registration via Identity -> Applications -> App registrations
Resolution: Check that the correct Client ID is being used. Refer to Step 7 of the , to confirm you have provided the proper ID.
Resolution: Generate the necessary certificate and upload it to the registered application in Entra. Refer to "Upload the certificates from Movebot" section of
Pre-provision the user’s OneDrive using PowerShell ().
Read the full article .
Log in to .
Provide the S3 Access Key and S3 Access Key Secret, and optionally enter your S3 bucket name. For instructions on creating access keys, see this .
Connecting to a Google Workspace account is different. See for more information.
For help with CSV mappings, get in touch with support via
for your Google Workspace domain.
For more information on domain-wide delegation, see this Support article from Google: Tags: googledrive_domain
You can for configuration instructions. Once you have installed and configured the agent, you need to copy the configuration.
Now we need to set up the agent as a service. Follow the article . Be aware you don't need to install the agent again. You can go to the area of the article where it tells you to run the following command.
Wait for 30 seconds and verify the agent is working by doing a scan or another action in the . Tags: agent
Before starting, make sure that you have installed the Couchdrop Cloud Connector by Make sure you have run and configured everything properly and check that it is working. We recommend closing the desktop configuration app and systray application before starting the service.
Data Migrations
Movebot is the fastest and easiest data migration tool on the market. Learn how to move data with Movebot.
Mail Migrations
Movebot now supports email, calendars and contact migrations as well as Data migrations. Learn about them here.
Scan and Discovery
Scanning the source and destination provides a complete picture of your data. Making it easy to craft and navigate your migration project.
Transfer Mapping
Learn about adding transfer mappings to your project. Choosing which data is going to be moved to where.
Permissions and Metadata
Learn about configuring permissions and metadata in Movebot. Movebot has comprehensive support for permissions and metadata.
Transfer and Cutover
Learn about executing your migration project and cutting over users to the new platform.
Google Workspace
Learn how to connect Movebot to Google Workspace
Personal Google Drive
Learn how to connect Movebot to a personal Google Drive
Google Mail
Learn how to connect to Gmail to migrate mail, calendars and contacts
Directory.Read.All
Files.ReadWrite.All
SharePointTenantSettings.Read.All
Sites.Manage.All
User.ReadWrite.All
Sites.FullControl.All
SharePoint Document Libraries
Fully Supported
OneDrive Users
Fully Supported
Permissions
Fully Supported
Versions
Fully Supported
Modification Retention
Fully Supported
Automatic Sanitization
Fully Supported
SharePoint Column Metadata
Beta Feature
User Drives
Fully Supported
Shared Folders
Fully Supported
Permissions
Fully Supported
Versions
Fully Supported
Modification Retention
Fully Supported
Automatic Sanitization
Fully Supported
Projects files and folders
Fully Supported
Permissions
Not Supported
Versions
Not Supported
Feature
Supported in Movebot
Files and Folders
Supported as Source only
Modification Retention
Fully Supported
Feature
Supported in Movebot
Files and Folders
Fully Supported
Modification Retention
Fully Supported
Feature
Supported in Movebot
Files and Folders
Fully Supported
Modification Retention
Fully Supported
Feature
Supported in Movebot
Files and Folders
Fully Supported
Modification Retention
Fully Supported
Feature
Supported in Movebot
Files and Folders
Fully Supported
Modification Retention
Fully Supported
User Drives
Fully Supported
Versions
Fully Supported
Modification Retention
Fully Supported
Automatic Sanitization
Fully Supported
{files.is_dir == true}
Only match directories
{files.depth > 10}
Match files/directories that are greater than 10 directories deep
{files.depth < 10}
Match files/directories that are less than 10 directories deep
{files.size < 1024}
Match files smaller than 1KB
{files.size > 1024}
Match files larger than 1KB
{files.extension == "png"}
Match files with the extension .png
{files.modtime > 1602629811}
Match files modified after the unix timestamp provided
{files.modtime < 1602629811}
Match files modified before the unix timestamp provided
{files.modtime > 1602629811} and {files.size > 1024}
user:[email protected]
user:[email protected]
teamdrive:/Shared
teamdrive:/Archive/Shared
mailbox:[email protected]
teamdrive:/Archive/Mail
source,destination
user:[email protected],user:[email protected]
user:[email protected],user:[email protected]
/SERVER2
This is the hostname of the target file-sharing server you are connecting to.
If the original UNC path was \\SERVER2\SharedFolder, this is where SERVER2 came from.
/SharedFolder
The file share on the server
Files older than
Only match files that are older than
Files modified before timestamp
Only match files modified before the defined unix timestamp
File size greater than
Only match files with a size greater than
File/Folder name matches
Only match files with the following name. This field supports unix style wildcards
Path matches
Only match files with the following path. Field also supports unix style wildcards
New York
Digital Ocean NYC1
Toronto
Digital Ocean TOR1
Amsterdam
Digital Ocean AMS1
Singapore
Digital Ocean SING1
London
Digital Ocean LON1
Frankfurt
Digital Ocean FRA1
Tokyo
AWS ap-northeast-1
Dedicated/Self Hosted
Chat with the Movebot team for more information on this option.
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
{
...
"proxies": {
"http": "",
"https": ""
},
...
}
Simple, no username and password
http://<ip>:<port>
With username and password
http://username:password@<ip>:<port>
Socks
socks://<ip>:<port>
C:\Users\%username%\AppData\Local\CouchdropCloudConnector
C:\Couchdrop\couchdrop-cloud-connector-installer.msi /quiet
C:\Users\%username%\AppData\Local\CouchdropCloudConnector
.\couchdrop-cloud-connector-service.exe install
.\couchdrop-cloud-connector-service.exe install
services.msc
Error Type
uploaded-size-mismatch
Relevant Store
All
Error Type
access-denied
Relevant Store
All
Learn how to connect to Amazon WorkDocs
Connecting to Amazon WorkDocs is fast to set up and supported as a source connection in Movebot.
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
Login to your AWS Management Console and navigate to applications then IAM
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": "*" } ] }
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.
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.
Go back to the AWS Management Console and under settings on far left go "All services"
Click on "Amazon Workdocs" under Business Applications
Click on the settings on far left and now select "My sites"
Note down your Organization ID and the Amazon region in the url (e.g. us-east-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.
Log in to Movebot, choose Create New Connection, select Amazon WorkDocs as the connection, and set a name.
Set the Access Key ID, Access Key Secret, the site's Organization ID, and the region it belongs to.
Save and Test connection in Movebot
Movebot is currently working on adding comprehensive support as a source for Amazon WorkDocs and is well-maintained
Users, Files and Folders
Fully Supported
Permissions
Fully Supported
Tags: aws_workdocs
Learn how to connect Movebot to Citrix ShareFile.
Movebot has comprehensive support for Citrix ShareFile through the ShareFile API. Connecting to ShareFile uses OAuth to authorize.
To connect to ShareFile in Movebot you will need:
To have Admin access rights to ShareFile
The ShareFile tenant must be licensed
Login to Movebot and create a new project or task
When configuring the source or destination, choose to Create new Connection
Select Citrix Sharefile from the list of available connections and set the connection name
Click Connect to Sharefile and authorize the connection through the popup window. Enter the account's subdomain prefix and click continue.
Click Save and Test connection in Movebot
If the connection has succeeded, you can continue
Movebot has comprehensive support for ShareFile and is well-maintained.
User Drives
Fully Supported
Permissions
Fully Supported
Versions
Not Supported
Modification Retention
Fully Supported
Automatic Sanitization
Fully Supported
Tags: sharefile
Learn how to connect to Azure Files
Movebot supports moving files and folders to and from Azure Files.
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
When configuring a new connection, select Azure Files from the list of available connections and set the connection name
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
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
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
In Movebot, select Save and Test Connection
Movebot has comprehensive support for Azure Files and is well-maintained.
Feature
Supported in Movebot
Files and Folders
Fully Supported
Modification Retention
Fully Supported
Automatic Sanitization
Fully Supported
Tags: azure
Learn how to connect to Azure Blob
Movebot supports moving files and folders to and from Azure Blob storage.
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
When configuring a new connection, select Azure Blob from the list of available connections and set the connection name
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
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
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
In Movebot, select Save and Test Connection
Movebot has comprehensive support for Azure Blob and is well-maintained.
Feature
Supported in Movebot
Files and Folders
Fully Supported
Modification Retention
Fully Supported
Automatic Sanitization
Fully Supported
Tags: azureblob
Learn how to connect to a personal Dropbox account.
Movebot supports connecting to a personal Dropbox account through the Dropbox API. Connecting to Dropbox uses OAuth to authorize.
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
Login to Movebot and create a new project or task
When configuring the source or destination, choose to Create new Connection
Select Dropbox Personal from the list of available connections and set the connection name
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.
Click Save and Test connection in Movebot
If the connection has succeeded, you can continue
Movebot has comprehensive support for Dropbox and is well-maintained.
User Drives
Fully Supported
Versions
Fully Supported
Modification Retention
Fully Supported
Automatic Sanitization
Fully Supported
Tags: dropbox
Learn about calendar migrations with Movebot
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.
Because transferring or migrating calendar data uses the same process as emails and contacts, simply follow the existing guide for
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.
If you enable calendars, some more options for migrating your calendar pop up.
Include External Events (Recommended)
This includes all events if checked, including events not owned by the user. Keeping this unchecked prevents event duplication
Include External/Shared Calendars (Not Recommended)
This includes all calendars if checked, including calendars not owned by the user. Keeping this unchecked prevents event duplication
Ignore Events Older than 7 days (Recommended)
This will ignore events that were created more than 7 days ago. This is typically preferred, to avoid moving old events. You can uncheck this box to include all events in the migration
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.
*@google.com
*@microsoft.com
@google.com
@microsoft..com
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.
Learn about how Movebot handles Deltas and changed files.
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.
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.
To enable Delta Migrations across all runs:
Go to Step 4 in your project settings.
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.
You can manually launch a Delta Migration at any time. Here’s how:
Open your project.
Select the job(s) you want to run a Delta for.
Click Launch Scan or Transfer.
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
Learn about performance limitations with Google Drive.
Like most cloud storage providers, Google Drive has limitations that impact migration performance.
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.
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 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.
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
Depending on the tenant, there is an undisclosed download limit. We believe this limit is around 13TB per day, but it varies between tenants.
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
Learn about granting OneDrive access for SharePoint migrations.
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.
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.
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="[email protected]"
#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
Learn how to setup the windows agent on Windows 2012 R2.
Microsoft has deprecated Windows 2012 R2 however it is still widely in use in legacy environments and in some environments it is not possible to use a virtual machine to act as a jump host to transfer the data with Movebot.
In this guide - we will cover how you can setup and run the Movebot windows agent in this type of environment.
Running a migration directly on Windows 2012 R2 is not recommended as it requires using a legacy version of the Movebot/Couchdrop windows agent that is not as robust as more recent versions and may be unreliable. If possible - we recommend using a virtual machine to connect via SMB/CIFS to the legacy server instead.
To get started - you will need:
Administrator access to the server
A RDP session or physical access to the server
Basic knowledge of server administration
The storage authentication token from Movebot
To install and start the agent
Install the package downloaded above
Configure the agent manually
Start the installed process. The front end for the agent will fail to load properly.
Test the connection in Movebot
The agent uses a configuration file stored in the filesystem. When running the agent on windows 2012 - the GUI front end does not work so you will need to configure the process manually.
This is relatively easy:
Open the configuration file with notepad - creating it if it does not already exist.
C:\Users\%username%\AppData\Local\CouchdropCloudConnector\configuration.conf
Copy the JSON configuration below - with a valid storage_id
{"storage_id":"KEY_FROM_MOVEBOT_FRONTEND"}
Save the configuration file and start the Movebot agent again.
Error Type
token-expired
Relevant Store
Box, ShareFile, OneDrive
This error indicates that the authentication token used to connect Movebot to a storage platform (source or destination) has expired. Without a valid token, Movebot cannot continue scanning or migrating data.
The OAuth or API token used during initial connection has expired due to time limits set by the storage provider.
Project settings were modified mid-migration, triggering a refresh or disconnect of the active token.
The connection has been idle for an extended period.
The token was revoked manually or automatically by the platform (e.g., security policy or admin action).
Open your Project Settings.
Navigate to the Source or Destination section where the error occurred.
Click Manage Connection Settings and re-authorise the connection.
Avoid making changes to connection settings or project configuration while a migration is running, as this can increase the risk of token expiry.
Learn how to connect to Backblaze B2
Movebot supports moving files and folders to and from Backblaze B2.
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
When configuring the source or destination, select Backblaze B2 from the list of available connections and set the connection name
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.
Provide your Backblaze Bucket ID
In Backblaze B2, this can be found underneath Buckets
In Movebot, select Save and Test Connection
Movebot has comprehensive support for Backblaze B2 and is well-maintained.
Feature
Supported in Movebot
Files and Folders
Fully Supported
Modification Retention
Fully Supported
Tags: backblazeb2
Error Type
duplicate-file-name
Relevant Store
All
Duplicate File Name error is caused by having 2 files with the same name
The file has the same path as another file
Nothing needs to be done to resolve this - we perform de-duplication to ensure that your files do not end up with the same path
De-duplication causes the file name to be renamed and prefixed with (Dup 1), (Dup 2), etc
After attempting a fix, rerun failures or run a new delta migration to see if the error is resolved.
Error Type
user-not-found
Relevant Store
All
A User Not Found User error occurs when Movebot cannot find a user. This could be due to an invalid transfer mapping or by attempting to map a user that does not exist.
The transfer mapping is inaccurate and includes a user that does not exist
The username has a misspelling or other mistake
Ensure that your transfer mappings are accurate, and that the user actually exists. If you add transfer mappings with a CSV, there is a higher potential for this to occur. Adding mappings using the transfer modal can resolve this.
Error Type
invalid-filename-characters
Relevant Store
All
Invalid Filename Character errors are due to having an invalid name for a file.
The file has an invalid name for the store that it is being uploaded into
Add a filename transformation rule to modify the names of the files during the transfer
This is found under Project Settings -> Content Options
This cannot be done for email/contacts/calendars, only for files
Change the name of the affected files manually in the source.
After attempting a fix, rerun failures or run a new delta migration to see if the error is resolved.
Error Type
file-not-found
Relevant Store
All
File Not Found errors are caused by us not being able to find and download the file in the store.
The file has been moved
The file is not accessible due to permissions
The filename has changed
Check that the connected account has appropriate permissions to download the affected files.
After attempting a fix, rerun failures or run a new delta migration to see if the error is resolved.
Error Type
unknown-error
Relevant Store
All
Unknown Errors are errors that are not mapped to error types in Movebot.
Unexpected error caused in a storage provider's API
The error has not been categorised by us yet
A bug in our system
Run a delta. The error might have been temporary
Attempt to diagnose by viewing the underlying error from the storage API in the storage tracker
Reach out to support
Instructions to disable EWS throttling using your Microsoft 365 account
By default, Microsoft throttles EWS connections in order to limit simultaneous connections for security and infrastructure stability. In typical use, most users will not come across EWS throttling, but it is possible to hit this limitation during a migration due to the increased number of requests.
Throttling can be temporarily disabled for up to 90 days from within the Microsoft 365 account settings and requires an account with access to the Admin portal.
To disable EWS throttling you will need:
A Microsoft 365 account with access to the Admin portal
Permissions to submit Support requests in the Microsoft 365 admin center
Login to Microsoft 365 with an Admin account
Open the Admin panel from the list of apps
From the Sidebar, choose the tab for Support and then Help & Support. You may need to click Show All for the Support tab to appear.
A search bar will appear. Type in Increase EWS Throttling Policy.
An option will appear to Run Diagnostics. Click Run Tests and choose a duration that will cover the migration period.
You will receive a message that an update to the throttling policy has been started. This may take 15 minutes to take effect.
After at least 15 minutes have passed, you can check to see if the changes have taken effect. Repeat Steps 1-4 above. If the changes were successful, the Run Diagnostics window should now show a message that Exchange Web Services are not currently throttled.
An alternative method to disable EWS throttling is to create a Support ticket and ask the Microsoft Team to make the change for you.
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.
Ludicrous Mode is ideal for:
Projects involving high file counts and small files
Reducing the likelihood of significant throttling during large-scale transfers
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
Because of this, it is crucial not to toggle Ludicrous Mode partway through a migration. Switching modes mid-migration can result in duplication or delta inconsistencies, as filenames will be treated as different objects depending on which API handled them.
Enable Ludicrous Mode before starting a migration and keep it enabled for the entire duration of the job.
Do not enable/disable Ludicrous Mode if you have already started transferring data. Doing so will result in duplicate files/folders and delta failures due to differences in filename sanitization rules.
Ludicrous Mode can be enabled at the project level in Movebot. Before enabling:
Open your project settings.
Select 4. Options
Enable "Include only changed objects/files"
Open Advanced Options
Enable "SharePoint Ludicrous Mode"
If you have any questions, please contact [email protected] or reach out via the live chat.
Learn how to add transfers directly from scan results.
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.
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.
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.
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.
Learn about how to map permissions in Movebot
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
Group 1
Administrator
*
*@couchdropdemo.com
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
[email protected], [email protected]
[email protected], [email protected]
Tweak the permission migration further
Send Notification Invitations
Send email notifications to users when permissions are added.
This option is not supported by all cloud platforms.
Exclude Unmapped Permissions
Only include permissions for users that are included in the mappings.
This option is useful for preventing re-sharing with external users.
Exception Rules
Prevent permissions from being migrated under certain circumstances.
Learn about the ShareWithMe option when Google is the source.
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.
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.
Exclude Shared Content owned by another user
This option will filter files by owner.
All files in the shared folder will be transferred to the destination
Exclude Shared Content owned by a migrating user
This option will filter files by users in the project.
Files that are not owned by users included in the migration project will be excluded.
Learn about Sharing and Ownership within Google Drive platforms.
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.
There are some subtle differences between Team Drives and 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, 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.
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.
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.
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 [email protected].
Tags googledrive
Learn about how to debug and deal with errors and failures in Movebot
Movebot attempts to remedy all failures automatically, but there are some failure types that will require manual intervention and we cannot transfer the data across.
There are two main types of failures:
Fatal Failures
File or Folder Failures
Fatal failures occur when we cannot proceed with any transfers in a migration job and file or folder failures occur when there was an issue transferring or scanning a file or folder discovered under a transfer mapping (job).
Errors can be found on an individual transfer mapping basis under Error Tracker.
Errors and failures in Movebot are categorized by severity as described below.
Critical
Folder / Files failed to scan
Critical errors are generally very bad. These include an outright failure to scan a directory, which can lead to dataloss.
High
Could not create file x.txt
High severity errors are generally isolated to a single object. It is recommended that you address them on an individual basis.
Medium
File y.txt was ignored
Medium severity errors can normally be ignored, but should be noted as they can show incorrect configuration.
Low Severity
File !blah.txt was renamed to blah.txt
Low severity warnings are informational.
Fixing errors generally comes down to two approaches:
Adjustments in configuration or a manual transfer of the object
Running a Delta
If the root cause is not obvious and it cannot be fixed through configuration, then attempt to run a Delta. If running a Delta does not fix the issue, then reach out to support at [email protected].
Learn how to connect to a Box account.
Movebot has comprehensive support for Box through the Box API. Connecting to Box uses OAuth to authorize.
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
Login to Movebot and create a new project or task
When configuring the source or destination, choose to Create new Connection
Select Box from the list of available connections and set the connection name
Click Connect to Box and authorize the connection through the popup window
Click Save and Test connection in Movebot
If the connection has succeeded, you can continue
Movebot supports Box migrations for individual users and entire organizations. Below are common issues and questions related to scanning and migrating data from Box.
Movebot has comprehensive support for Box and is well-maintained.
Tags: box
When migrating data into, out of, or within SharePoint Online, Microsoft enforces strict throttling limits to ensure fair usage across tenants. These limits scale depending on how many licenses you have.
Resource Units (RUs) are how Microsoft measures the cost of API operations. Each action your migration tool performs consumes a specific number of RUs.
These limits apply daily across the entire tenant, regardless of how many apps are in use.
These limits apply daily per app registration, and per tenant.
Learn how to setup the windows agent on Windows 2008 R2.
Microsoft has deprecated Windows 2008 R2 however it is still widely in use in legacy environments and in some environments it is not possible to use a virtual machine to act as a jump host to transfer the data with Movebot.
In this guide - we will cover how you can setup and run the Movebot windows agent in this type of environment.
Running a migration directly on Windows 2008 R2 is not recommended as it requires using a legacy version of the Movebot/Couchdrop windows agent that is not as robust as more recent versions and may be unreliable. If possible - we recommend using a virtual machine to connect via SMB/CIFS to the legacy server instead.
To get started - you will need:
Administrator access to the server
A RDP session or physical access to the server
Basic knowledge of server administration
The storage authentication token from Movebot
To install and start the agent
Uncompress the downloaded modified agent from above
In the command line - run the agent using the batch file
Stop the agent - Ctl-C
Start the agent again:
Test the agent from Movebot
The agent uses a configuration file stored in the filesystem. When running the agent on windows 2012 - the GUI front end does not work so you will need to configure the process manually.
This is relatively easy:
Open the configuration file with notepad - creating it if it does not already exist.
Copy the JSON configuration below - with a valid storage_id
Save the configuration file and start the Movebot agent again.
It is not recommended to transfer permissions within Movebot as it is difficult to properly map permissions between disparate systems
Permissions Mapping Incomplete error means that not all of your permissions were able to be translated into a format usable at the destination.
There is a unique or uncommon permission on the file/folder that cannot be properly translated
There is a missing mapping for the permissions on the file
Provide a mapping for a username, email address or group to inherit the permission from
Exclude unmapped permissions
Answer: Box may not always display accurate or up-to-date file and folder counts due to a known platform limitation. For more details, refer to Box’s .
See the page to see how these limits can affect migration performance.
The modified windows agent - Contact for the download link
Install python3.8 -
Setup the configuration - see
User Drives
Fully Supported
Permissions
Fully Supported
Versions
Fully Supported
Modification Retention
Fully Supported
Automatic Sanitization
Fully Supported
Operation
Resource Units (per file or folder)
Scan Directory (Excluding Permissions and Version History)
2
Create Folder (Non-Delta)
2
File Upload
2
File Download
1
Tenant License Count
Daily Limit
0 – 1,000
5,400,000
1,001 – 5,000
10,800,000
5,001 – 15,000
16,200,000
15,001 – 50,000
21,600,000
50,000+
27,000,000
Tenant License Count
Daily Limit
0 – 1,000
1,200,000
1,001 – 5,000
2,400,000
5,001 – 15,000
3,600,000
15,001 – 50,000
4,800,000
50,000+
6,000,000
$> cd C:\Users\%username%\Downloads\<location of download>
$> INSTALL.bat
$> cd C:\Users\%username%\Downloads\<location of download>
$> INSTALL.bat
C:\Users\%username%\AppData\Local\CouchdropCloudConnector\configuration.conf
{"storage_id":"KEY_FROM_MOVEBOT_FRONTEND"}
Error Type
permissions-mapping-incomplete
Relevant Store
All
Learn how to connect to an Exchange Server
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.
To connect Movebot to Exchange, you will need:
Exchange Server credentials and server hostname
Service account with Discovery Management Role
Login to Movebot, choose Create New Connection, choose Microsoft Exchange (EWS), and set the connection name.
Enter your Exchange Server EWS hostname. Example: exch01.mydomain.com
note: please do not include the https://
prefix.
Provide the username for the service account, typically in the format of <username>@<exchange_domain>
, e.g. Administrator@<exchange_domain>
Provide the password for the service account.
Provide Discovery Management permissions to the service account following these steps.
Log in to your Exchange Admin Center (Exchange Control Panel), which can be accessed through the web at <domain_hosting_exchange>/ecp
Log in to the administrator account
Select the 'permissions' tab within the Exchange Control Panel
Under Admin Roles select Discovery Management and click the '+'. button.
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".
Click Save and Test connection in Movebot
Movebot supports migration from Exchange On-Prem environments. Below are common errors users may encounter, along with troubleshooting steps and frequently asked questions.
Movebot has comprehensive support for Exchange and is well-maintained.
Feature
Supported in Movebot
Email Messages and Folders
Fully Supported
Calendars
Fully Supported
Contacts
Fully Supported
Public Folders
Fully Supported
Tags: exchange
Learn about Mail, Calendar and Contact migrations in Movebot
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.
Movebot currently has support for:
Email from individual users and shared mailboxes
Private and shared calendars
Contacts
In the following platforms:
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.
Using Movebot to perform email, calendar, and contact migrations uses the same process as with Data Migrations with Movebot.
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.
Deltas move new emails automatically, without a hard cutover
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.
Because transferring or migrating mailbox data uses the same process as files, simply follow the existing guide for Data Migrations with Movebot.
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.
Within your project, click + Add Transfer. Select Import Transfers from CSV.
When executing a file migration, the CSV uses a simple source, destination
format.
source,destination
/user:[email protected]/Files,/user:[email protected]/Files
/sharepointsite:/sites/Accounting:/Documents,/teamdrive:Accounting
CSV prefixes can target special objects like users, drives, on-premises agents, or mailboxes.
/user:<username or email>
/user:[email protected]/Files
Boomsync, Box, Dropbox Business, Egnyte, Google Workspace, OneDrive, pCloud, Sharefile, Sharepoint, Legacy Sharepoint, Amazon Workdocs
/teamdrive:<team drive name>
/teamdrive:My Team Drive/Files
Boomsync, Dropbox Business, Egnyte, Google Workspace, Huddle, Sharefile
/teamdriveid:<team drive ID>
/teamdriveid:0AI2ezk6QbPvvUk9PVA/Files
Google Workspace
/<drive letter>:/<path>
/D:/Company Data/Files
Windows/OSX Agent
/<uncpath>/<path>
/REMOTESERVER/Shared Data/Files
Windows/OSX Agent
/mailbox:<email_address>
/mailbox:[email protected]/@MAIL/Inbox
Exchange, Office 365 Outlook, Google Workspace Gmail, IMAP
/sharepointsite:<site path>:<document library path>
/sharepointsite:/sites/Site1:/Docs
Sharepoint, OnPrem Sharepoint
/hub:<hub_name>
/hub:HubName/Files
BIM360
/project:<project_name>
/project:ProjectName/Files
BIM360
/bucket:<bucket_name>
/bucket:BucketName/Files
Amazon S3, S3 Compatible, BiFrost Cloud, Digital Ocean, Filebase, IDrive Cloud, Lyve Cloud, Wasabi
/publicfolders:<path>
/publicfolders:/Files
Exchange, Office 365 Outlook via EWS
No prefix
/Files
Backblaze B2, SFTP, Dropbox Personal, Google Cloud, Google Drive Personal, Azure Blob, Azure Files
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:[email protected],[email protected]:P@ssw0rd1,/mailbox:michael@newdomain
/mailbox:[email protected],[email protected]:P@ssw0rd2,/mailbox:[email protected]
For help with CSV mappings, get in touch with support via [email protected]
Learn about Namespaces and Limitations in Dropbox.
When migrating large datasets to Dropbox and when migrating permissions, namespaces inside Dropbox need to be considered.
Dropbox has published official documentation around namespace limitations that can be found in the following locations. Movebot recommends reading through this if migrating more than 1 million files.
Restrictions and Limitations for Team Deployments
Dropbox Performance Guide
Team folders and Shared folders in Dropbox typically reside in their own namespace. Each namespace has soft and hard limits around the number of files, users, and permissions associated with them.
Movebot has some features that can assist with navigating namespace limitations and properly structuring data when moving into Dropbox.
Identification of Potential Issues
During a Discovery Scan, Movebot will identify folders that should be split into separate team folders or namespaces inside Dropbox.
While Movebot does not force you to split large folders into smaller namespaces, it is highly recommended that you follow the guidance provided by the Discovery Scan and use this information to direct the structuring process.
Root Folder Namespace Creation
"Create a namespace per transfer" is an option that can be enabled from the Content Options page for a project or an individual transfer mapping.
When enabled, Movebot will create the root folder targeted by the transfer within a new namespace. If the root folder already has its own namespace, Movebot will not create an additional namespace.
Only the root folder will receive a unique namespace. Subfolders of the same transfer will not be created with separate namespaces unless they have permissions that break inheritance or are created by other transfers in Movebot.
Permission Namespace Creation
When migrating with permissions, Movebot will create a namespace for any shared folders with permissions that do not inherit permissions from the parent folder.
Movebot will automatically detect Shared folders with custom permissions that have not been inherited and create the shared folder/namespace in Dropbox with the required permissions.
If you remove the permissions inherited from a parent shared folder, a new namespace will be created inside Dropbox.
For assistance configuring large migrations to Dropbox, please contact [email protected]
Tags: dropbox dropboxfull dropboxfullbusiness
Learn how to connect to a Microsoft Windows File Server with Movebot
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.
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
Login to Movebot and create a new project or task
When configuring the source or destination, choose to Create new Connection
Select Microsoft Windows/Apple OSX from the list of available connections and set the connection name
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.
Login to the remote Windows file server as an administrator
Install the agent and launch it
Paste the identifier token provided in Movebot and click Connect. After a few seconds, the status indicator should change to show it's connected.
Return to the Movebot interface, and Click Save and Test
If the connection has succeeded, you can continue
Movebot has comprehensive support for Microsoft Windows and is well-maintained.
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.
Tags: agent
Learn how to connect to a Dropbox Business or Dropbox Teams account.
Movebot has comprehensive support for Dropbox Business and Dropbox Teams through the Dropbox API. Connecting to Dropbox uses OAuth to authorize.
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
Login to Movebot and create a new project or task
When configuring the source or destination, choose to Create new Connection
Select Dropbox Business from the list of available connections and set the connection name
Provide the email address of your administrator account
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.
Click Save and Test connection in Movebot
If the connection has succeeded, you can continue
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.
Movebot has comprehensive support for Dropbox and is well-maintained.
Tags: dropboxfullbusiness
Learn about requirements for connecting Movebot to file servers.
This software is run as an executable and can be also run as a service. While every migration is different, we recommend the resources below.
Below are the current versions of Microsoft Windows that are tested and supported.
If you’re working with an unsupported server OS, you can still migrate your data using this workaround:
Install the Windows Server Agent on a supported Windows machine.
Create a mapped network drive to the location of the unsupported server.
Configure the agent to access data via the mapped drive path.
This approach allows you to migrate data across your network without needing to install the agent directly on the unsupported system.
Need help setting this up? Contact [email protected].
Migrations are upload-intensive by nature and so the speed of your migration will be heavily dependant on your internal and external network capacity. We recommend 1Gbps uplink speed where possible.
If you are experiencing performance issues with the agent, we recommend running a speed test and checking your project settings to ensure you've selected migration region that is close to the agent.
Recommended Connectivity for Host
The Movebot agent communicates with the Movebot control plane and APIs exclusively via HTTPS. This means that no additional ports are needed to be opened.
If you have a restrictive firewall, we recommend deploying the Movebot agent on a virtual machine that can be whitelisted through the firewall. Movebot uses dynamic IP addresses and connectivity to Movebot's cloud infrastructure IP addresses cannot be whitelisted due to the dynamic nature of Movebot's cloud architecture.
A host that meets the
A host that meets the
A host that meets the
For a full list of requirements, see
To configure connectivity through a proxy server -
Resolution: This is a known Dropbox limitation. for a detailed explanation.
If you are using a proxy server - we highly recommend allowing Movebot to use a direct path to the internet. If this is not possible, then follow the to configure the Movebot agent to connect via the proxy.
For more information, get in touch with support via Tags: agent
Folders
Fully Supported
Network Drives
Fully Supported
Permissions
Source Only
Versions
Not Supported
Modification Retention
Fully Supported
Automatic Sanitization
Fully Supported
User Drives
Fully Supported
Shared Folders
Fully Supported
Team Workspace (Team Drives)
Fully Supported
Permissions
Fully Supported
Versions
Fully Supported
Modification Retention
Fully Supported
Automatic Sanitization
Fully Supported
Memory
16Gb
Hard Disk Space
32GB of free disk
Network
1000GB LAN connectivity
Internet Connectivity
Unfiltered connectivity
CPU
4+ vCPU Cores
Windows 10
Yes
Windows Server 2016
Yes
Windows Server 2019
Yes
Windows Server 2022
Yes
Windows 2008 R2
Yes - please contact support
Ports and Connectivity
HTTP and HTTPS internet access. Ports 80, 443 and 53
Uplink Speed
100MBit Internet Uplink. Recommended 1GBit
Local Network
1000Gbit Physical LAN connectivity
Outbound Firewall
No outbound filtering
Learn how to connect to a Google Workspace Gmail Account
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.
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
Login to Movebot and create a new project or task
When configuring the source or destination, choose to Create new Connection
Select Google Workspaces Gmail from the list of available connections and set the connection name
Provide an email address for an administrator account.
Provide the primary domain for your Google Workspace tenant
Click "Create Service Account"
Copy the identifier for the service account (created as part of the process above)
Login to Google Admin - admin.google.com
Search for "API Controls" in Google Admin
Click "Manage Domain Wide Delegation"
Click Add New
Provide the "client id" copied from Movebot as the client id
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
Save the new client connection in Google and return to Movebot
Click Save and Test connection in Movebot
If the connection has succeeded, you can continue
Movebot supports Google Workspace Mail migrations, including user mailboxes and calendar events. Below are common errors and frequently asked questions related to GWS Mail.
Movebot has comprehensive support for Google Workspaces and is well-maintained.
Email Messages and Folders
Fully Supported
Private Calendars
Fully Supported
Shared Calendars
Fully Supported
Contacts
Fully Supported
Tags: googleworkspaces_gmail
Connecting to Google Workspace is fast to set up and fully supported in Movebot.
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.
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
When configuring a new connection, select Google Workspace from the list of available connection types and give the connection a name
Enter your Google administrator account email address
Enter your domain (find this under "Manage domains" in Google Admin) .
Click "Create Service Account" - this will generate a Client ID
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:
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
Test the connection
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.
Movebot has comprehensive support for Google Workspaces and is well-maintained.
Shared Drives
Fully Supported
User Drives
Fully Supported
Permissions
Fully Supported
Versions
Fully Supported
Modification Retention
Fully Supported
Automatic Sanitization
Fully Supported
Tags: googledrive_domain
Learn how to run a data migration with Movebot at a high level.
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.
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.
Migrations in Movebot are not really migrations at all.
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.
A project is a collection of transfer jobs and settings.
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
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.
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.
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.
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.
Deltas update changed and added files
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.
Transferring or migrating data with Movebot generally comes down to the following process.
Pro Tip: Run a small migration/transfer first. Don't jump in the deep end too quickly
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.
Projects in Movebot are a logical unit of separation. Projects have a source and destination connection, configuration settings, and child transfers.
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
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.
Once transfers are created, they can be launched. Launching transfers stages them for execution.
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.
It's important that you investigate Critical and High Severity errors. Ignoring these will most likely result in data loss if they are not fixed.
Errors caused by intermittent issues will most likely be resolved in the next stage.
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.
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 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
There are a lot of nuances with Migrations that cannot be covered in a short document. If you are migrating from one of the major platforms, we recommend reading the and which will give you a good grounding.
Learn how to connect to an Outlook Online (Office 365) account.
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.
This connection type has the advantage that it does not send calendar notifications during a migration.
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.
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.
First, login to Azure as an administrator for your domain, and navigate to App Registrations.
Click New Registration
Specify a name for the new application. Leave the remaining fields as default, then click Register.
Make a note of the Application (Client) ID. This will be entered into your Movebot configuration.
Make a note of the Tenant ID. This will be needed in Movebot
Configure the permissions. Click API Permissions --> Add a Permission.
Select APIs my organisation uses, then search for Office 365 Exchange Online.
Select Application Permissions
And then check the permissions detailed below:
full_access_as_app
Click Grant admin consent for Couchdrop Demo and follow the consent process
Click Certificates and Secrets --> Client Secrets --> New Client Secret
Copy the Client Secret Value
The EWS API does not allow access to the user database without an additional role.
Find Discovery Management
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:
Login to Movebot and create a new project or task
When configuring the source or destination, choose to Create new Connection
Select Office 365 Outlook (via EWS) from the list of available connections and set the connection name
Provide your tenant id. This is a UUID found when configuring the application.
Provide the Application Client ID copied from the configuration step above
Provide the Application Client Secret from the steps above
Provide the admin users email address
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.
Movebot has comprehensive support for Outlook Online (Office 365) and is well-maintained.
Email Messages and Folders
Fully Supported
Public Folders
Fully Supported
In-Place Archive
Fully Supported
Private Calendars
Fully Supported
Shared Calendars
Fully Supported
Contacts
Fully Supported
Tags: office365outlook
File density (number of files per terabyte) significantly impacts performance.
Lower file counts with higher data volume generally yield faster migrations and lower API consumption.
Resource Units (RUs) are how Microsoft measures the cost of API operations. Each action your migration tool performs consumes a specific number of RUs.
The following tables provide estimated resource unit (RU) consumption when using one Movebot transfer job to copy a single folder comprising of:
1 TB data
500,000 files
50,000 folders
Each table illustrates how RU usage varies depending on the type of migration — whether migrating into SharePoint, between tenants, within the same tenant, or out of SharePoint.
Source Tenant (Scan + Transfer Files)
Destination Tenant (Create Folders + Transfer Files)
Total (source + destination): 1,700,000 (RUs)
Source App (Scan + Transfer)
Destination App (Create + Transfer)
Total (source + destination): 1,700,000 (RUs)
These are first-pass estimates. Delta passes will vary based on change volume.
API usage is measured in resource units (RUs), not raw call counts.
Review to understand how usage in this example compare to your tenant’s daily quota.
For tenant-specific daily limits, refer to the.
Consider when migrating large numbers of small files.
<50,000 files / TB
Low density – Better performance
~500,000 files / TB
Medium density - Typical performance
>1,000,000 files / TB
High density – Slower performance
Operation
Resource Units (per file or folder)
Scan Directory (Excluding Permissions and Version History)
2
Create Folder (Non-Delta)
3
File Upload
2
File Download
1
Create Folder
50,000
3
150,000
Transfer Files (Upload)
500,000
2
1,000,000
Total
—
—
1,150,000
Scan (Folders)
50,000
2
100,000
Transfer Files (Download)
500,000
1
500,000
Subtotal
—
—
650,000
Create Folder
50,000
3
150,000
Transfer Files (Upload)
500,000
2
1,000,000
Subtotal
—
—
1,150,000
Scan (Folders)
50,000
2
100,000
Transfer Files (Download)
500,000
1
500,000
Subtotal
—
—
600,000
Create Folder
50,000
3
150,000
Transfer Files (Upload)
500,000
2
1,000,000
Subtotal
—
—
1,150,000
Scan (Folders)
50,000
2
100,000
Transfer Files (Download)
500,000
1
500,000
Total
—
—
600,000
Scenario
Source RUs
Destination RUs
Total RUs
Into SharePoint (External ➝ SharePoint)
—
1,150,000
1,150,000
Tenant-to-Tenant SharePoint
600,000
1,150,000
1,750,000
Same-Tenant (Separate Apps)
600,000
1,150,000
1,750,000
Out of SharePoint (SharePoint ➝ External)
600,000
—
600,000