Environment Transferring

Transfer an Environment

Environment transferring allows the ownership of an existing environment to be moved from one platform account to another. The environment configuration, deployed application and associated resources remain in place while management responsibility is assigned to the receiving account.

In this article

Transfer Overview

The transfer operation changes the account that owns and manages an environment. It is useful when a project is handed over to a customer, reassigned to another team, or moved between accounts without rebuilding the application.

Environment ownershipManagement control is assigned to the receiving platform account.
Application dataDeployed files, databases, configuration and environment topology remain associated with the environment.
Environment availabilityThe transfer is designed to avoid rebuilding or redeploying the application.
Billing responsibilityFuture resource consumption is associated with the receiving account after the transfer is completed.
!

A transfer is not the same as account collaboration

Transferring changes the environment owner. When another user only needs shared access, use the collaboration feature instead of transferring ownership.

Environment transfer overview
Transfer an environment when permanent ownership must move to another account.

Requirements and Limitations

Review the environment and both user accounts before initiating the transfer.

Recipient accountThe recipient must have an active account on the same platform installation.
Account limitsThe receiving account must have sufficient balance, quotas and permission to own the environment.
Environment statusFinish critical deployment, scaling or maintenance operations before starting the transfer.
Provider policyThe hosting provider may restrict transferring for certain environment types, subscriptions or account plans.
✓

Prepare a handover record

Before transferring a production environment, document its domains, credentials, integrations, backup status and operational contacts for the recipient.

i

Review account-specific resources

Items tied directly to the original account, such as external integrations, collaboration permissions, payment settings or account-level access keys, may need separate review after transfer.

Start an Environment Transfer

1

Select the environment

Locate the required environment in the platform dashboard.

2

Open Settings

Click the environment’s Settings button to open its management options.

3

Open Transfer

Select the Transfer or Change Owner section, depending on the interface provided by the platform.

Open environment transfer settings
Open the transfer settings for the required environment.

Specify the Recipient

1

Enter the recipient account

Provide the email address or account identifier registered for the receiving platform user.

2

Review transfer details

Confirm the environment name, recipient and any warnings shown by the platform.

3

Send the transfer request

Click Transfer, Send Request or the equivalent confirmation button.

Enter recipient account for environment transfer
Enter the recipient’s registered platform account and confirm the request.
!

Verify the recipient carefully

Confirm the recipient account before sending the request. After the transfer is accepted, the original owner may lose administrative control of the environment.

Accept the Transfer

The receiving user must review and accept the transfer before ownership is changed.

1

Open the notification

The recipient should sign in and open the platform notification, dashboard request or email associated with the transfer.

2

Review the environment

Check the environment name, topology, expected resource consumption and any applicable account limits.

3

Accept the request

Select Accept to complete the ownership transfer. The recipient may also decline the request when the environment should not be received.

Accept an environment transfer request
The recipient reviews and accepts the environment transfer.
✓

Check quota and balance before acceptance

The recipient should ensure that the account can support the environment’s current and future resource usage before accepting ownership.

Verify the Transferred Environment

1

Confirm dashboard ownership

Verify that the environment is displayed in the recipient’s dashboard and is no longer listed under the original owner.

2

Test application availability

Open the application and confirm that its public URLs, custom domains and internal services remain accessible.

3

Review management access

Confirm that the recipient can configure nodes, deploy updates, access logs and manage environment settings.

4

Review integrations and permissions

Check collaborators, SSH access, deployment credentials, API integrations, registry access and external services.

Environment transfer completed
Verify that the environment is available and manageable under the receiving account.

Expected Result

The environment is assigned to the recipient’s platform account. Its application, topology and stored data remain available, while ownership, management responsibility and future resource usage move to the receiving account.

Important Notes

  • Use account collaboration when permanent ownership transfer is not required.
  • Confirm the recipient’s registered account before sending the request.
  • Verify that the receiving account has enough quota, balance and permissions.
  • Create a recent backup before transferring a production environment.
  • Complete active deployments, scaling operations and maintenance tasks first.
  • Review account-specific integrations, collaborators and credentials after transfer.
  • The original owner may lose management access after the recipient accepts the request.

Common Issues and Solutions

Transfer option is unavailableThe provider may have disabled the feature, or the environment type may not support ownership transfer.
Recipient account is not foundConfirm the exact email address or account identifier and ensure the user is registered on the same platform.
Request cannot be sentCheck the environment status and complete any active deployment, scaling or maintenance operation.
Recipient cannot acceptReview the receiving account’s balance, quotas, subscription plan and provider restrictions.
Transfer request remains pendingAsk the recipient to review platform notifications and email, or cancel and resend the request when supported.
Original owner still needs accessThe new owner should add the original user through account collaboration with the appropriate permissions.
Integration stops working after transferReview account-level API keys, registry credentials, SSH keys, allowlists and external billing or monitoring integrations.

Related Guides