Error: Invalid client secret provided
**Cause:** The client secret value is incorrect. **Resolution:** Double-check that you have copied and entered the **client secret value**, not the **client secret ID**. These are often confused but are different fields in Entra.Error: SCP or roles claim need to be present in the token.
**Cause:** Required claims are missing from the token. **Resolution:** Ensure all necessary API permissions are granted and that they are assigned as *Application* permissions, not *Delegated*. Also, confirm admin consent has been granted for these permissions.Error: Tenant "domain.com" not found
**Cause:** The specified SharePoint Tenant Domain does not exist or is misconfigured. **Resolution:** Verify that the tenant domain is correct. It should follow the format `yourcompany.onmicrosoft.com`Error: Application with identifier 'a323b4ba-031...' was not found in the directory
**Cause:** The application’s Client ID is incorrect or the app registration is missing. **Resolution:** Check that the correct Client ID is being used. Refer to **Step 7** of the [configuration steps](#configuration-steps), to confirm you have provided the proper ID.Error: The certificate used to sign the client assertion is not registered
**Cause:** The required certificate has not been uploaded to the application in Entra. **Resolution:** Generate the necessary certificate and upload it to the registered application in Entra. Refer to "**Upload the certificates from Movebot**" section of [configuration steps.](#configuration-steps)Error: Could not find site (site-not-found)
**Cause:** The SharePoint domain value is incorrect or the specified site does not exist. **Resolution:** Review your SharePoint configuration settings and ensure that you have specified the correct non-admin SharePoint domain. If the domain includes '-admin,' please remove it.aError: User Migration Failed (user-not-active)
**Cause:** The user account is not currently active or fully provisioned in Microsoft 365. **Resolution:** First ensure the user has an active license assigned.\ If the user is newly created, their OneDrive may not yet be provisioned. You can either: * Pre-provision the user’s OneDrive using PowerShell ([learn more](https://learn.microsoft.com/en-us/sharepoint/pre-provision-accounts)). * Have the user sign in to OneDrive manually at least once to trigger provisioning.Error: Call was made to the default drive, which is not supported for apponly tokens
**Cause:** The OneDrive you are connecting to in the destination hasn't been provisioned yet. **Resolution:** You will need to pre-provision your OneDrive accounts so they are active before the migration by logging into them. You can do this in bulk following Microsofts current recommendations - [here](https://learn.microsoft.com/en-us/sharepoint/pre-provision-accounts)Can Movebot migrate data between two Microsoft 365 tenants?
**Answer:** Yes. Movebot supports bidirectional migrations between Microsoft 365 tenants, including full tenant-to-tenant migrations.Can we restrict the app registration to only have access to specific users or sites?
**Answer:** No. Currently, the app registration will have access to all users and sites within the tenant. More granular access control is not supported at this time.Why does SharePoint show more storage used than Movebot?
**Answer:** SharePoint includes all previous versions of files in its reported storage usage. By default, Movebot only counts the most recent version of each file, which can result in lower reported storage.Can Movebot migrate data from a Classic SharePoint Site to a Modern Site?
**Answer:** Yes. Movebot treats both Classic and Modern SharePoint sites the same. Data can be migrated seamlessly between them.Error: invalid_request: Invalid impersonation
**Cause:** The admin email address specified in your Google connection is invalid or does not have sufficient permissions. **Resolution:** Ensure the email address exists, is correctly entered, and belongs to a licensed Google Workspace admin user with appropriate privileges.Error: Bad Request. "<email address>" is not a member of this shared drive. Only members can access items in this shared drive.
**Cause:** Destination tenants sharing settings do not allow non-members to be assigned permissions on a Shared Drive. **Resolution:** To resolve this, you can either: 1. Add the user as a member of the Shared Drive before rerunning the migration,\ or 2. Adjust the Shared Drive’s settings to allow sharing with users who are not drive members. These changes can be made in the Google Workspace Admin Console under the Shared Drive's access and sharing configuration.Error: teamdrive-not-found: Could not find team drive
**Cause:** Movebot was unable to locate a Shared Drive with the specified name. **Resolution:** This error may be caused by one or more of the following: * **Hidden whitespace:** Check for extra spaces at the beginning or end of the Shared Drive name in Google Drive. * **Special characters:** `/teamdriveid:Error: parent-folder-not-found
**Cause:** Google Drive creates folders asynchronously, which means there can be a short delay before new folders are fully available. If Movebot tries to upload a file to a folder that hasn’t been fully created yet, it triggers a **parent-folder-not-found** error. **Resolution:** Run a **Delta Migration** to retry the failed uploads. By the time you run the Delta Migration, the necessary folders usually exist—allowing the uploads to complete successfully.Error: user-teamdrive-access-denied
**Cause:** Occurs when the source or destination Shared Drive lacks the required permissions or settings. **Resolution:** You must have **Manager** permissions on both the source and destination Shared Drives. For Google to Google migrations, Google Docs require the following Shared Drive Settings. Ensure these are enabled on the source/destination drives, then re-run the migration or Delta Migration to complete the transfer. * *Allow people who aren’t Shared Drive members to access files.* * *Allow people outside of `Is it possible to migrate between two existing Google tenants using Movebot?
**Answer:** Yes. Movebot fully supports bi-directional migrations between Google tenants, including full tenant-to-tenant transfers.Why does the Movebot scan result show more/less data than the Google Admin Console?
**Answer:** The discrepancy occurs because Google and Movebot calculate storage usage differently. * **Google Admin Console** reports storage based on **file ownership**. It includes all files a user owns, even if they are located in folders shared with them by others. * **Movebot** only scans and reports on content located **within a user’s actual MyDrive**. It does **not** include files the user owns inside folders shared with them by other users. *** #### When Google Admin shows **more** data than Movebot **Scenario:**\ Jeff shares a folder with Sarah. Sarah adds 50GB of photos to Jeff’s shared folder. * **Google Admin Console:** Reports 50GB of storage used by **Sarah**, because she is the file owner. * **Movebot:** Scans **Sarah’s MyDrive** and detects **0KB**, since the data physically resides in **Jeff’s** folder. *** #### When Movebot shows **more** data than Google Admin **Scenario:**\ Mathias creates a Shared Folder and shares it with five colleagues. They add 20GB of data to it, but Mathias doesn’t add anything himself. * **Google Admin Console:** Reports **0KB** usage for **Mathias**, because he doesn’t own any files. * **Movebot:** Scans **Mathias’s drive** and detects **20GB**, since he is the owner of the Shared Folder—meaning all content within it is considered his for the purpose of migration. ***What happens to Google Docs, Sheets, and Slides during migration?
**Answer:** When migrating between two Google tenants, the native Google file formats (Docs, Sheets, Slides, etc.) are retained, and everything will function the same in the destination tenant as it did in the source. If you're migrating **out of the Google ecosystem** (e.g., to Microsoft 365), Google files will be automatically converted to their equivalent Microsoft Office formats (e.g., Docs → Word, Sheets → Excel). **Note:** Due to limitations in the Google API, documents larger than **11MB** cannot be exported into Microsoft Office formats. These files will either be skipped or need to be downloaded manually. [Learn more](/platform-guides/google/performance-and-limits#google-docs-export-limit).Why can't I see a particular Shared Drive in the list of available drives in Movebot?
**Answer:** Ensure that the admin user specified in the Movebot-Google connection has Manager permissions on the Shared Drive. If the Shared Drive was recently created, it can take up to 30 minutes for Google's APIs to reflect the new drive. Wait and check back later.| Feature | Supported in Movebot |
|---|---|
| Shared Drives | Fully Supported |
| User Drives | Fully Supported |
| Permissions | Fully Supported |
| Versions | Fully Supported |
| Modification Retention | Fully Supported |
| Automatic Sanitization | Fully Supported |
| Feature | Supported in Movebot |
|---|---|
| Folders | Fully Supported |
| Network Drives | Fully Supported |
| Permissions | Source Only |
| Versions | Not Supported |
| Modification Retention | Fully Supported |
| Automatic Sanitization | Fully Supported |
Error: ECONNRESET
**Cause:** Your outbound firewall is filtering the internet connection **Resolution:** Configure your firewall to allow all outbound traffic on port 443 and 53 from the virtual machine or server running the Movebot agent.Error: Agent Disconnected
**Cause:** The movebot agent is not longer connected to Movebot **Resolution:** Check that the virtual machine running the agent is still online and the agent is running. Restart the agent and/or virtual machine if required.Does Movebot support network drives
**Answer:** Yes. Movebot supports migrating to and from network drives. To migrate data from network drives make sure they are mounted/connected to the virtual machine or physical server you have installed the Movebot agent on.Does Movebot support proxy servers
**Answer:** Yes. Movebot supports migrating data on networks with a proxy server managing network connectivity. To configure connectivity through a proxy server - [Proxy Configuration](/platform-guides/windows-fileservers/proxy-configuration)Does Movebot have Static IPs to whitelist
**Answer:** No. Movebot utilises dynamic IP addresses during a migration. We cannot provide you with static ip addresses or domain names to whitelist.What ports does Movebot use for migrations
**Answer:** 443 and 53. Movebot connects to the Movebot cloud via HTTPs.Can I run Movebot on a desktop or laptop workstation
**Answer:** Not recommended We do not recommend running the Movebot agent on a laptop or desktop. While possible, doing so can result in unpredictable performance and interruptions.How much memory and cpu resources does the agent require
**Answer:** 16GB of ram and 4vCPUs minimum We do not recommend running a migration on servers with less than above.Error: Failed to scan Team Folder (access-denied)
**Cause:** The admin user specified in your Dropbox connection does not have sufficient access to the Team Folder. **Resolution:** Even if the folder appears visible in the Dropbox Admin Console, the admin must be explicitly granted editor permissions on the folder itself. Visibility alone is not enough for Movebot to scan or migrate the contents.Error: "Requested user could not be found."
**Cause:** The admin email address used in your Dropbox connection is invalid or misspelled. **Resolution:** Double-check the spelling of the email address and confirm that the user exists within the Dropbox tenant.Error: Too many items for single namespace
**Cause:** This folder account contains more items than recommended for a single namespace. **Resolution:** This is a known Dropbox limitation. [See here](/platform-guides/dropbox/namespaces-and-limitations) for a detailed explanation.Movebot scan shows substantially more data than what I see in my Dropbox account
**Answer:** This typically occurs when the **"Exclude Shared Content"** option is **disabled** in your Dropbox connection settings. When this setting is turned off, Movebot includes **shared folders** in the scan results **for every user the folder is shared with**. This means the contents of that folder are counted once for each user, significantly inflating the total scanned data. > **Important:**\ > A **shared folder** is different from a **Team Folder**. > > * **Shared folders** are owned by a specific user and live within that user's personal Dropbox space. > * **Team Folders** are owned and managed at the organizational level and are **not affected** by the **"Exclude Shared Content"** setting. **Example:**\ A shared folder named **"Shared Media"** is 1.5TB and shared with 20 users.\ With **"Exclude Shared Content"** disabled, Movebot counts that same folder **20 times**—once for each user—resulting in **30TB** appearing in the scan results. To avoid this, enable the **"Exclude Shared Content"** setting so shared folders are only counted once, keeping scan results accurate and avoiding data duplicationHow can I migrate a folder that has been shared with me by another user?
**Answer:** By default, Movebot ignores folders shared with a user to avoid duplicating data when migrating an entire tenant. If the folder was shared with you by another user in your Dropbox tenant, you can locate and migrate the folder by browsing to the owner’s account in the Folder-to-Folder mapping modal. If the folder was shared by a user outside your organization, please contact Movebot support for assistance in mapping and safely migrating the data.| Feature | Supported in Movebot |
|---|---|
| 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 |
| Feature | Supported in Movebot |
|---|---|
| User Drives | Fully Supported |
| Shared Folders | Fully Supported |
| Permissions | Fully Supported |
| Versions | Fully Supported |
| Modification Retention | Fully Supported |
| Automatic Sanitization | Fully Supported |
Error: Access Denied when trying to scan/migrate certain users
**Cause:** The account used to connect Movebot to Box does not have sufficient administrative privileges. Only the primary Box Admin user can access all user data, including content owned by other Co-Admins. If you connect using a Co-Admin account, you may encounter access denied errors when trying to access the Admin or other Co-Admin accounts. **Resolution:** Reconnect using the Box Admin account to ensure full access to all user content.The number of files shown in Movebot scan results doesn't match what I see in Box
**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 [official documentation](https://support.box.com/hc/en-us/articles/360043695334-Storage-Usage-Or-File-Count-In-My-Account-Is-Incorrect).How can I migrate a folder that has been shared with me by another user?
**Answer:** By default, Movebot ignores folders that have been shared with a user to avoid duplicating data when performing a full tenant migration. If the folder was shared by another user within your Box tenant, you can locate it by browsing into that user’s account using the Folder-to-Folder mapping modal. If the folder was shared by someone outside your organization, please contact Movebot support for help mapping and migrating the data safely.Movebot scan shows substantially more data than what I see in my Box account
**Answer:** This typically occurs when the **"Exclude Shared Content"** option is **disabled** in your Box connection settings. When this setting is turned off, Movebot includes **shared folders** in the scan results **for every user the folder is shared with**. This means the contents of that folder are counted once for each user, significantly inflating the total scanned data. **Example:**\ A shared folder named **"Shared Media"** is 1.5TB and shared with 20 users.\ With **"Exclude Shared Content"** disabled, Movebot counts that same folder **20 times**—once for each user—resulting in **30TB** appearing in the scan results. To avoid this, enable the **"Exclude Shared Content"** setting so shared folders are only counted once, keeping scan results accurate and avoiding data duplication| Feature | Supported in Movebot |
|---|---|
| User Drives | Fully Supported |
| Permissions | Fully Supported |
| Versions | Fully Supported |
| Modification Retention | Fully Supported |
| Automatic Sanitization | Fully Supported |
Error: Unable to scan specific folders (file-not-found)
**Cause:** This usually occurs when attempting to scan permissions using an account that is not the ShareFile Account Owner. **Resolution:** * Reconnect Movebot to ShareFile using the Account Owner credentials, **or** * Disable permission migration if permissions are not required for your use case. **Important:** \ You must use the Account Owner. "Super Admin" users do not always have sufficient access to scan permissions on folders inside "allshared" space.| Feature | Supported in Movebot |
|---|---|
| User Drives | Fully Supported |
| Permissions | Fully Supported |
| Versions | Not Supported |
| Modification Retention | Not Supported |
| Automatic Sanitization | Fully Supported |
Error: Calendar Event Failure (attendees-mapping-required-error)
**Cause:** Event attendee mapping is missing for calendar migration. **Resolution:** You must configure mapping rules for event attendees in Step 4 of your project settings. Without this, calendar events will not be migrated.Error: Authentication Failed (invalid-credentials)
**Cause:** The required scopes for Google Domain Delegation are missing or misconfigured. **Resolution:** Review your domain delegation setup and ensure all necessary scopes are assigned correctly.Review the documentation.How do I handle the cutover?
Movebot simplifies cutover using **delta migrations**. You can migrate while users are active, then run a final delta to capture any changes after they stop using the source—**minimizing downtime**. If your domain changes during cutover, use **"Remap Domains for Cutover"** from the **Run Action** menu. This allows you to specify the old and new domains for source/destination mailboxes, ensuring mappings remain accurate. After remapping, you can continue running **delta migrations post-cutover**.Is it possible to migrate between two existing Google Workspace tenants using Movebot?
**Answer:** Yes. Movebot supports bi-directional, tenant-to-tenant migrations between Google Workspace environments.How do I transfer one specific folder within a mailbox?
**Answer:** Use the CSV Import feature to migrate the specific folder. \ \ Example: source,destination\ /mailbox:How does Movebot handle messages tagged with multiple labels when migrating into Microsoft?
**Answer:** Movebot creates a separate folder in Microsoft for each label from Google. If a message has multiple labels, a separate copy will appear in each corresponding folder.How can I migrate a mailbox larger than 100GB into Microsoft using the Online Archive feature?
**Answer:** 1. Add a content exclusion rule in Step 6 of your project settings to ignore mail received within the last year. 2. Run a full migration. 3. Allow Microsoft’s automatic archiving to move older content into the Online Archive. 4. Adjust your exclusion rule to ignore mail older than one year.How can I migrate only mail that was received before a specific date?
**Answer:** Yes, from the launch menu, you can select a desired timeframe to include email up to the specified date.Once I've migrated historical mail, can I migrate only mail received after a certain date?
**Answer:** Yes. Select "**Start Delta Migration**" from the launch menu and choose the desired timeframe for the delta to include only newer mail.Migrated calendar events are missing Google Meet links. Why?
**Answer:** This is expected behaviour. Google Meet links are tenant-specific and cannot be transferred between environments. Events will be migrated without their original meeting links.Does Movebot support merging multiple mail accounts into a single mailbox?
**Answer:** Yes. You can use a CSV import to map multiple source mailboxes into a single destination mailbox, organizing each into its own sub-folder. Make sure to check "Migrate folder contents" when importing the CSV. Example:\ \ source,destination\ /mailbox:[Learn more.](/using-movebot/transfer-mapping/import-csv-mappings#id-01h8055v9asmr1cykjcc57791m-1)
| Feature | Supported in Movebot |
|---|---|
| Email Messages and Folders | Fully Supported |
| Private Calendars | Fully Supported |
| Shared Calendars | Fully Supported |
| Resource Calendars | Fully Supported |
| Contacts | Fully Supported |
The legacy EWS API will not send invitations. {% endhint %} ### Requirements To connect Movebot to Outlook/0365, you will need: * To have Global Admin access to Azure * To be familiar with the configuring applications in Azure ### Configuration Steps There are two steps to this process. The first is creating the application in Azure with the correct permissions. Next is configuring the connection in Movebot. #### Creating the application in Azure 1. First, login to Azure as an administrator for your domain, and navigate to **App Registrations.** 2. Click **New Registration** 3. Specify a name for the new application. Leave the remaining fields as default, then click **Register.** 4. Make a note of the **Application (Client) ID.** This will be entered into your Movebot configuration. 5. Configure the permissions. Click **API Permissions --> Add a Permission.** 6. Select **Microsoft Graph,** then **Application Permissions.** 7. Select the permissions detailed below: ``` Directory.Read.All Mail.ReadWrite User.ReadWrite.All Contacts.ReadWrite Calendars.ReadWrite MailboxSettings.Read ``` 8. Click **Grant admin consent for Couchdrop Demo** and follow the consent process 9. Click **Certificates and Secrets** --> **Client Secrets** --> **New Client Secret** 10. Copy the **Client Secret Value** #### Configure the connection in Movebot 1. Login to Movebot and create a new project or task 2. When configuring the source or destination, choose to **Create new Connection** 3. Select **Office 365 Outlook** from the list of available connections and set the connection name 4. Provide your tenant name. This is normally in the format "companyname.onmicrosoft.com". 5. Provide the Application Client ID copied from the configuration step above 6. Provide the Application Client Secret from the steps above ### Supported Features Movebot has comprehensive support for Outlook Online (Office 365) and is well-maintained.
| Feature | Supported in Movebot |
|---|---|
| Email Messages and Folders | Fully Supported |
| Public Folders | Not Supported |
| In-Place Archive | Not Supported |
| Private Calendars | Limited Support |
| Shared Calendars | Limited Support |
| Contacts | Fully Supported |
Error: The impersonation principal name is invalid
**Cause:** The email address of the admin user is incorrect. **Resolution:** Double-check the admin user's email address in your configuration settings to ensure it's valid and matches the expected domain.Error: The caller has not assigned any of the RBAC roles
**Cause:** The specified admin user has not been granted the Discovery Management role. **Resolution:** If you're unable to assign the Discovery Management role, use a [CSV import ](/using-movebot/transfer-mapping/import-csv-mappings) to map your transfers. This Discovery Management role is only required for listing available mailboxes/automatic transfer mappings. It will not prevent migration.Error: Unknown failure in response. Code: 403
**Cause:** Missing or incorrect API scopes. **Resolution:** Review steps 5-9 of the [configuration steps](#configuration-steps) to confirm that the required API scopes have been correctly configured and admin consent has been granted.\ \ **Resolution:** Once confident the above steps are completed, if you still experience a 403 error, please check your Tenant and Users EWS status is enabled. [This is Microsoft's Documentation](https://learn.microsoft.com/en-us/exchange/client-developer/exchange-web-services/how-to-control-access-to-ews-in-exchange) on how to enable.Error: Invalid client secret provided
**Cause:** The client secret is incorrect. **Resolution:** Make sure you have entered the Client Secret Value, not the Client Secret ID. This is a common mistake during app registration setup.Error: Mailbox shows 0KB scanned
**Cause:** Mail migration settings may be disabled or duplicate job exists. **Resolution:** First, ensure that mail/contact/calendar migration is enabled under options in your project settings. Then check for duplicate transfers of the same source mailbox and remove one.Error: Calendar Event Failure (attendees-mapping-required-error)
**Cause:** Event attendee mapping is missing for calendar migration. **Resolution:** You must configure mapping rules for event attendees under "Attendee mappings" of your project settings. These tell Movebot how to convert calendar attendees during a migration, and without this, calendar events will not be migrated. Examples <_chris@domain.com> --> chris\@domain.com\_\ *\*@domain.com --> \*@domain.com*How do I handle cutover?
Delta migrations only migrate new and updated data and are designed to be used for cutover. Deltas can be run while users are still active to pull across updates or changes without requiring downtime.What if the domain changes during cutover?
If the domain changes during cutover, use **Remap Domains for Cutover** from the Run Action menu. This allows you to replace the old domain with the new one for any new transfers. After remapping the domain, you can continue running delta migrations post-cutover. See [Remapping Domains ](https://docs.movebot.io/using-movebot/transfer-execution-and-cutover/remapping-domains)for more details.Is it possible to migrate between two existing Microsoft 365 tenants using Movebot?
**Answer:** Yes. Movebot supports bi-directional migrations between Microsoft 365 tenants, including full tenant-to-tenant migrations.Can I connect to GoDaddy M365 tenants using Movebot?
Yes. Movebot supports migrations too/from GoDaddy M365 tenants using the same mechanism as regular M365 tenants.My mail migration appears stuck after transferring 50–100GB of data
This is likely due to mailbox size limits in Microsoft 365. By default: * Standard Outlook Online licenses support up to 50GB of mailbox storage. * Users with extended licenses may have up to 100GB, but will still encounter similar limits. Once the mailbox reaches this threshold, migration will appear to stall until auto-archiving policies move older emails to the Online Archive. ### Workarounds **Option 1:** \ Pause the migration, allow the auto-archiving to complete, then resume the migration. {% hint style="danger" %} If you take this approach, you will not be able to run a Delta Migration afterward. Doing so will cause archived emails to be re-migrated. {% endhint %} **Option 2 (Recommended):** \ Delete the destination mailbox entirely and start the migration of affected users from scratch using the steps [outlined here](#how-can-i-migrate-a-mailbox-over-100gb-into-microsoft-using-the-online-archive-feature). This ensures a clean and accurate migration.How do I transfer one specific folder within a mailbox?
**Answer:** Use the CSV Import feature to map the specific folder.\ Example:\ \ source,destination\ /mailbox:How does Movebot handle emails from Google that are tagged with multiple labels?
**Answer:** Movebot creates a separate folder in for each label. If a message has multiple labels, a separate copy is placed in each corresponding folder.How can I migrate a mailbox over 100GB into Microsoft using the Online Archive feature?
**Answer:** 1. Add a content exclusion rule in Step 6 of your project settings to ignore mail received within the last year. 2. Run a full migration. 3. Allow Microsoft’s automatic archiving to move older content into the Online Archive. 4. Adjust your exclusion rule to ignore mail older than one year. 5. Run a delta migration to capture the latest mail.How can I use Movebot to restore a folder from an Online Archive?
**Answer:** Use the CSV import feature to map the specific folder from the Online Archive to a destination in the primary mailbox.\ Example: source,destination\ /mailbox:How can I migrate only mail that was received before a specific date?
**Answer:** Yes, from the launch menu, you can select a desired timeframe to include email up to the specified date.Once I've migrated historical mail, can I migrate only mail received after a certain date?
**Answer:** Yes. Select "**Start Delta Migration**" from the launch menu and choose the desired timeframe for the delta to include only newer mail.| Feature | Supported in Movebot |
|---|---|
| Email Messages and Folders | Fully Supported |
| Public Folders | Source Only |
| In-Place Archive | Fully Supported |
| Private Calendars | Fully Supported |
| Shared Calendars | Fully Supported |
| Contacts | Fully Supported |
Error: Authentication Issue - UPN Logins Not Allowed
**Cause:** UPN-based logins are not permitted in the current server configuration. **Resolution:** Enable UPN-based logins on your Exchange server to allow authentication using theError: Authentication Issue - Basic Authentication Not Allowed
**Cause:** Basic authentication is disabled on the Exchange server. **Resolution:** Enable basic authentication for EWS access. This is required for Movebot to successfully authenticate and perform migrations from Exchange On-Prem.Error: The account does not have permission to impersonate the requested user
**Cause:** The service account you specified on your Exchange connection doesn’t have **ApplicationImpersonation** rights for the mailbox. **Resolution:** Use steps below to check current permissions and grant org-wide or scoped access.\ \ **1. Check current permissions** ```powershell Get-ManagementRoleAssignment -Role ApplicationImpersonation -GetEffectiveUsers ``` 2. **Grant org-wide impersonation** ```powershell New-ManagementRoleAssignment -Name "impersonation_svc" -Role ApplicationImpersonation -User user@domain.com ``` 3. **(Optional) Grant scoped impersonation** ```powershell New-ManagementScope -Name "ImpersonationScope" -RecipientRestrictionFilter {Department -eq "Migration"} New-ManagementRoleAssignment -Name "impersonation_svc_scoped" -Role ApplicationImpersonation -User user@domain.com -CustomRecipientWriteScope "ImpersonationScope" ```Error: Hostname Issue
**Cause:** The default hostname or URL used to connect to EWS is not resolving correctly or is incomplete. **Resolution:** If the default URL format exch01.domain.com doesn't work, try using the full EWS path instead: `exch01.domain.com/ews/exchange.amsx`How do I handle the cutover?
Movebot simplifies cutover using **delta migrations**. You can migrate while users are active, then run a final delta to capture any changes after they stop using the source—**minimizing downtime**. If your domain changes during cutover, use **"Remap Domains for Cutover"** from the **Run Action** menu. This allows you to specify the old and new domains for source/destination mailboxes, ensuring mappings remain accurate. After remapping, you can continue running **delta migrations post-cutover**.How do I transfer one specific folder within a mailbox?
**Answer:** You can use the CSV Import feature to map the specific folder.\ Example:\ \ source,destination\ /mailbox:How can I migrate only mail that was received before a specific date?
**Answer:** Yes, from the launch menu, you can select a desired timeframe to include email up to the specified date.Once I've migrated the historical mail, can I run a migration for only mail received after a certain date?
**Answer:** Yes. Use the **Start Delta Migration** option from the launch menu, then specify how far back you'd like the delta to cover.Does Movebot support merging multiple mailboxes into a single mailbox?
**Answer:** Yes. It is possible to use a CSV import to map multiple source mailboxes into a single destination mailbox. You can assign each source to a custom sub-folder.\ \ Be sure to enable "**Migrate folder contents**" when importing the CSV. Example: source,destination\ /mailbox:| Feature | Supported in Movebot |
| Email Messages and Folders | Fully Supported |
| Calendars | Fully Supported |
| Contacts | Fully Supported |
| Public Folders | Source Only |
### Supported Features Movebot has comprehensive support for IMAP servers and is well-maintained. | Feature | Supported in Movebot | | -------------------------- | -------------------- | | Email Messages and Folders | Fully Supported | \ Tags: imap # pCloud Learn how to connect to a pCloud account ### Introduction Connecting to pCloud is fast to set up and supported as a source connection in Movebot. {% hint style="info" %} pCloud is only supported as a source. Setting it as a destination will throw an error. {% endhint %} ### Requirements To connect to pCloud in Movebot you will need: * Username and password for the pCloud account or be able to connect via OAuth ### Configuration Steps 1. When configuring a new connection, select **pCloud** from the list of available connection types and give the connection a name. 2. Connect to pCloud by clicking 'Link to pCloud' button, and log in to pCloud in the popup that comes up 3. After a successful login, click Save and Test Connection in Movebot ### Transferring Multiple Users In pCloud, it is only possible to connect a single user per connection, and impersonation via an admin user is not supported within pCloud. In order to transfer multiple users, a separate pCloud Storage Connection and project will need to be created for each user. ### Supported Features Movebot has comprehensive support for pCloud and is well-maintained.
| 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 |
| Automatic Sanitization | Fully Supported |
| Modtime Retention | Not Supported |
| Feature | Supported in Movebot |
| Files and Folders | Fully Supported |
| Modification Retention | Fully Supported |
| Automatic Sanitization | 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 |
| Feature | Supported in Movebot |
| Files and Folders | Fully Supported |
| Modification Retention | Fully Supported |
| Feature | Supported in Movebot |
|---|---|
| SharePoint Document Libraries | Fully Supported |
| OneDrive Users | Fully Supported |
| Permissions | Fully Supported |
| Versions | Fully Supported |
| Modification Retention | Fully Supported |
| Automatic Sanitization | Fully Supported |
Error: Authentication Failed (invalid-credentials)
**Cause:** Permission scopes were not added correctly **Resolution:** Review your marketplace application setup in Google Cloud Admin and ensure all necessary scopes are assigned correctly. Review all steps above. Sometimes waiting 24 hours can help as well.Rate limiting
Using a custom marketplace application and project means that you are benefiting from Movebot's high quota limits with Google. If you are hitting high numbers of rate limiting, you may need to increase the project quotas for the Google Drive API or Gmail API. Most of the time, this will require approval from Google.| Feature | Supported in Movebot |
|---|---|
| Email Messages and Folders | Fully Supported |
| Private Calendars | Fully Supported |
| Shared Calendars | Fully Supported |
| Resource Calendars | Fully Supported |
| Contacts | Fully Supported |
2. **Configure the Connection in Movebot** The following information is must be entered into the Movebot EWS connector. * **Tenant ID** * **Email Address** (does not need to be an administrator account.) * **Application Client ID** * **Application Client Secret**
3. **Connect to Exchange Online using PowerShell** ``` Connect-ExchangeOnline ``` 4. **Create a Mail-Enabled Security Group** * Create a group that defines which mailboxes Movebot can access. ``` New-DistributionGroup -Name "EWS-App-Allowed-Mailboxes" -Type Security ``` * Add allowed mailboxes: ``` Add-DistributionGroupMember -Identity "EWS-App-Allowed-Mailboxes" -Member user@domain.com ``` * **Only mailboxes added to this group will be accessible.**
5. **Retrieve the Distinguished Name of Security Group** ``` Get-DistributionGroup "EWS-App-Allowed-Mailboxes" | Select DistinguishedName ``` * Copy the entire DistinguishedName value. * Example: ``` CN=EWS-App-Allowed-Mailboxes,OU=contoso.onmicrosoft.com,OU=Microsoft Exchange Hosted Organizations,DC=AUSP913A004,DC=PROD,DC=OUTLOOK,DC=COM ``` 6. **Create the Management Scope** ``` New-ManagementScope -Name "User Mailboxes" ` -RecipientRestrictionFilter "MemberOfGroup -eq 'FULL-DN-HERE'" ``` * **Replace `FULL-DN-HERE` with your group’s Distinguished Name.**
7. **Register the Service Principal** * You will need: * **Application ID (from App Registration)** * **Object ID (from Enterprise Application)** ``` New-ServicePrincipal ` -AppId
## Important Notes #### Connection Test Behaviour When using restricted RBAC scoping, the Movebot connection test will fail by design. This is expected behaviour and does not indicate a misconfiguration. Because the application does not have organization-wide access, automatic mailbox discovery and validation are not supported. #### Permission Propagation Delay Permission updates and RBAC scope changes may not take effect immediately. In some environments, it can take up to an hour before access behaviour reflects the new configuration. If testing fails immediately after setup, wait and retry before troubleshooting further. #### Mailbox Mapping Requirement When using restricted access: * Mailboxes must be mapped manually using [CSV Transfer Mapping](/using-movebot/transfer-mapping/import-csv-mappings). * Only mailboxes included in the mail-enabled security group can be migrated. * Mailboxes outside of the group will return HTTP 403 errors during migration. ## Common Errors
Error: 403 Forbidden
**Cause:** Mailbox is not a member of the mail-enabled security group used in the management scope. **Fix:** Add the mailbox to the group and retry the migration.2. **Configure API Permissions**\ \ **Graph API** * **API Permissions → Add a Permission** * Select: **Microsoft Graph → Application Permissions** * Enable permission: ``` Sites.Selected ``` * Click **Grant admin consent**. **SharePoint API** * **API Permissions → Add a Permission** * Select: **SharePoint API→ Application Permissions** * Enable permission: ``` Sites.Selected ``` * Click **Grant admin consent**.
3. **Create a Client Secret** * Navigate to: **Certificates & secrets → Client secrets → New client secret** * Create the secret and copy the **Client Secret Value**. * This will be required in Movebot.
4. **Configure the Connection in Movebot** * The following information must be entered into the Movebot SharePoint connector: * **SharePoint Domain** * **Tenant ID** * **Application Client ID** * **Application Client Secret**
5. **Upload the certificate 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
6. **Grant Site-Level Access Using Microsoft Graph** * The `Sites.Selected` permission alone does not grant access. Site-level permissions must be assigned explicitly. * Retrieve the Site ID. Open the following URL in your browser and replace the placeholders: ``` https://
7. **Sign in to Graph Explorer** * Navigate to:
8. **Assign Application Access to the Site** * Run the following request in Graph Explorer:\ `POST` `https://graph.microsoft.com/v1.0/sites/{site_id}/permissions` * Replace `{site_id}` with the Site ID retrieved earlier. * Request Body: ```json { "roles": ["write"], "grantedToIdentities": [ { "application": { "id": "
| Data Migrations | Movebot is the fastest and easiest data migration tool on the market. Learn how to move data with Movebot. | /pages/W5Jftk1XffuUoO4DgVxS | |
| Mail Migrations | Movebot now supports email, calendars and contact migrations as well as Data migrations. Learn about them here. | /pages/X3LbYPfYzl5uk3gACkS7 |
Email Support Send us an email and we will get back to you. | support@movebot.io | mailto:support@movebot.io |
| Join our discord | Get live assistance from our team and community on discord | https://discord.gg/dZzqr3EVez |
| Chat to Moby | Get AI assistance from Moby Chat on our Website. He does not have access to your account. The team fact checks his answers and updates his documentation regularly. |
In the following platforms: * [Google Workspaces Gmail](/connections/google-workspaces-gmail) * [Exchange Server](/connections/exchange-server) * [Outlook Online (Office 365)](/connections/outlook-online-office-365) * [IMAP Server](/connections/imap-server) ## Key Concepts in Movebot for Mailboxes When configuring a mailbox migration in Movebot, there are a couple of key concepts that we have adopted to help make the process simple. It's useful to quickly skim through them to understand how we approach mailbox transfers differently. ### Mailboxes are Built on Movebot Using Movebot to perform email, calendar, and contact migrations uses the same process as with [Data Migrations with Movebot](/features/data-migrations-with-movebot). ### Migrate Mail the Same Way as Files and Folders Movebot extracts email, calendars, and contacts so that they behave like files and folders. This approach is a bit unusual, but has some key benefits. One benefit is that mailbox migrations support delta migrations natively, another is that mailboxes can be transferred to normal file storage, allowing you to back up mail with Movebot. A major advantage to our approach is that Mailboxes can be cherry-picked. Because Movebot works with your mailbox as if it's a filesystem, you can pick and choose what content you move and use Movebot to reorganize and ignore certain folders inside mailboxes. This means you can include/exclude based on a filter or move mail between labels, users, and inboxes. ### Delta Migrations {% hint style="success" %} Deltas move new emails automatically, without a hard cutover {% endhint %} The delta functionality in Movebot is an overlooked gem. Most migration tools require a hard cutover, but with Movebot, the cutover process can be managed by the admin in a way that best suits them. In Movebot, delta migrations iteratively migrate changes that have occurred since the first transfer using the modification time and other metadata by looking at a scan of both the source and the destination. During a delta migration, Movebot will only transfer emails that have either been updated or newly created in the source. Deltas can be ran as many times as needed, including months after the project was initially set up. ## Quick Start Guide Because transferring or migrating mailbox data uses the same process as files, simply follow the existing guide for [Data Migrations with Movebot](/features/data-migrations-with-movebot). ## Frequently Asked Questions
How do I manage the cutover?
Movebot simplifies cutover using **delta migrations**. You can migrate while users are active, then run a final delta to capture any changes after they stop using the source—**minimizing downtime**. If your domain changes during cutover, use **"Remap Domains for Cutover"** from the **Run Action** menu. This allows you to specify the old and new domains for source/destination mailboxes, ensuring mappings remain accurate. After remapping, you can continue running **delta migrations post-cutover**.Do I need separate migration projects for mail and data?
Yes. **Mail, calendar, and contact migrations** require a separate project from data migrations because they involve different access scopes and permissions.Should I separate my mail migration from my calendar migration?
Mail and calendars can typically be migrated together in a single project. However, for **larger or more complex migrations**, separating them into **individual projects** may help improve performance. If you're unsure which approach is best for your migration, please **contact support** for guidance.What will happen to my meeting rooms, shared mailboxes, etc?
Resources such as **meeting rooms** and **shared mailboxes** are treated as **standard mailboxes** during the migration process.| 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. | /pages/zSMIXcnkhmz6nNCs35b5 | |
| Transfer Mapping | Learn about adding transfer mappings to your project. Choosing which data is going to be moved to where. | /pages/0niY2XO2d5ccr8WPFKty | |
| Permissions and Metadata | Learn about configuring permissions and metadata in Movebot. Movebot has comprehensive support for permissions and metadata. | /pages/e5wG3P8PQzET7NsiSyHS | |
| Transfer and Cutover | Learn about executing your migration project and cutting over users to the new platform. | /pages/uIdBaGppwGe6Nx4xk0kB |
# Searching Scan Results 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. | {files.filename == "file1.txt"} | Match files with the filename "file1.txt" | | ------------------------------- | ----------------------------------------------------------------- | | {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 | You can join queries together with an "and" operator: ``` {files.modtime > 1602629811} and {files.size > 1024} ``` Spaces and character cases are important and currently there is limited error handling. # Adding Transfers from Scan 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. ### Adding Transfers from Explorer After running a scan, check the **Discovery Scan** tab and choose **Explorer** to review the files and folders that Movebot has scanned. You'll also see an overview of errors and warnings, such as if you are attempting to map a drive in the source that is too large for the destination. If you click on one of these errors or warnings, the results will only show results that have that specific issue. To add a Transfer from the scan results, simply highlight beside a folder, click the checkbox, and click **Add Transfers**. You can also pick to **Ignore File**, which can be useful for isolating objects that you do *not* want to move to the destination. If a folder or its subfolders are used in a transfer, Movebot will inform you with an icon beside the file name.
| Source | Destination |
|---|---|
| user:michael@couchdrop.io | user:michael@couch.io |
| teamdrive:/Shared | teamdrive:/Archive/Shared |
| mailbox:michael@couchdrop.io | teamdrive:/Archive/Mail |
| Add User Mappings | Learn how to map user to user transfers in Movebot | /pages/qIcPWNvuwagokcsNnZyT | |
| Add Team Drive Mappings | Learn how to map team drives in Movebot | /pages/sDH0dj2bJnTTFREvYh7x | |
| Import CSV Mappings | Learn how to use the CSV import process to bulk import users and folders to Movebot | /pages/EVR2Hl8WDFwGOvBa9lRr |
# Add Team/Shared Drives 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. {% hint style="info" %} Movebot treats everything as a folder, which means the destination is interchangeable. You can map folders into Shared Drives/Team Drives, Folders within Team Drives, etc. {% endhint %} Team Drives show up in the root along with users. ### **Adding a Team Drive mapping** Click **Add Transfer** from the project overview and navigate through the source and destination selecting the folders on the source and the destination.
# Add Network Mappings 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
| /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 |
# Import CSV Mappings The easiest way to add mappings to a project at scale is via a CSV file. CSV mappings are added to a project as individual transfers/move jobs and you can then treat them like any other mappings. ### Uploading a CSV file Within your project, click **+** **Add** **Transfer**. Select **Import Transfers from CSV**. ### CSV Formatting When executing a file migration, the CSV uses a simple `source, destination` format. ``` source,destination /user:michael@couchdrop.io,/user:donald@newdomain.io /sharepointsite:/sites/Accounting:/Documents,/teamdrive:Accounting ``` CSV prefixes can target special objects like users, drives, on-premises agents, or mailboxes.
| Prefix Format | Example | Supported Store Types |
|---|---|---|
| /user:<username or email> | /user:michael@couchdrop.io | Boomsync, Box, Dropbox Business, Egnyte, Google Workspace, OneDrive, pCloud, Sharefile, Sharepoint, Legacy Sharepoint, Amazon Workdocs |
| /teamdrive:<team drive name> | /teamdrive:My Team Drive | Boomsync, Dropbox Business, Egnyte, Google Workspace, Huddle, Sharefile |
| /teamdriveid:<team drive ID> | /teamdriveid:0AI2ezk6QbPvvUk9PVA | Google Workspace |
| /<drive letter>:/<path> | /D:/ | Windows/OSX Agent |
| /<uncpath>/<path> | /REMOTESERVER/Shared Data | Windows/OSX Agent |
| /mailbox:<email_address> | /mailbox:chris@couchdrop.io | Exchange, Office 365 Outlook, Google Workspace Gmail, IMAP |
| /sharepointsite:<site path>:[<document library path>] | /sharepointsite:/sites/Site1: (all libraries) /sharepointsite:/sites/Site1:/Documents (single library) | Sharepoint, OnPrem Sharepoint |
| /hub:<hub_name> | /hub:HubName | BIM360 |
| /project:<project_name> | /project:ProjectName | BIM360 |
| /bucket:<bucket_name> | /bucket:BucketName | Amazon S3, S3 Compatible, BiFrost Cloud, Digital Ocean, Filebase, IDrive Cloud, Lyve Cloud, Wasabi |
| /publicfolders:<path> | /publicfolders:All Public Folders | Exchange, Office 365 Outlook via EWS |
| No prefix | /Files | Backblaze B2, SFTP, Dropbox Personal, Google Cloud, Google Drive Personal, Azure Blob, Azure Files |
| Setting | Behaviour |
|---|---|
| Migrate folder contents (Don't retain root folder) | Enabled: Only the contents of each specified source folder are migrated - the folder itself is not created in the destination.
|
| Ignore checks on import | Skip validation of CSV source/destination paths (e.g. prefix formatting). Contact support before enabling. |
The format for these columns are shown below. **Example (IMAP source):** ``` source,source_secret,destination /mailbox:michael@couchdropdemo.com,michael@couchdropdemo.com:P@ssw0rd1,/mailbox:michael@newdomain /mailbox:chris@couchdropdemo.com,chris@couchdropdemo.com:P@ssw0rd2,/mailbox:chris@newdomain.com ``` For help with CSV mappings, get in touch with support via
# Excluding Content Learn about options for excluding content from transfers The default behavior of Movebot is to migrate all compatible files and folders from the source to the destination. This behavior can be overridden by using content exclusion rules. Content exclusion rules can be defined on the project or individual transfer levels. *** ### **Project Level Exclusion Rules** Project-level exclusion rules will apply to all migrations in a project. Administrators can define these in the project settings under **Rules.** Select "Ignored Files" to choose relevant folders/files you want to exclude. When selecting a folder, all subfolders will also be excluded from transfers. *** ### **Individual Migration/Transfer Level Rules** Exclusion rules are also available at the Transfer level. Rules defined at this level are **in addition** to rules set at the project level. At the project level, there is also the option for explicit inclusion. Defining rules here will exclude all content **except** content that matches the rule set. {% hint style="success" %} Explicit inclusion rules are also useful for carving up your project into chunks by file types or size. {% endhint %} #### Ignore subfolders mapped in other transfers When this transfer-level **default option** remains checked, Movebot will ignore subfolders that are mapped within the same project. The intent is to stop the same folder from being transferred multiple times to avoid creating duplicate content at the destination. If you intentionally want to transfer a folder to multiple locations, you will need to uncheck this option. **Available Rule Types** | File Extension Matches | Only match files with the following extensions | | ------------------------------- | ------------------------------------------------------------------------------------------------------- | | 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. Requires a unix style wildcard to start eg *\*/D:/Documents* |
# Permissions and Metadata # Mapping Permissions Learn about how to map permissions in Movebot Permission Mappings define how user/group permissions should be rewritten and ensure that destination permissions are correctly applied in scenarios where the username/domain is changing. \ \ Once permissions migration has been enabled, you will see the option to configure Permission Mappings as an additional step in your project settings. *Example Mappings* | Scenario | Source Mapping | Destination Mapping | | ------------------------------------------ | ----------------------- | -------------------------- | | All usernames mapped to email addresses | `*` | `*@couchdropdemo.com` | | Domain-only change (username unchanged) | `*@couchdrop.io` | `*@couchdropdemo.com` | | Username changes and becomes email address | `john.doe` | `jdoe@couchdropdemo.com` | | Username and domain both change | `john.doe@couchdrop.io` | `jdoe@couchdropdemo.com` | | Group name mapped to group email | `Group 1` | `group1@couchdropdemo.com` | ### **Importing mappings from a CSV file** For situations where the username format is changing, you can add explicit mappings for each user. When migrating a large organization, you can create a CSV file of mappings that can be imported. *An example CSV file is:* ``` source,destination michael@couchdrop.io,michael.lawson@couchdropdemo.com chris@couchdrop.io,chris.roy@couchdropdemo.com ``` ### ### Other Options *Tweak the permission migration further* | **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. |# Scanning permissions 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**. ### **Downloadable reports** 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 |
# Manual Permissions 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. ### CSV File Format If you are not using the Box collaborators report, the format of the permissions CSV file is as shown in the example below. ``` filename,collaborator permission,collaborator login /Case Studies,Editor,jack@couchdrop.io /FolderX/Case Studies,Editor,jack@couchdrop.io ``` ### Box Collaborators Report From your Box admin console, go to **Reports > Create Report** and click **Select Filters** on the row for the collaboration report.
# Transfer Execution and Cutover # Deltas and Changes Learn about how Movebot handles Deltas and changed files. ### Keeping Your Data Up to Date In active environments, it’s common for files to be added or updated during a migration. Movebot’s **Delta Migration** feature helps keep your destination up to date by copying **only the files that have been added or modified** since the last transfer. *** ### How Delta Migrations Work Delta Migrations compare the **source and destination** using each file’s **modification time (modtime)**.\ Only files that are **new** or have a **more recent modtime** on the source will be transferred. This reduces duplication and speeds up the process by skipping files that haven't changed. {% hint style="warning" %} Important: **Movebot does not delete or move files at the destination** If you rename files or move them to a new directory in the source, Movebot will see them as "new" files. This means that they won't be moved in the destination, and instead will be migrated again. If you delete files at the source, a delta migration **will not** delete them in the destination. To avoid duplication or confusion, we recommend **avoiding major restructuring** during the migration process. {% endhint %} *** ### Running a Delta Migration Delta Migrations increase **scan time**, but reduce **transfer time** by focusing only on what’s changed. You can only launch a Delta Migration **after your Full Migration** run. To do this: 1. Open your project. 2. Select the transfer(s) you want to run a Delta for. 3. Click **Run Action**. 4. Choose **Start Delta Migration**.
We recommend running a Delta Migration for your Cutover to catch files that were created or updated since your Full Migration. You can also run a Delta Migration to resolve certain errors. See further information on this at [Failures and Errors](/using-movebot/transfer-execution-and-cutover/failures-and-errors). ### Running a delta migration as your initial transfer If you already have content in your destination tenant because of user access or a partially-completed migration, you may want to start with a Delta Migration instead of a Full Migration. In this scenario, you can enable the "**Include only Changed Files/Objects**" setting. This setting forces Delta Migrations and uses the delta migration process outlined above for all transfers. \ \ To force Delta Migrations across all runs: 1. Go to **Step 4** in your project settings. 2. Enable the **“Include only Changed Files/Objects”** option. # Failures and Errors Learn about how Movebot handles Failures and Errors. ### Handling Failures with Confidence While Movebot is designed to be reliable, occasional failures can happen—especially when dealing with varying cloud platforms and environments. The good news? Most issues are easy to fix, and failures are **nothing to be afraid of**. We’re here to help you handle them with ease. *** ### First Step: Resume Job / Rerun Failures If you have a finished transfer with outstanding failures, your first action should be to **Resume Job / Rerun Failures**. This simply resets the status of any failed files and tries again. This action does not require a re-scan of the source data. To rerun failures: 1. Open your project and select any jobs that have failures. 2. Click **Launch Scan or Transfer**. 3. Select **Resume Job / Rerun Failures**. This often clears up transient or permission-based issues with minimal effort. *** ### Secondary Option: Start a Delta Migration If some failures persist—particularly with error types such as **unknown errors**, **file-not-found**, or **checksum-mismatch**—running a **Delta Migration** can be helpful. Delta migrations scan for and retry transferring files that have changed, or failed previously, without reprocessing files that have already migrated successfully. To start a delta migration: 1. Open the project and select any jobs that have failures. 2. Click **Launch Scan or Transfer**. 3. Select **Start Delta Migration**. This is a safe and efficient way to retry specific problem files without restarting the entire job. ### Investigating Persistent Failures Movebot displays detailed failure information in the **admin interface**, including the original error message returned from the cloud platform. This can help pinpoint the reason a file failed to transfer. ### Still Need Help? If the reason for failure remains unclear, we’re happy to assist. 📩 **Contact support at**
# Pausing/Resuming Learn about pausing and resuming transfer jobs. ### Pausing and Resuming Transfer Jobs Transfer jobs in Movebot can be safely **paused and resumed at any time**, giving you full control over the migration process. *** #### How to Pause and Resume a Job * To **pause** a job that is currently running, click **Cancel/Pause Migration** in the job menu. * To **resume**, open the same job and click **Resume Job / Rerun Failures**. When resumed, Movebot will **pick up where it left off**. You can pause and resume migrations as often as needed without affecting already transferred data. *** #### ⚠️ Keep in Mind If you click **Start Full Migration, Start Delta Migration,** or **Start Data Only Migration** instead of \ **Resume Last Action / Rerun Failures**, the job will **start from scratch**, requiring a re-scan of all previously scanned data. Always use **Resume Last Action / Rerun Failures** to avoid unnecessary duplication and preserve your job's progress.
# Scheduling 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. ### Scheduling Daily Execution Migration jobs can be scheduled to launch daily at a certain time. This feature is useful for syncing where the source dataset is still active and you want to perform a daily sync. Scheduling daily executions requires setting a daily start time and we recommend enabling **Always Use Delta** so Movebot is not migrating the same files every day without changes. ### Scheduled Data Transfer Window Movebot supports the ability to specify a time window when Movebot can move data in the transferring stage. Scheduling a data transfer window is done by specifying a start and end hour in UTC time. Unlike when Scheduling Daily Executions, scheduling a data transfer window does not start the migration automatically; you must still start the migration. Once the migration reaches the transferring stage, Movebot will check to make sure we are inside the scheduled data transfer window. If outside the defined window, we pause the transfer. {% hint style="warning" %} **Note:** When outside the transfer window, the migration will remain in the Transferring state, but no data will be migrated {% endhint %} .
# Data Localization 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 the project settings of any project under **Settings --> Finalise** in the section **Choose Movebot Region**. ### Available regions | Region | Node ID | | --------------------------- | --------------------------------------------------------------- | | San Francisco (Recommended) | Digital Ocean SFO3 | | 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 | | Bangalore | Digital Ocean BLR1 | | Tokyo | AWS ap-northeast-1 | | Sydney | Digital Ocean SYD1 | | HIPPA Compliant | Chat with the Movebot team for more information on this option. | | Dedicated/Self Hosted | Chat with the Movebot team for more information on this option. | # Remapping Domains Learn about how Movebot handles updating domains during your migration. Domain changes are performed in your own environment. Remapping domains in Movebot updates transfer mappings to reflect those changes, allowing subsequent migrations to continue successfully. This process may involve removing and adding domains in your tenant and may require updating MX records for mail migrations. #### When to Remap your Domains Remapping will only be successful when no migrations with the old domain are in progress, so Domain changes are typically completed near the end of a migration for final cutover. {% hint style="warning" %} Storage connections using admin accounts with the old domain will need to be updated using the new domain. {% endhint %} #### Domain Remapping Process 1. Finish or cancel any running migrations with the old domain. 2. Update domains in your tenants and Movebot storage connections. {% hint style="info" %} For user data migrations such as OneDrive or My Drive, check if you have the "create subfolder" transfer mapping option enabled. If so, contact
| Google Workspace | Learn how to connect Movebot to Google Workspace | /pages/i4nnSvepod3G15NdJrZV | |
| Personal Google Drive | Learn how to connect Movebot to a personal Google Drive | /pages/Hc1Jh8XyxpVsgOKVFDPh | |
| Google Mail | Learn how to connect to Gmail to migrate mail, calendars and contacts | /pages/XtmmdU6InfM3FvTUFZRa |
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.
|# Sharing and Ownership 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. ### Team drives vs Shared folders There are some subtle differences between Team Drives and Shared folders. | | Team Drives | Shared Folders | | -------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | | Who owns the content | The organisation | The individual user who created each file or folder. | | Can permissions be removed | No |
Permissions can be customised at any level.
The sharing user, can be removed from subfolders created by external users.
| | File limitations | 400,000 files per drive | None | | Content can be orphaned | No | Yes | The most important thing to remember here is around ownership. In a **Team Drive**, the **organization** owns the content, not individual users. In a **Shared Folder**, the **individual** that creates the content owns it. This means,# Delegating Domain Wide Authority Connect Google Workspace to Movebot with a Client ID and domain-wide delegation ## Introduction To connect a Google Workspace account to Movebot, you need to delegate domain wide authority so Movebot can access your users and migrate them automatically. ## Requirements Delegating Domain-Wide Authority requires the following: * A Google Workspace Administrator Account to access the Admin Console * Familiarity with the Google Admin Console * Client ID for Google generated in Movebot when configuring a Google Workspace connection ## Configuration Steps 1. [Login to the admin console ](https://admin.google.com/)for your Google Workspace domain. 2. Select the **Security** tab. If you don't see **Security**, select **Show More** from the bottom of the menu list. 3. Choose **Access and data control** and then **API controls**. 4. In the **Domain wide delegation** section, choose **MANAGE DOMAIN WIDE DELEGATION**. 5. In the **API clients** section, click **Add new**. Paste the Client ID generated from Movebot into the **Client ID** field. 6. In the **OAuth scopes (comma-delimited)** field, paste the following: ``` https://www.googleapis.com/auth/drive,https://www.googleapis.com/auth/drive.file, https://www.googleapis.com/auth/admin.directory.user, https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.user.security ``` 7. Click **Authorize**. Test that the connection in Movebot is successful to complete your configuration. For more information on domain-wide delegation, see this Support article from Google:
# Custom Column Metadata {% hint style="warning" %} This feature is currently in **beta** and may change. Use with **caution in production** and test thoroughly in staging environments. {% endhint %} ### Overview When migrating between SharePoint Online (SPO) sites—whether across tenants or within the same tenant—preserving metadata like custom columns can be critical. Movebot now allows you to retain these metadata values during your migration, improving post-migration usability and data continuity. *** ### What It Does This allows you to transfer: * **Custom columns** from SharePoint Document Libraries * **Metadata values** associated with files *** ### How to Enable 1. Open the "Options" tab from within your Project Settings 2. Check the box to enable **"Include SharePoint Column Metadata"** *** ### Limitations * **Not supported in Ludicrous Mode** * **Slower performance** due to additional API requirements * **Beta feature**– edge cases may not be fully supported *** ### Recommendations * **Test first** in a non-production environment * **Review sample files** post-migration to verify metadata * Only use in scenarios where metadata accuracy is more important than speed *** ### Summary The **"Include SharePoint Column Metadata"** option helps retain custom metadata during SPO migrations, enhancing the fidelity of your data. While in beta, it’s a valuable tool for more accurate and context-rich SharePoint transfers. # SharePoint Ludicrous Mode ### **What Is Ludicrous Mode?** **Ludicrous Mode** is a high-performance migration mode that leverages SharePoint’s **Migration API.** \ This is a lesser-known, batch-based ingestion API designed to reduce the number of calls via the standard Microsoft Graph API. It offers **significantly improved throughput**, especially for migrations containing larges number of small files. ### **Key Benefits** Ludicrous Mode is ideal for: * Projects involving **high file counts and small files** * Reducing the likelihood of significant throttling during large-scale transfers ### **Filename Sanitization Differences** Ludicrous Mode requires **stricter character sanitization** than the Graph API. Specifically: * **Ampersands (`&`)** and **single quotes (`'`)** will be **removed** from file and folder names * This behaviour is different from standard Graph-based migrations, which may preserve these characters 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. {% hint style="success" %} Enable Ludicrous Mode **before starting a migration** and keep it enabled for the **entire duration** of the job. {% endhint %} ### **How to Enable Ludicrous Mode** {% hint style="danger" %} 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. {% endhint %} Ludicrous Mode can be enabled at the **project level** in Movebot. Before enabling: 1. Open your project settings. 2. Select **4. Options** 3. Enable "**Include only changed objects/files**" 4. Open **Advanced Options** 5. Enable "**SharePoint Ludicrous Mode**" If you have any questions, please contact
# Running the Movebot Agent as a Service 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. Before starting, make sure that you have installed the Couchdrop Cloud Connector by [following the steps outlined here](https://docs.movebot.io/connections/windows-file-server)[. ](https://community.movebot.io/hc/en-us/articles/360002289775)Make sure you have run and configured everything properly and check that it is working. Click on the settings icon (⚙️) in the top right of the agent window, then click "**Install as a service**" If you encounter an error, try running the agent as an administrator before installing the service.
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# Others {% content-ref url="/pages/b2ZTR54Cir4aqmxoxBeZ" %} [Exchange Web Services (EWS)](/platform-guides/others/exchange-web-services-ews) {% endcontent-ref %} # Exchange Web Services (EWS) Here are the articles in this section {% content-ref url="/pages/SVseeRD0Jy0Wo106HLZy" %} [How to disable EWS throttling](/platform-guides/others/exchange-web-services-ews/how-to-disable-ews-throttling) {% endcontent-ref %} # How to disable EWS throttling 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. ### Requirements 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 ### Steps to Disable EWS throttling 1. Login to Microsoft 365 with an Admin account 2. Open the Admin panel from the list of apps 3. 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. 4. A search bar will appear. Type in **Increase EWS Throttling Policy**. 5. An option will appear to Run Diagnostics. Click **Run Tests** and choose a duration that will cover the migration period. 6. You will receive a message that an update to the throttling policy has been started. This may take 15 minutes to take effect. ### Verifying that EWS throttling has been successfully disabled 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. ### Disabling EWS throttling via support ticket An alternative method to disable EWS throttling is to create a Support ticket and ask the Microsoft Team to make the change for you. # Performance and Speed 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. ### Rate-limiting 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
# Errors and Failures 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). ### Viewing Errors Errors can be found on an individual transfer mapping basis under **Error Tracker.**