Import / Export

Effortlessly backup, transfer, and migrate your Nodinite configuration between different instances. This guide explains how to use Import/Export and the Web API to manage integrations, repository data, and user roles—ensuring business continuity, compliance, and rapid deployment.

✅ Backup and migrate your Nodinite configuration for disaster recovery and upgrades
✅ Transfer integrations, repository models, and user roles between environments
✅ Use the Web API for flexible, automated import/export operations

![IMPORTANT]

In Nodinite version 7.0, this feature has been disabled. It will be reintroduced in a future version. Please use the Web API to export and import data between instances of Nodinite for now.

Backup and transfer your Nodinite configuration between different instances of Nodinite.

Currently, the following artifacts/entities/items can be managed by the Import / Export feature:

• Repository Model
  • Integrations
  • Systems
  • Services
  • Message Types
  • Endpoints
  • Articles
  • Custom Fields
  • Custom Metadata
• Roles
  • Users

The diagram above illustrates the import/export process between Nodinite instances, including transfer methods and modules.

1. The general idea is first to create and configure data in one Nodinite instance (Source).
2. Once you're happy with your configuration you can then select items to be exported. During the export operation, all dependencies to other items are identified by the system and get selected. You can pinpoint specifically what items should be part of the export or exclude items as you wish/feel fit.

Tip

You should be generous of selected items to be exported. It is possible, to pinpoint specific items to be included during the import operation later. You can not import more than what is part of the Import module.

3. The following two options for transferring content are currently available:
   1. Synchronous using the Web API (requires online network access) or
   2. Asynchronous using a JSON based file (offline)
4. Items exported are managed by an Import Module on the target Nodinite instance. If you performed the export operation with the file option, you must Upload it next on the target Nodinite instance
5. The Import Module is then imported with selected items. Any changes or problems are presented with a migration report with ability to resolve any conflicts/changes
6. Final destination for exported data (Target)

Here's an example of links providing Access to the Import / Export operations

Security/User rights

You must be a member of the Nodinite built in Administrators Role in both the source and target Nodinite instance.

Next Step

Export
Upload
Import

Related Topics

External Instances

• Access Management
• Web Client