Overview
Volume transfers move ownership of a volume from one project to another without copying any data. The operation is token-based: the source project creates a transfer request that generates a one-time authorization key, then the destination project accepts the transfer using the ID and key. The volume changes ownership instantly — no data movement occurs.Prerequisites
- The volume to transfer must have status Available (not attached to an instance)
- The source project user must have the
memberoradminrole - The destination project user must have the
memberoradminrole - Both users must have access to their respective project credentials
How Volume Transfers Work
Transfer a Volume
Step 1 — Create the Transfer Request (Source Project)
- Dashboard
- CLI
Navigate to Volumes
Log in to the Xloud Dashboard (
https://connect.<your-domain>) and navigate to
Project → Volumes → Volumes as the source project.Create transfer
Locate the target volume (status must be Available). Click
Actions → Create Transfer.Provide a descriptive transfer name and click Create Volume Transfer.
Step 2 — Accept the Transfer (Destination Project)
- Dashboard
- CLI
Switch to destination project
Log out and log in as a user in the destination project, or switch projects
using the project selector in the Dashboard.
Accept the transfer
Navigate to Project → Volumes → Volumes and click Accept Transfer.Enter the Transfer ID and Authorization Key provided by the source
project, then click Accept Volume Transfer.
Cancel a Pending Transfer
If the transfer has not been accepted, the source project can cancel it:- Dashboard
- CLI
Navigate to Project → Volumes → Volumes. Find the volume with a pending transfer
indicator and click Actions → Delete Transfer.
Important Limitations
| Constraint | Detail |
|---|---|
| Volume status | Must be Available — cannot transfer attached volumes |
| Snapshots | Snapshots are not transferred — they remain in the source project |
| Encryption keys | Encrypted volumes can be transferred, but the destination project must have access to the same key management service |
| Auth key expiry | Transfer requests do not expire automatically — cancel unused transfers to maintain security hygiene |
Next Steps
Create a Volume
Provision a new volume in the destination project after transfer
Volume Snapshots
Create a snapshot before transferring to preserve a copy in the source project
Attach / Detach
Attach the transferred volume to an instance in the destination project
Volume Types
Understand storage tiers and verify the transferred volume type is available