Import Environment

Import an Environment

The Environment Import feature lets you create and configure an environment from a supported manifest file or package definition. It can be used to restore an exported environment, migrate an application between compatible platforms, or deploy a custom JPS-based solution.

In this article

Supported Import Options

The platform can process environment and package definitions in several commonly used formats.

Supported files.json, .jps, .yml, .yaml and .cs files.
Exported environmentsRecreates a previously exported environment on another compatible platform installation.
Custom packagesDeploys solutions described through JPS, JSON or YAML manifests.
Ready-made packagesAllows installation of prepared packages from a package collection or direct manifest URL.
!

Platform version compatibility

An exported environment should be imported into a platform installation running the same or a newer compatible version. Importing into an older version may cause deployment or configuration errors.

Start an Environment Import

1

Open the dashboard

Sign in to the platform dashboard using an account that has permission to create environments.

2

Click Import

Select the Import button from the main toolbar at the top of the dashboard.

Choose the Import Source

The Import window provides three methods for supplying the required manifest or package definition.

Local FileUpload a supported manifest stored on your computer by using the Browse or file-selection option.
URLEnter a direct link to a remotely hosted manifest file.
JPSPaste, edit or create JPS, JSON or YAML code directly in the built-in editor.
1

Select the required tab

Choose Local File, URL or JPS depending on where the package definition is stored.

2

Provide the manifest

Upload the local file, paste the direct URL, or enter the package code in the JPS editor.

3

Click Import

After the manifest is accepted, click Import in the lower-right corner of the selected tab.

Local File, URL and JPS environment import options
Choose the appropriate source for the environment manifest.
✓

Use package examples as a reference

Ready-made JPS packages can help you understand the required manifest structure and can also be imported directly when a suitable package already exists.

Configure the New Environment

After the manifest is processed, the platform displays a confirmation window with package details and the settings required for the new environment.

EnvironmentEnter the unique domain name or environment name for the imported solution.
Display NameOptionally enter an alias that will be shown in the dashboard instead of the technical environment name.
RegionSelect the data-center region where the environment should be hosted, when multiple regions are available.
1

Review the package information

Check the package name, description and source details. For exported environments, the confirmation may also show the source platform and export date.

2

Complete the environment settings

Enter the environment name, optional display name and required region.

3

Confirm the import

Click Import to begin creating and configuring the environment.

Environment import confirmation settings
Review the package and configure the imported environment.

Monitor the Import Process

The platform automatically creates the environment, deploys the required nodes and applies the settings defined in the manifest.

1

Follow the installation progress

Keep the progress window open to monitor the current deployment stage and package actions.

2

Continue working when required

You can minimize the progress window and continue using the dashboard. The import process will continue in the background.

3

Review the completion message

After the deployment is finished, the platform displays a success window.

4

Open or reconfigure the environment

Select Open in Browser to test the application immediately, or close the dialog and update settings such as hostnames, IP addresses, credentials or integrations.

Imported environment deployment progress
The environment is created and configured automatically.
i

Review the confirmation email

The platform may send important information about the imported environment, including hostnames or newly generated administrator credentials.

JPS Deployment and Troubleshooting

The Import > JPS option is useful for developers who create automation packages, repeatable deployments or CI/CD workflows.

Automatic validationThe editor parses the code and marks detected errors near the relevant line.
Local draft retentionUnsaved code can be retained in the browser so work can continue after closing and reopening the Import window.
Format JSONApplies readable indentation and line breaks to JSON content.
Wrap LinesWraps long lines to fit within the editor width.
SearchFinds text in the manifest with optional case-sensitive and regular-expression matching.
View LogsOpens execution logs for monitoring and troubleshooting package actions.
JPS editor for environment import
Use the built-in JPS editor to validate and test package code.
✓

Check logs first when deployment fails

Open View Logs and locate the first reported error. Later errors are often consequences of the original failure.

Expected Result

A new environment is created from the selected manifest and configured automatically according to the package definition. After successful deployment, the application can be opened, tested and adjusted for the target platform.

Important Notes

  • Import exported environments only into a compatible platform version.
  • Use a direct file URL when importing through the URL tab.
  • Ensure the environment name is unique before confirming the import.
  • Review the selected region before deployment when multiple regions are available.
  • Check package code and validation warnings before importing through the JPS editor.
  • After migration, verify hostnames, IP addresses, credentials, integrations and external dependencies.

Common Issues and Solutions

Manifest file is rejectedConfirm that the file uses a supported extension and contains valid JSON, JPS or YAML syntax.
Remote URL cannot be loadedUse a publicly accessible direct file URL and verify that it does not require an interactive login.
Environment name is unavailableChoose another unique environment name and repeat the confirmation step.
JPS editor shows validation errorsOpen the marked lines, correct the syntax or required parameters and validate again.
Deployment stops during installationOpen the import logs and identify the first failed action, missing resource or unsupported component.
Application opens incorrectly after migrationReview domain bindings, IP addresses, environment variables, database connections and platform-specific settings.

Related Guides