> ## Documentation Index
> Fetch the complete documentation index at: https://docs.incredibuild.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Moving the Coordinator to a New Machine

Last updated on Nov 05, 2024

To migrate your existing Coordinator to a new machine, use the following procedure. Most of the steps below can also be performed in the user interface.

1. [Backup](/linux/backup) your Primary Coordinator's settings using the following command:

   ```
   /opt/incredibuild/management/ib_coordinator_backup.sh <path to output file>
   ```

2. [Install](/linux/installing-components) a new Primary Coordinator on the new machine. The version must be the same or higher than the original Coordinator.

3. [Obtain a new license and upload it](/linux/activate-license) to the new coordinator. The new license should have at least the same amount of cores as the original license.

4. [Restore](/linux/backup) the original coordinator data to the new Coordinator using the following command:

   ```
   /opt/incredibuild/management/ib_coordinator_restore.sh <backup .tar file>
   ```

5. For every Agent in your grid, use the [following command](/linux/cli) to move it to the new Coordinator:

   ```
   sudo /opt/incredibuild/management/set_agent_params.py coordinator <hostname/IP of new Coordinator>
   ```

   If run on a helper, it will stop any running tasks and reassign them to an available helper or the initiator. If run an Initiator, any builds started by that initiator will be aborted.

   If the new Coordinator is not the same version of Incredibuild as the Agents, the Agents will be automatically upgraded or downgraded.

6. If you have a secondary coordinator, use the following command to reassign it to the new Coordinator:

   ```
   sudo /opt/incredibuild/management/set_agent_params.py coordinator <hostname/IP of new Coordinator>
   ```