Export Environment

Export an Environment

Environment export creates a portable JSON package containing the selected environment configuration and data. The exported package can be downloaded, stored as a backup reference or imported into another compatible platform installation.

In this article

Environment Export Overview

The environment export process collects the environment topology, selected configuration files, application files and private data into a single .json manifest. This package can then be imported into another compatible cloud platform to recreate the environment.

Portable JSON packageStores the exported environment definition in a compact downloadable file.
Cross-platform migrationSupports moving an environment between compatible platform installations.
Selective contentAllows topology, private data and configuration files to be included according to migration requirements.
Reusable export copiesMultiple exported manifests can be created and retained for later use.

Requirements and Limitations

!

The environment must be running

An environment can be exported only while it has the Running status.

i

Source access must be available during import

The source platform may need to allow the import process to download environment files through the required service port. Export and import availability can therefore depend on the hosting provider’s network configuration.

Before beginning a migration, verify that both the source and destination platforms support environment export and import. Also confirm that the destination platform offers compatible node types, software stacks and sufficient resource quotas.

Start the Export Process

1

Locate the environment

Sign in to the dashboard and find the running environment that you want to export.

2

Open environment settings

Click the Settings button for the selected environment.

3

Open the Export section

Navigate to Export in the environment settings and click the export action.

Environment settings button
Open the settings of the running environment that should be exported.
Environment export section
Select the Export section from the environment settings.

Select Export Content

In the Environment Export dialog, choose which parts of the environment should be included in the package. Select all available options when a closely matching copy is required.

Topology SettingsIncludes the environment structure and resource configuration defined through the topology wizard. This option is required and enabled by default.
Private DataIncludes application files and private information stored inside supported application and database nodes.
Configuration FilesIncludes files visible through the configuration manager and settings for deployed Git or SVN projects, such as repository links, access credentials and attached SSH keys.
1

Select the required data categories

Enable the options that match the migration or backup requirement.

2

Review the selection

Confirm that all important application and configuration data is included.

3

Click Export

Start the package creation process and wait for the platform to complete the export.

Environment export options dialog
Choose topology settings, private data and configuration files before starting the export.
✓

Keep the source environment until migration is verified

Do not delete or permanently modify the original environment until the exported package has been imported successfully and the copied application has been tested.

Container-Specific Considerations

Some node types and services require additional attention during export and later import.

Elastic VPS, Maven, Docker and Windows nodesTheir runtime data may not be included in the export. The node can still appear in the imported topology but may need to be configured again manually.
NGINX nodesAn NGINX load balancer or application server may be stopped briefly and restarted automatically while the platform creates the server dump.
Private SSH keysRepository SSH keys included with Git settings may continue to be used after import even when they are not displayed in the dashboard. Selecting a new key replaces the imported one.
!

Review unsupported data before migration

Create separate backups or configuration records for node types whose files are not included in the environment export package.

Download the Exported Package

After the export completes successfully, a new date- and time-based entry appears in the Exported Environment Copies list.

1

Locate the completed export

Find the newly created entry in the exported copies list.

2

Download the JSON file

Click the export entry to save the compiled .json package to your local computer.

3

Copy the manifest address when required

Use the available context action to copy the direct package address. This address may also be used during environment import.

Exported environment copies list
Download the completed JSON package or copy its manifest address.

The account may also receive an email notification containing access to the list of completed environment exports.

Manage Exported Copies

Multiple export packages can be retained in the account. Each package consumes storage space and may therefore affect platform usage charges according to the hosting provider’s tariff.

DownloadSaves the selected environment package to the local computer.
Copy manifest addressProvides a direct reference that can be used during environment import.
Delete exportRemoves an unneeded package from the account storage.
Create another copyGenerates a separate export package based on the current environment state and selected data options.

Expected Result

A downloadable JSON package is created for the selected environment. The package contains the mandatory topology settings and any optional private data or configuration files selected during export. It can then be imported into another compatible platform installation.

Important Notes

  • The environment must be running before export can begin.
  • Topology settings are mandatory and included by default.
  • Select Private Data and Configuration Files when a more complete environment copy is required.
  • Some node types do not include their runtime data and must be reconfigured after import.
  • An NGINX node may restart briefly during export.
  • Keep the original environment until the imported copy is fully tested.
  • Exported packages use account storage and may contribute to platform charges.
  • Protect downloaded JSON packages because they may reference sensitive configuration or access information.

Common Issues and Solutions

Export button is unavailableConfirm that the environment is running and that the account has permission to manage it.
Application data is missing after importCheck whether Private Data was selected and whether the affected node type supports data export.
Configuration is incomplete after importVerify that Configuration Files was included and recreate unsupported settings manually.
Export takes longer than expectedLarge application files, databases and configuration archives can increase package generation time.
Export cannot be imported elsewhereConfirm destination compatibility and verify that the source platform permits access to the package files required during import.
Account storage usage is increasingDelete obsolete exported copies after retaining any required local backups.

Related Guides