Volume Transfers Between Projects

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 member or admin role
The destination project user must have the member or admin role
Both users must have access to their respective project credentials

How Volume Transfers Work

The authorization key is displayed only once at the time of transfer creation. Store it securely before closing the dialog or terminal session. If the key is lost, cancel the transfer and create a new one.

Transfer a Volume

Step 1 — Create the Transfer Request (Source Project)

Dashboard
CLI

Navigate to Volumes

Navigate to Storage > Volumes as the source project.

Create transfer

Locate the target volume (status must be Available). Click the More dropdown and select Create Transfer.Provide a descriptive transfer name and click Confirm.

Record the credentials

A dialog displays the Transfer ID and Authorization Key. Copy both values immediately and share them securely with the recipient project (e.g., via an encrypted message or password manager).

The authorization key is shown only once. It cannot be retrieved after closing this dialog. If lost, delete this transfer and create a new one.

Authenticate as source project

Source your credentials file to authenticate with the Polystack platform:

Load credentials

source openrc.sh

Your administrator provides the RC (credentials) file for your project. See CLI Setup for configuration details.

Create transfer request

Create transfer (source project)

openstack volume transfer request create \
  --name transfer-to-project-b \
  <volume-name-or-id>

The output includes auth_key — copy this value immediately. It is shown only once.

List pending transfers

openstack volume transfer request list

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 Storage > Volumes and click Accept Transfer.Enter the Transfer ID and Authorization Key provided by the source project, then click Confirm.

Verify

The volume now appears in the destination project’s Volumes list with status Available.

Volume ownership transferred — the volume is now in the destination project.

Authenticate as destination project

Source credentials for the destination project:

Load destination project credentials

source project-b-openrc.sh

Accept the transfer

Accept transfer (destination project)

openstack volume transfer request accept \
  --auth-key <auth-key> \
  <transfer-id>

Volume ownership transferred. It now appears in the destination project.

Verify

Confirm volume is in new project

openstack volume list

The transferred volume appears in the destination project’s volume list.

Cancel a Pending Transfer

If the transfer has not been accepted, the source project can cancel it:

Dashboard
CLI

Navigate to Storage > Volumes. Find the volume with a pending transfer indicator and click the More dropdown and select Cancel Transfer.

List pending transfers

openstack volume transfer request list

Cancel a transfer

openstack volume transfer request delete <transfer-id>

Transfer cancelled. The volume remains in the source project with status Available.

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

Core Services

Other Services

Overview

How Volume Transfers Work

Transfer a Volume

Step 1 — Create the Transfer Request (Source Project)

Navigate to Volumes

Create transfer

Record the credentials

Authenticate as source project

Create transfer request

Step 2 — Accept the Transfer (Destination Project)

Switch to destination project

Accept the transfer

Verify

Authenticate as destination project

Accept the transfer

Verify

Cancel a Pending Transfer

Important Limitations

Next Steps

Create a Volume

Volume Snapshots

Attach / Detach

Volume Types

​Overview

​How Volume Transfers Work

​Transfer a Volume

​Step 1 — Create the Transfer Request (Source Project)

Navigate to Volumes

Create transfer

Record the credentials

Authenticate as source project

Create transfer request

​Step 2 — Accept the Transfer (Destination Project)

Switch to destination project

Accept the transfer

Verify

Authenticate as destination project

Accept the transfer

Verify

​Cancel a Pending Transfer

​Important Limitations

​Next Steps

Create a Volume

Volume Snapshots

Attach / Detach

Volume Types

Overview

How Volume Transfers Work

Transfer a Volume

Step 1 — Create the Transfer Request (Source Project)

Step 2 — Accept the Transfer (Destination Project)

Cancel a Pending Transfer

Important Limitations

Next Steps