# Resource Transfer


Resource Transfer action allows users to transfer their services from one project to another within the same CRN.

:::info Note
    This action is only available to **Owners** and Contact Persons with the roles of **Admin** or **Project Lead**.
:::

## Node


Using this action you can transfer your node from node's current project to another project within the same CRN. On transferring this node, all attached **Reserved IPs, Backups, Volumes**, and **Saved Images** associated with this node will also be transferred to the selected project.

:::info Note
    After the transfer, the security group attached to the node in the current project will be removed, and the node will be assigned the default security group of the target project.
:::

## To Transfer the Node

- Ensure the node is not in **Creating**, **Terminating**, or **Failed** state. Also, the node should not be **Locked**.
- The node should not be attached to a **Load Balancer** or to a **Scalable File System**.
- **Auto-scaling** configured using the **node's saved image** also prohibits transfer.
- The node must not have any **Tags**, **VPC**, or **more than one security group** assigned.
- No services with attached tags should be linked to the node.

To transfer a node, click on **Move To Another Project** from Actions.

![Transfer Node Actions](images/transfer_node_actions.png)

Now, select the **target project**, check the checkbox, and click **Transfer**.

![Node Move To Another Project](images/node_moveToAnotherProject.png)


:::info Note
    An audit log will be generated for the node and any associated resources in both the current and target projects during the transfer.
:::

## Images


Using this action you can transfer your image from image's current project to another project within the same CRN.

:::info Note
        To transfer the image -

        1. Ensure the image is not in **Deleting** or **Error** state.
        2. Ensure no **Auto-scaling** is configured using the **image**.
        3. The image must not have any **Tags** attached.
:::

## To Transfer the Node

- Ensure the node is not in **Creating**, **Terminating**, or **Failed** state. Also, the node should not be **Locked**.
- The node should not be attached to a **Load Balancer** or to a **Scalable File System**.
- **Auto-scaling** configured using the **node's saved image** also prohibits transfer.
- The node must not have any **Tags**, **VPC**, or **more than one security group** assigned.
- No services with attached tags should be linked to the node.

To transfer a node, click on **Move To Another Project** from Actions.

![Transfer Node Actions](images/image_project_transfer1.png)

Now, select the **target project**, check the checkbox, and click **Transfer**.


![Node Move To Another Project](images/image_project_transfer2.png)

==pp

## Volume


Using this action you can transfer your volume from volume's current project to another project within the same CRN. On transferring this volume, **Snapshots** of volume will also be transferred.

:::info Note
        To transfer the volume -

        1. Ensure the volume is not in **Attached**, **Creating**, **Deleting** or **Error** state.
        2. The volume must not have any **Tags** attached.
:::

To transfer the volume click on **Move To Another Project** button in actions.

![Transfer volume](images/Volume_project_transfer1.png)
   

Then click on **Move To Another Project** from Actions, select the **target project**, check the checkbox, and click **Transfer**.


![Move to Another Project](images/Volume_project_transfer2.png)

:::info Note
    An audit log will be created for the transfer in both the current and target projects during the transfer.
:::

## Reserve IP

Using this action you can transfer your reserve ip from its current project to another project within the same CRN.

:::info Note
        To transfer the reserve ip -

        1. Ensure the reserve ip is not in **Attached** or **Unavailable** state.
        2. The reserve ip must not have any **Tags** attached.
:::

To transfer the reserve ip click on **Move To Another Project** button in actions.


![Reserve IP](images/reserveIP_project_transfer1.png)


Then click on **Move To Another Project** from Actions, select the **target project**, check the checkbox, and click **Transfer**.


![Project Transfer 2](images/reserveIP_project_transfer2.png)


:::info Note
    An audit log will be created for the transfer in both the current and target projects during the transfer.
:::


## Dbaas

Using this action you can transfer your dbaas from its current project to another project within the same CRN.

:::info Note
        To transfer the dbaas -
        
        1. Ensure the Dbaas is in **Running or Stopped** only.
        2. The Dbaas must not have any **Tags**, **VPC** or **Parameter Group** attached.
        3. Transfer is not permitted for **Kafka** databases.
:::

To transfer the Dbaas click on **Move To Another Project** button in actions.


![Dbaas Move another Project](images/dbaas_move_to_another_project.png)     

Then click on **Move To Another Project** from Actions, select the **target project**, check the checkbox, and click **Transfer**.


![Dbaas Transfer](images/dbaas_transfer.png)           

:::info Note
    An audit log will be created for the transfer in both the current and target projects during the transfer.
:::

## Parameter Group


Using this action you can transfer your Parameter Group from its current project to another project within the same CRN.

:::info Note
        To transfer the Parameter Group -

        1. The Parameter Group must not have any **Tags** attached.
        2. The Parameter Group must not be attached to a **Dbaas**.
:::

To transfer the Parameter Group click on **Move To Another Project** button in actions.


       
![PG Move another Project](images/pg_move_to_another_project.png)         

Then click on **Move To Another Project** from Actions, select the **target project**, check the checkbox, and click **Transfer**.


![PG Transfer](images/pg_transfer.png)    
      



---