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

Was this helpful?

Export as PDF
  1. Using Movebot
  2. Transfer Execution and Cutover

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 support@movebot.io Our team can review the issue and guide you to a solution.


Last updated 2 months ago

Was this helpful?