Skip to main content

Creating a migration

Updated

Availability: Migrate isn't offered for purchase or activation at launch. It's coming later. This page explains how Migrate works so you can plan client moves ahead of time. There's no Migrate pricing yet. To hear when it's available, submit a request.

Setting up a migration in Migrate involves three layers: a client record, a project that belongs to that client, and one or more jobs under the project. Each job represents a single workload — a file share, a mailbox migration, an archival run, and so on. You also need credentials stored in the vault before you can attach them to a job.

Step 1: Register the Client

  1. Open Migrate and go to Clients > New.
  2. Enter the client name and any relevant details.
  3. Save. The client record becomes the parent for all projects and jobs associated with that customer.

Step 2: Create a Project

  1. Go to Projects > New.
  2. Name the project and link it to the client you just created.
  3. Save. A project groups all related jobs — for example, everything involved in migrating a single customer tenant.

Step 3: Add Credentials to the Vault

Before creating a job, make sure the credentials for your source and destination systems are in the vault.

  1. Go to Credentials > New.
  2. Select the provider (OneDrive, SharePoint, Exchange Online, Google Workspace, etc.) and enter the required credentials.
  3. Save. Migrate encrypts the credential blob with AES-256-GCM and stores it. The raw credentials are never stored in plain text.

Step 4: Create a Job

  1. Under your project, go to Jobs > New.
  2. Set a job name and select the job type: migrate_files, migrate_mailbox, archive, or sync. Two further types are catalogued — discovery_scan and validation — but nothing runs them today (see the correction note at the top of this page).
  3. Select the source connector (for example, exchange_on_prem) and the destination connector (for example, exchange_online).
  4. Attach credentials from the vault for both source and destination.
  5. Configure optional settings: concurrency, chunk size, bandwidth limit, integrity verification, whether to delete files from source after upload, and whether to preserve folder structure.
  6. Save. Invalid source-destination-job-type combinations are rejected immediately with an error.

Step 5: Generate an Agent Key

The agent on the customer machine needs a key to authenticate.

  1. Go to Agent Keys > Generate.
  2. Copy the key.
  3. Paste it into the Migrate module on the customer machine — the endpoint side of Migrate is a module of The One Agent, installed once per device and enabled per device, not a separate Migrate installer. The agent registers and starts sending heartbeats. It will appear under Agents as Online.

FAQ

Do I need a separate project for each client? Yes. Clients and projects keep jobs organized by customer. One client can have multiple projects (for example, one per migration engagement).

What if my source-destination combination is rejected? Migrate only allows combinations that make sense — for example, you cannot migrate files into a mailbox destination. Check the connector catalog to confirm which combinations are supported.

How do I move credentials between jobs? Credentials live in the vault and can be referenced by multiple jobs. You do not need to re-enter them. When a job starts, the agent fetches the credentials it needs directly from the vault (rate-limited to 10 fetches per hour per agent).

Related