Environment Export/Import: How to Migrate Application between Clouds

Platform-as-a-Service is designed to provide a real freedom of choice to developers: no proprietary APIs, no necessity to adjust your applications’ code before hosting, a wide variety of stacks and features available. And one of the key options that exempts our users from any lock-in is the Environment Export / Import feature. It allows to easily migrate hosted applications across available PaaS installations (i.e., hosting provider platforms). In such a way, you are able to switch to the most suitable platform according to your current preferences (e.g., due to platform versions differentiation or pricing systems distinctions) at any time.

Notes:

You can also use the Environment Transferring option for moving your projects between different accounts of a single hosting provider platform, without the necessity to export/import them.

Currently, the Environment Export feature exports only topology information. The imported environment will be created from scratch without any custom data inside.

Environment Export / Import feature to work properly, the initial hosting provider’s platform should have the 7979 port opened, which is intended to be used for downloading environment source files during the import operation. Thus, depending on a particular provider’s configurations, exported environments from some of our partners’ platforms may be not available for importing at other PaaS installations.

What’s next?

Default Environment Variables
Java Options and Arguments
Container Variables
Configuration File Manager