Running a Migration

Migrations only start when there's a completed scan and everything else is in place.

Prerequisites

The Start Migration button is only enabled when:

• A scan has completed successfully
• At least one source folder has files that aren't blocked
• A destination is configured
• An active agent is connected
• The client has an active subscription

If any check fails, the button is disabled with a tooltip explaining why.

Start

In the project Migrate step, click Start Migration.

The agent picks up the signal within 30 seconds and begins. The dashboard shows live progress from then on.

What happens

Behind the scenes:

1. The agent enumerates files again (to catch anything added since the scan)
2. Files are grouped by destination (in multi-destination mode)
3. Each destination's files are batched into packages (800 files or 200 MB per package, whichever comes first)
4. Packages process 3 at a time; within each package, 8–16 uploads run concurrently
5. Upload progress streams to the dashboard in real time

You don't need to understand packages to use CloudMove — it's just how the agent parallelizes work efficiently.

During the migration

The dashboard shows:

• A global progress bar (percent complete)
• Files uploaded / total files
• Bytes transferred / total bytes
• Current file being uploaded
• Package-level breakdown (see Migration Progress)

Heartbeats continue throughout — if the agent disconnects mid-migration, the dashboard flags it and the migration pauses until the agent reconnects.

When it finishes

Completed migrations land in one of three states:

• Completed — all files uploaded successfully
• Completed with errors — some files failed; successful ones are still in SharePoint/OneDrive
• Failed — migration couldn't proceed at all (rare — usually an auth or configuration issue)

See Migration Errors for reviewing failed files.