Movebot has two main types of failures.
Migration failures
Migration failures occur when an entire migration process has either failed to start or has exited prematurely due to a high file failure rate.
Common Failure Types
| Failure Type | Reason | Remediation |
| invalid-credentials | The source or destination systems rejected your credentials. | Re-authenticate with the source and destination stores and rerun. |
| source-checks-failed |
Before scanning or migrating, our sanity checks on the source provider have failed. |
Check the underlying error message and remedy |
| destination-checks-failed |
Before scanning or migrating, our sanity checks on the destination provider have failed. |
Check the underlying error message and remedy |
| failure_rate_to_high |
More than 10% of files or folders have failed to migrate |
Investigate the cause of such a high failure rate, and rerun once remedied |
| no-space-left |
Not enough free space to perform the migration |
Check space limits on user or team drive and rerun |
| account-not-authorized |
Your Movebot account is blocked, chat with the team |
Individual file failures
Individual file failures are when a file cannot be transferred to the destination successfully. Movebot will retry most failures by default.
Failures can be inspected in the Movebot admin portal and we provide as much detail as possible directly to help you remedy the issue.
Common Failure Types
| Failure Type | Reason | Remediation |
|
cannot-export file-not-downloadable export-failed |
This file is a proprietary format, like gdoc and cannot be exported.
Some systems have limits on the size and format of exports. |
|
|
download-size-mismatch uploaded-size-mismatch |
The file size, once downloaded/uploaded did not match our expectations.
This means the file has been corrupted in transit or recently changed. |
Rerun the transfer |
|
download-checksum-match uploaded-checksum-match |
The checksum, once downloaded/uploaded did not match our expectations.
This means the file has been corrupted in transit or recently changed.
|
Rerun the transfer |
| parent-folder-not-found |
We could not create the folder or upload the file as the parent folder does not exist. |
|
| file-not-found | The file could not be found. Check that it exists | |
| teamdrive-not-found | The teamdrive could not be found | |
| storage-config-error | There is an issue with your storage configuration. Check that you have provided all required fields in the source and destination configuration. | |
| agent-store-timeout | The agent communication channel has timed out. | Check the Windows agent is running and connected on the server. |
| agent-not-connected | The Windows agent is no longer connected. We have not seen any activity from it in 30 minutes. | Check the Windows agent is running and connected on the server. |
|
user-not-found user-or-group-not-found |
The requested user could not be found in the source or destination system | Check that your source/destination mapping is correct and the user exists |
|
invalid-credentials-or-user user-not-activated |
The user is invalid/suspended/not activated or has not accepted the terms and conditions | Check the username/email is correct and the account is active. |
| illegal-or-disallowed-filename | The file or folder name has been rejected by the destination system | Rename the file and run a delta migration |
| path-to-large | The supplied path is to long | Restructure the data in the source to meet the destination system requirements |
| restricted-content | The content is considered by the source system as being restricted or locked | |
| access-denied | You do not have the correct permissions to access that file or folder | Review permissions |
| malware-or-spam | The file or folder has been marked as malicious and cannot be downloaded or uploaded. | |
| file-to-large | The file exceeds the size limitations on the destination | |
| token-expired | The authentication token has expired. | Re-authenticate with the source and destination stores and rerun. |
| invalid-credentials | The source or destination systems rejected your credentials. | Re-authenticate with the source and destination stores and rerun. |
| rate-limit-exceeded | Rate limiting thresholds were exceeded. | Rerun the failures |
| timeout |
During the transfer, a timeout of no activity on the file occurred. This generally indicates significant network or latency issues. |