Migration Errors

Review per-file failures and export them for cleanup.

Migration Errors

Migrations that complete with at least one file failure show an Errors section on the migration card.

Error breakdown

Errors are grouped by type:

  • throttled — Microsoft rate-limited the upload. Usually transient; retry should succeed.
  • access_denied — Agent couldn't read the source file (permissions) or Graph rejected the write. Check NTFS permissions at source, or admin consent for the destination.
  • file_locked — File was in use at upload time (open in Word, still being written to, etc.). Retry when the file is closed.
  • timeout — Upload took too long. Common for very large files on slow networks. Retry will re-upload from scratch.
  • upload_failed — Catch-all for other upload failures. See the error message for specifics.
  • quota_exceeded — Destination (SharePoint or OneDrive) is out of space.

Error list

Click any error type to open the full list of affected files in a modal.

Each row shows:

  • File path — source path
  • Error type — classification
  • Error message — the specific message from Microsoft or the agent
  • Details — additional context when available

The modal is virtualized — it handles huge error lists without slowing down.

Export

Click Export CSV on the errors section or inside the modal. Share the CSV with whoever needs to address the failures.

Retrying failures

CloudMove doesn't have a "retry failed files only" button yet. To retry:

  1. Address the root cause (fix permissions, free up quota, close locked files, etc.)
  2. Start a new migration

Files already successfully migrated will either be skipped or end up with (1) suffixes depending on the destination. The error list from the first migration stays visible alongside the new run for comparison.