Moving data and integration projects between environments

As an administrator, you can move BMC Helix Multi-Cloud Broker data and BMC Helix iPaaS, powered by Jitterbit integration projects from one environment to another environment. By moving data across environments, you make sure that you test and verify the data and integration projects before making them available to your users.

For example, you want to deploy the BMC Helix ITSM and Jira integration template to an environment available to your users. The following events occur in different environments:

1. Environment 1—You update the integration template with your system details and move the template to Environment 2.
2. Environment 2—The quality analyst team in your company tests the template and verifies that it is working as expected.
   Then, you move the template to Environment 3.
3. Environment 3—You deploy the template and it is available to your users.

Types of environments

The following image lists the different environments between which you can move data and shows a typical sequence of moving data:

Refer to the following table to access information about moving data and integration projects: