# Migrate API Signer

This page describes how to migrate your API Signer to a new host.

You might want to migrate your API Signer for a number of reasons—for example, moving from one cloud provider to another (such as Google Cloud to AWS), or moving from a local setup ([like Docker Desktop on your machine](https://docs.fordefi.com/developers/getting-started/set-up-an-api-signer/api-signer-docker)) to a cloud host where the Signer can run permanently.

The steps show you how to move your API Signer to its new home, without re-registering your API User keys.

1. Turn off your currently running API Signer.
2. Remove your API Signer from your organization:
Click **Settings** > **API Signer** > **Remove from organization**.

This action requires Admin access.
3. Refresh your browser and click **Add API Signer** to create a new instance:

4. Install the latest API Signer image in the new host by running the install commands described [here](https://docs.fordefi.com/developers/getting-started/set-up-an-api-signer/install-the-api-signer#install-the-api-signer-docker-image):

5. Select **Provision signer**, then scan the QR code with your Fordefi mobile app after interacting with the **Add API signer** notification that appears in your To Do feed.
6. Once you have provisioned the new API Signer successfully, run it as before:

7. After refreshing the browser in **Settings**, the new API Signer should show as Activated:

  - You do not need to re-register your API User public keys with the Signer. The registration is recorded on the Fordefi backend and will survive the migration.
  - Any API-initiated transaction created during the migration will remain in `Pending signature` state in the Fordefi transaction history. Signing will resume once the new API Signer is running.