Your First Migration

This is the fastest path from a fresh CloudMove account to a completed migration. We'll skip most of the nuance — later docs cover the details. Here we just want something working.

You'll need:

• A CloudMove account (sign up if you haven't)
• The agent installed on a machine with access to a source folder (install guide)
• Microsoft 365 Global Admin access for one of your clients
• A small test folder to migrate (start tiny — a few MB, 10–20 files)

1. Create a client

From the dashboard, open Clients and click New Client.

Give it a name (e.g. "Acme Corp") and save.

2. Connect Microsoft 365

On the client's detail page, click Connect Microsoft 365.

You'll be redirected to Microsoft to grant admin consent. Sign in with a Global Admin account and accept the permissions. When you land back in CloudMove, the client shows a green Connected badge.

3. Create a project

Still on the client page, click New Project. Name it (e.g. "HR Files Test") and save.

The project opens in the Setup step.

4. Connect an agent

In the project's Setup step, click Connect Agent. CloudMove generates an 8-character activation token.

Open the CloudMove agent on your test machine, paste the token, and click Activate. Within a few seconds, the dashboard updates to show the agent as connected.

5. Add source folders

In the agent, click Add Folder and browse to your test folder. It appears in the agent's source list — and within a heartbeat, in the dashboard too.

6. Pick a destination

In the dashboard, the project advances to the Destination step. Click Select Destination and choose SharePoint (or OneDrive, if you want).

Pick a site, a library, and optionally a folder. Save.

7. Run a scan

Project now shows the Scan step. Click Start Scan.

The scan runs on the agent. For a small test folder it finishes in seconds. You'll see a summary with total files, total size, and any issues found.

If there are blocking issues, the migration step won't activate — fix or exclude the problem files first (see Understanding Scan Results).

8. Run the migration

Project now shows Migrate. Click Start Migration.

The dashboard shows live progress: packages completing, files uploaded, bytes transferred, current file name. For a small test folder you'll be done in under a minute.

When it's done, status flips to Completed. Open SharePoint (or OneDrive) and verify the files are where you expect.

You shipped

That's the full loop. From here:

• Explore Projects for multi-destination mappings and folder exclusions
• Dig into Scans to understand what pre-migration analysis catches
• Read Migrations for error handling, resume, and large-scale runs