---
title: Moving a Node Between Data Centers
slug: moving-node-between-data-centers
description: The six-step sequence for relocating a node machine to a new data center while keeping operator allowances and reward configurations consistent.
tags:
  - node-provider
  - maintenance
  - runbook
  - registry
  - rewards
date: 2026-05-04
related:
  - node-provider-maintenance
  - adding-additional-nodes
  - removing-node-from-registry
  - reward-configuration
---

Relocating a node between data centers touches three things at once:
allowance on two operator records, the registry record for the node
itself, and the reward configuration on both ends. The order matters
— doing the registry and allowance steps in the wrong sequence
leaves the operator record blocked from onboarding the node at its
new home.

> [!WARNING]
> Before starting, confirm that the destination data center supports
> the network's decentralization objectives. Movements that
> concentrate the network in a single jurisdiction will not be
> approved.

## Procedure

1. **Increase node allowance at the destination data center.** The
   receiving operator record needs spare allowance to accept the
   incoming machine. Submit the NNS proposal that raises its
   allowance by one. Use
   [Adding Additional Node Machines to an Existing Allowance](/wiki/adding-additional-nodes/)
   for the validation evidence and proposal pattern.
2. **Physically move the node machine.** Ship or transport the
   server to the destination data center. Apply the same physical
   security controls there as at the origin site.
3. **Remove the previous node record.** Once the machine is offline,
   follow
   [Removing a Node From the Registry](/wiki/removing-node-from-registry/)
   to clear the old node ID. This frees the allowance slot on the
   origin operator record.
4. **Re-onboard the node at the new data center.** Follow the
   standard deployment flow:
   [Gen-2 Node Deployment Guide](/wiki/node-deployment-gen-2/) or
   [Gen-1](/wiki/node-deployment-gen-1/). The node comes up with a
   fresh node ID under the destination operator record.
5. **Reduce the previous operator's reward configuration by one.**
   Submit a reward configuration change so the origin record stops
   being paid for the moved node. See the
   [Reward Configuration Guide](/wiki/reward-configuration/).
6. **Increase the new operator's reward configuration by one.**
   Submit the matching reward configuration change at the
   destination so the moved node is paid under its new home.

> [!NOTE]
> Steps 5 and 6 should land in the same minting period to avoid
> double-paying or under-paying the move. Check the next minting date
> at [next-rewards-gnj.caffeine.xyz](https://next-rewards-gnj.caffeine.xyz/)
> before submitting.

## Related

- [Node Provider Maintenance Guide](/wiki/node-provider-maintenance/) — the parent runbook.
- [Adding Additional Node Machines to an Existing Allowance](/wiki/adding-additional-nodes/) — the allowance step.
- [Removing a Node From the Registry](/wiki/removing-node-from-registry/) — the registry step.
- [Reward Configuration Guide](/wiki/reward-configuration/) — the reward steps on both ends.