Agent Overview

The CloudMove agent is a small desktop app that runs inside your client's network. It's the only component that touches your client's files.

What it does

• Reads source files from local paths or mapped drives
• Reports folder structure so you can map folders to destinations in the dashboard
• Scans files for issues before migration
• Uploads files directly to Microsoft (SharePoint via Migration API, OneDrive via Graph)

The agent does not:

• Send files to CloudMove's servers
• Store credentials or tokens beyond the current session
• Modify source files (read-only operation)

How it talks to the dashboard

The agent polls /api/agent/heartbeat every 30 seconds. Each heartbeat:

• Tells the dashboard the agent is alive
• Pulls the latest project configuration (source folders, destinations, start/stop signals)
• Returns cancellation signals if you hit cancel in the UI

Progress updates from scans and migrations go to /api/agent/migration-progress as they happen.

Where to install it

Any Windows 10/11 or macOS 12+ machine that can:

• Read the source file share
• Reach cloudmove.app on port 443
• Stay powered on for the duration of the migration

A dedicated server works best for long migrations. A technician workstation works fine for small jobs.

One agent per project

Each agent activation is tied to one project via an activation token. If you want to migrate folders for multiple clients from the same machine, generate separate tokens and switch between them (or install multiple agents — though that's overkill).

Next steps

• Activating an Agent — token flow
• Agent Lifecycle — heartbeats, reconnect, revoke