Move a node to another project

To keep your work organized, for example with testing and production in separate projects, you can move a node to another project of the same account. The node stays in the same region with its plan, its IP addresses, and its data, and the move does not restart it. GPU nodes move the same way.

The node takes its related resources with it: the reserved IPs and volumes attached to it, the saved images taken from it, and its CDP backups and snapshots. A committed node keeps its committed plan in the new project, and so does a committed volume attached to it.

Before you begin

To move a node, you need to be the account owner, or to have the Admin or Project Lead role in the node’s project; Move To Another Project appears for those roles. See Choose a role for a user. If the account has only one project, create a second one first; see Create a project.

The Nodes list does not offer Move To Another Project for E1 and E1WC nodes.

Get the node ready

Before you move the node, go through this list and fix whatever applies to it:

• Wait until any action in progress on the node has finished, such as creating, upgrading, powering off or on, saving an image, or reinstalling. A node that is Terminating or Failed, or one that is suspended, cannot move.
• If the node is locked, click Unlock Node in its Actions menu. See Lock a node.
• Detach the node’s VPC. See Attach a node to a VPC.
• Keep one security group on the node and detach the others. See Detach a security group from a node.
• Remove the node from the backend servers of any load balancer in the same project. See Manage backend groups and servers.
• End the node’s access to any SFS. See Configure per-node access to an SFS.
• Remove the tags from the node, from the reserved IPs and volumes attached to it, from the saved images taken from it, and from its CDP backup. See Tag a resource.
• Check that no scale group uses a saved image taken from the node. MyAccount tells you about this only after you click Transfer. To remove a scale group, see Delete a scale group.

You do not need to detach the reserved IPs or volumes, or delete the saved images and backups. They move with the node.

Move the node

1. In MyAccount, open Compute and then Nodes. Next to the node, open Actions and click Move To Another Project. The Actions menu on the node’s own page has the same item.

   If something still blocks the move, MyAccount lists the conditions the node must meet. Fix the ones that apply, using Get the node ready, and try again.

2. Move Node to Another Project opens. In Select Project, choose the project to move the node to. The list shows every project in the account, with the node’s current project listed but unavailable.

   A note confirms that the node will move to that project and will no longer be accessible in the current one. It also says that the attached reserved IPs, backups, volumes, and saved images move too.

3. Turn on the checkbox that names the node and the project you chose. Transfer becomes available.

4. Click Transfer. To close the dialog without moving anything, click Cancel instead.

The node moves as soon as you click Transfer. Nobody has to approve the move, and no email or one-time password is needed. MyAccount shows Resource is transferred successfully. The Nodes list then reloads without the node.

If MyAccount refuses the move, the node has not moved. Find the message in Troubleshooting node actions and lifecycle.

Find the node in its new project

To see and manage the node, switch to the project you moved it to: in the header, open the project list and click that project. See Create a project. The reserved IPs, volumes, and saved images that moved with the node are in that project too.

In the new project, the node has that project’s default security group for its region, and the security group it had before is removed. If the node needs other rules, attach the security group that has them. See Attach a security group to a node.

The audit logs of both projects record the move. Besides the node itself, they show each reserved IP and volume that moved with it, and the security group change. See Read the audit log.

A volume, saved image, or reserved IP can also move on its own, without a node. See Move a volume to another project, Move a saved image to another project, and Move a reserved IP to another project. For answers about billing and undoing a move, see Node FAQ.