> For the complete documentation index, see [llms.txt](https://docs.movebot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.movebot.io/using-movebot/transfer-execution-and-cutover/remapping-domains.md).

# Remapping Domains

Domain changes are performed in your own environment. Remapping domains in Movebot updates transfer mappings to reflect those changes, allowing subsequent migrations to continue successfully.

This process may involve removing and adding domains in your tenant and may require updating MX records for mail migrations. 

#### When to Remap your Domains <a href="#keeping-your-data-up-to-date" id="keeping-your-data-up-to-date"></a>

Remapping will only be successful when no migrations with the old domain are in progress, so Domain changes are typically completed near the end of a migration for final cutover.&#x20;

{% hint style="warning" %}
Storage connections using admin accounts with the old domain will need to be updated using the new domain.&#x20;
{% endhint %}

#### Domain Remapping Process  <a href="#keeping-your-data-up-to-date" id="keeping-your-data-up-to-date"></a>

1. Finish or cancel any running migrations with the old domain.
2. Update domains in your tenants and Movebot storage connections.

{% hint style="info" %}
For user data migrations such as OneDrive or My Drive, check if you have the "create subfolder" transfer mapping option enabled. If so, contact <support@movebot.io> before remapping.&#x20;
{% endhint %}

3. Use the Remap Domains feature by selecting relevant transfers and starting a "run" action to replace the old domain with the new one.
   1. Calendar and/or Permission migrations will also need to update Extended Mappings using the new domain.&#x20;
4. Run a new delta migration to complete your final sync.&#x20;