When working with multiple Loome Integrate tenants, there may be a need to sync the contents from one to another. The Import/Export feature of Loome Integrate aims to support this use case by providing options for moving jobs and tasks, as well as all their dependencies, between tenants both within the Integrate application and through third party integrations.
To get started using Import/Export, you first need to decide which import method best suits your business case. Integrate supports two methods of importing data from one tenant to another.
Loome Integrate supports importing the contents of one tenant (the ‘Source Tenant’) into another (the ‘Target Tenant’). This is kicked off from the target and essentially pulls all the jobs and tasks in from the source.
Tenant to Tenant is good for scenarios where you need to quickly import data from one tenant into another and don’t have a need for version control or tracking of changes between each import.
If you require tracking of the changes between each sync or more formality around changes to a tenant, the Git Repository Import is more suited to your use case and is further explained below.
Learn more about Tenant to Tenant imports here.
Loome Integrate supports exporting the contents of its tenant to a Git Repository. Jobs, tasks and all their dependencies are stored as human readable JSON files that can be compared for changes using pull requests. The contents of the repository can then be uploaded back into the tenant using a secured API endpoint.
We support any Git provider as an export target, and currently provide step by step instructions for creating a Continuous Integration/Continuous Development pipeline using Azure Devops.
The use of pull requests allows for tracking of the changes between each sync and provides more formality around changes to a tenant.
Learn more about importing to a Git Repository here.
As well as importing your tenant, you can import and export the connections in your tenant. This occurs separately from the import of a tenant in order to keep the credentials you provided separately from a connection string secure.
If you would like to migrate connections between tenants, this means that you will have to download and upload your connections before each import.
You will also need to add usernames and passwords, and validate the connections that you wish to use in this target tenant on the Connections page in order to run any jobs that use these connections.