Environment Transferring

Environment transfer enables you to shift any environment to a different PaaS account on the same platform, with confirmation needed from both parties involved.

Reasons

This feature can come in handy in various situations. For instance:

• If you want to shift all your projects to a new account, perhaps because you’ve registered with a different email address.
• When you need to transfer your work projects to another developer’s account, like when an employee leaves the company.
• If you need to move a production-ready environment from a personal testing account to the main company account.
• Restoring environments from an old deactivated account without having to reactivate it.

Note: Additionally, service hosting providers can provide a service where they create the necessary application for you. Once configured and tested, the fully operational environment will be transferred to your account.

Conditions

You can move any environment, whether it’s active or not, from any account, even if that account isn’t active anymore. However, the account you’re moving it to needs to meet these conditions:
It can be any type of account—beta, billing, etc.—but not a trial one.

• It should be active, meaning it hasn’t been suspended or deactivated.
• And it needs to have enough space, or quotas, available to accommodate the environment you’re adding.

Please keep in mind: On platforms older than version 5.9.3, you can only transfer environments to billing accounts.

During the transfer process, various limits are examined, such as the number of cloudlets per container, nodes per environment, and active environments on the account. This includes checking for features like public IP, VPS, or high-availability, if they’re activated in the transferred environment.

If any issues arise, you’ll receive a notification on the dashboard right away:

Note: Right now, the ability to transfer environments between accounts on different PaaS installations, including interactions between the main platform and sub-platforms (resellers), isn’t available.

Once an environment is transferred, it remains unchanged. The new owner gets it just as it was, with all the apps and custom setups intact. From then on, any costs for the environment will be the responsibility of the new owner.

Additionally, when ownership changes, access to the environment is no longer shared with previous users.

Transferring Steps

Let’s take a look at how we transfer an environment.

1. Press the Settings button located beside the environment you need.

2. Go to the tab that’s open, find where it says Change Owner, and type in the email address of the person you want to become the new owner.

To move forward, simply click on the Send Request button.

3. If the account you’re aiming for exists and fulfills all the necessary criteria, you’ll receive a notification confirming that your request has been sent.

Note: You have the option to cancel your request anytime using the button labelled Cancel Request unless it’s already been confirmed.

4. The designated user will get an email asking them to confirm an environment transfer. You just need to click on the Confirm Transfer to proceed with the transfer process.

Note: As the confirmation is pending, the environment gets labelled with a special icon on the initial owner’s dashboard, indicating that a transfer is still in progress.

5. Once the intended recipient of the transfer approves the request (by clicking the link in the email), the setting vanishes from the original user’s dashboard and pops up for the new owner. The initial owner will receive an email notification confirming the successful transfer.

Note: In this step, we double-check the target account to ensure it has the necessary limits. If it falls short, the transfer process halts. The user will see an error message on their dashboard and receive an email notification explaining the issue.

It’s straightforward! With this feature, you can effortlessly transfer environments from one account to another.