This will allow you to easily migrate your work around multiple servers from a UI driven option like migrating the reports dashboards from development server to production server etc. Note that functionality has been added from version 5.0 instance onward. In order to avoid any complication it is better if both source and target are exactly in the same version of Helical Insight.
Export
Let us first understand exporting from one Helical Insight instance with all the possible options.
Anyone who has rights on the folder can export the folder and all its content by simple right-click on the folder and selecting Export.

You can also choose what all options do you want to export from this folder along with all the files and folder structure. You can
From Helical Insight version 7.1.0.367 RC1, additional options have been introduced in the Export functionality to provide better control over the content being migrated between Helical Insight instances.
When you right-click on an individual folder/file in the File Browser and select Export, an Export popup appears with the following options:
Available Export Options
- File and Folder (Default): Selected by default. It exports all files and folders along with their existing folder structure.
- Datasources (Default): Selected by default. Exports the datasource configurations associated with the selected folder/files, allowing them to be migrated to another Helical Insight instance.
-
Recycle Bin (Default): This option is introduced in Helical Insight 7.1.0.367 RC1. It allows you to export the contents of the Recycle Bin along with the selected folder.
- By default, this option is selected.
- If selected, the Recycle Bin contents are included in the export package.
- If unselected, the Recycle Bin contents are not included in the export package. During import, the existing Recycle Bin contents on the target instance are restored.
Note: Before version 7.1.0.367 RC1, there was no separate option to control the export of Recycle Bin contents.
NOTE: Usage of Recycle Bin Option
In Helical Insight, resources can depend on each other. For example, dashboards depend on reports, reports on metadata, and metadata on data sources.
Sometimes, a resource may be deleted even though other resources still depend on it.
The Recycle Bin Export option helps preserve such deleted resources during export/import.
Example:
Suppose a folder contains a dashboard, reports, and metadata files. Two of the reports have been deleted and moved to the Recycle Bin.
- Without selecting the Recycle Bin option: The two deleted reports will not be included in the export and will therefore be missing from the target server.
- With the Recycle Bin option selected: The two deleted reports will also be exported and imported into the Recycle Bin of the target server.
This allows the administrator to recover those deleted reports whenever required, ensuring that dependent resources are not permanently lost during migration.
-
Share Details:
If any of the folder/files content is shared with different permission levels, this option allows you to export sharing information associated with folders, including user and role permissions. This helps maintain the sharing configuration when migrating content between instances. -
Schedules:
If any of the files have been scheduled, this configuration allows you to export scheduled report and dashboard configurations.Note that on your target machine, you still have to configure email SMTP settings in the backend to be able to use email scheduling. These schedules can then be used after migration to the newer server.
Once you have selected the required options, click Export. A ZIP file containing the selected content will be downloaded to your local machine.
📌 Note
Right now we have exported a single file/folder. From version 5.2 we have also added an “Export All” option which exports the entire file browser repository in a single go which can be imported, thus saving lot of time. In order to learn how to do that please refer this blog: https://www.helicalinsight.com/export-import-all-files-from-file-browser-repository/
Import
Importing the zip files is pretty simple too. Once you have the exported file from any of Helical Insight instance, you can simply take the zip file to another machine. On the admin home page you have option of Management and in it, select Import. Note that this importing is admin functionality only, if are a non admin role user you will not be able to see it and use it.

Select your zip file with Select File button.

- Options: As soon as it recognizes the file it will check all the boxes that this zip file contains automatically for you. If you find something incorrect, please seek attention of this with the person who exported this folder for you.
While importing you can remove anything that you do not want to import. Like if you do not want to copy data sources or schedules, you can uncheck that. Even if it is present in the zip file it will be ignored. - On Conflict: This option helps you manage the duplicity of the files. If the file(s) with same name exists, what do you want this import module do? You can, Skip the import and retain what you already have on this server; or Update and overwrite the existing files with new files from current zip. Choose the option based on your needs and click on Import.
Congratulations, now you will have all your files in the new Helical Insight 5.0 instance.

Manage your multiple Helical Insight instances easily with Export and Import functionalities now with this simple import and export functionality.
Helical Insight considers resources present in both the File Browser and the Recycle Bin during Import/Export operations.
1. Understanding Resource Dependencies
In Helical Insight, resources often depend on other resources to function correctly. When importing or exporting a resource, its associated dependencies must also be considered.
For example, the following dependencies exist:
Resource dependency flow in Helical Insight
- Dashboards depend on Reports: Reports are used to create and populate dashboards.
- Reports depend on Metadata: Reports use metadata to access and organize data.
- Metadata depends on Datasources: Metadata connects to the underlying datasources.
Therefore, resources stored in the Recycle Bin are also considered during Import/Export conflict detection. This ensures that Helical Insight identifies existing resources and their dependencies, regardless of whether they are in the File Browser or Recycle Bin.
2. Import Behavior: Skip vs. Update
The following table explains how resources are handled during the import process based on their locations in the source and target environments.
Understanding the table: R1 represents a resource and its respective location (File Browser or Recycle Bin). The table shows the resource locations in both source and target environments before and after importing.
R1 = Resource being imported
— = Resource is not present
| Import Mode | Stage | Source | Target | Explanation | ||
|---|---|---|---|---|---|---|
| File Browser | Recycle Bin | File Browser | Recycle Bin | |||
| SKIP | Before Import | R1 | — | — | — | The resource does not exist in the target. Therefore, Skip and Update produce the same result. The resource is transferred to the same location as in the source. |
| After Import | — | — | R1 | — | ||
| Before Import | R1 | — | — | R1 | The resource already exists in the target Recycle Bin. With Skip selected, the resource is not imported because it already exists in the target environment. | |
| After Import | — | — | — | R1 | ||
| Before Import | — | R1 | — | — | The resource does not exist in the target. Therefore, Skip and Update produce the same result. The resource is transferred to the Recycle Bin, matching its source location. | |
| After Import | — | — | — | R1 | ||
| Before Import | — | R1 | R1 | — | The resource already exists in the target File Browser. With Skip selected, the resource is not imported because it already exists in the target environment. | |
| After Import | — | — | R1 | — | ||
| UPDATE | Before Import | R1 | — | — | — | The resource does not exist in the target. Therefore, Skip and Update produce the same result. The resource is transferred to the same location as in the source. |
| After Import | — | — | R1 | — | ||
| Before Import | R1 | — | — | R1 | The resource already exists in the target Recycle Bin. With Update selected, the resource is imported and restored to the File Browser, matching its location in the source. | |
| After Import | — | — | R1 | — | ||
3. Recommended Approach
When a resource already exists in the target Recycle Bin, consider the following approaches before proceeding with the import:
Option 1: Clean Up the Recycle Bin
If the resource should be treated as a completely new resource, permanently delete the existing resource from the target Recycle Bin before importing.
Option 2: Use Update
Select the Update option during import if you want to restore the existing resource with the updated content from the source environment.
Import/Export functionality is available only to Administrators, who also have access to the Recycle Bin. This ensures that resource conflicts can be identified and managed across both the File Browser and Recycle Bin.
4. Key Takeaways
- Helical Insight checks resources in both the File Browser and Recycle Bin during Import/Export operations.
- Resource dependencies must be considered to avoid conflicts during migration.
- Skip prevents importing a resource that already exists in either target location.
- Update allows an existing resource in the target Recycle Bin to be restored with the source content.
- Permanently deleting an existing resource from the Recycle Bin allows it to be treated as a new resource during import.
- Only Administrators can perform Import/Export operations and manage Recycle Bin resources.
