Assets such as workflows, releases, models, and system settings are essential components of a Hyperscience deployment. Migrating them between development, testing, and production instances helps maintain consistency while reducing the need to recreate configurations and retrain models.
This article explains how to import and export these assets.
Importance of migration
Asset migration helps organizations move validated configurations and trained assets between instances while maintaining consistency throughout the deployment lifecycle.
Migration supports:
Consistent configurations – Keep workflows, models, releases, and system settings aligned across instances.
Faster deployment – Reduce the time and effort required to move validated assets between instances.
Testing and validation – Validate assets in lower instances before deploying them to production.
Common scenarios for migration
Asset migration is commonly used in the following scenarios:
Instance upgrades – Moving assets during application upgrades or when transitioning between Hyperscience versions.
Assets promotion – Promoting validated assets from lower instances, such as development or testing, to higher instances, such as production.
Workflows expansion – Deploying new workflows, layouts, or models to support additional document types or business processes.
Model and configuration updates – Migrating updated models, releases, or system settings to improve document processing performance.
Assets available for migration
Workflows
Releases
Classification models
To learn more about Classification, see Structured Document Classification and Semi-structured Document Classification.
Field Identification models and Table Identification models
Transcription Models
Vision Language Models (VLM)
Permission Groups
Field Dictionary
Translations
Learn more in Providing a Translated User Interface.
System Settings
The core configurations of the platform. Learn more in Application Settings Overview.
Migration process
Preparation
If you are migrating assets as part of an application upgrade, review the following articles before you begin:
Component dependencies
You can import or export one component at a time.
When migrating models, releases, or configurations, ensure that all required dependencies are included and verified after import.
(v42.3 and later) Migrating assets from the Assets page
Assets tab replaces the Import/Export tool in v42.3 and later.
Starting with v42.3, you can import and export supported components from Administration > Assets.
The Assets page groups supported asset types into categories and provides dedicated Import and Export actions for each component.

To migrate a component:
1. Go to Administration > Assets.
2. Locate the component type you want to migrate.
3. Select Import or Export.
4. Follow the steps in the respective modal.
Component-specific considerations
The available import/export steps vary depending on the component type.
Classification Models
Ensure that the Classification model is compatible with the target release version.
Training data is not included when importing or exporting Classification models. To learn more, see TDM for Classification models.
Field & Table Identification Models
Field & Table Identification models are associated with layouts.
When importing or exporting a model, select the relevant layout. Learn more in Identification Models Overview.
System Settings
You can choose which settings to include when exporting.
Importing system settings replaces the selected configuration values with those from the imported file. To learn more, see Application Settings Overview.
Releases
Release packages can contain layouts, custom data types, and related configuration.
When importing a release, choose how to handle duplicate custom data types. Learn more in Releases.
Field Dictionary
Field Dictionary entries are imported from and exported to CSV files.
Download the sample CSV file to review the required format before importing.
Imported entries must reference existing data types. To learn more, see our Data Types category.
Translations
Translation files are imported from and exported to CSV files.
Select the target locale before importing a translation file.
Use an exported translation file as a template when creating or updating translations. Learn more about translations in Providing a Translated User Interface.
(v42.2 and earlier) Import / Export tool
In v42.2 and earlier, you can import and export supported components from Administration > Import/Export.
The Import/Export tool allows you to migrate supported components between Hyperscience instances.
Using the Import/Export tool
Go to Administration > Import/Export.
Select the component you wish to import or export.
Click Export to download a bundle or Import to upload one.
Follow any on-screen prompts to complete the action.
Migrating assets from individual component pages
Assets can also be imported and exported directly from their respective pages. See the drop-downs below for asset-specific migration.
Exporting and importing flows
Exporting flows
Follow the steps below to export a flow:
Go to the Flows page and find the one you want to export.
Click on the menu () for the flow and click Export All Flows.
When exporting a flow from this menu, all connected subflows are included in the export.
You can also export your flow from its details page:
Go to the Flows page and find the flow you want to export.
Open the flow’s details page and scroll down to the Flows table.
Click Export on the Top-Level Flow.
The exported file is named Flow-[Flow_name]-[Flow_UUID]-[YYYYMMDD_HHMM].zip, where:
[Flow_name]is the name of the flow.[Flow_UUID]is its unique identifier.[YYYYMMDD_HHMM]represents the export date and time in GMT.
The ZIP file includes:
A
flowsfolder, containing the flow’s JSON file.A
manifest.jsonfile with metadata about the export.If the flow contains Code Blocks, their Python files are included.
Note that client secrets and Python package dependencies are not included in the export.
Importing flows
To import your flow:
Go to the Flows page.
Click Import Flow.
Upload the ZIP file you exported.
Exporting and importing releases
Exporting releases
Follow the steps below to export your releases:
Go to Library > Releases, and locate the release you want to export.
Use the search box to find the release by name or click Filters to filter the releases by status.
Click the name of the release to open its details.
Click Actions, then select Download Release.
The system may take a few minutes to prepare the file. You will receive a notification when it’s ready.
When notified, go to Notifications, find the entry for your file, and click Download.
The downloaded ZIP file contains the following assets:
A JSON file containing metadata about the release, such as creation and last updated timestamps.
manifest.json, which includes a summary of the release’s contents.field_data_types.json, containing a list of data types used in the release.Individual JSON files for each layout version in the release.
Individual JSON files for each layout variation with selected field customizations applied.
Importing releases
To import your release:
Go to Library > Releases and click Add Release.
Select Upload Existing.
Choose one of the following options:
Drag and drop the ZIP file into the dialog box.
Click Choose File to locate and upload the file from your machine.
Under How To Handle Duplicate Custom Data Types? select an option:
Skip if duplicate custom data type exists - Retains the existing custom data type’s list of values without overwriting.
Update with data from the JSON - Overwrites the existing custom data type’s list of values with those from the imported file.
Click Upload.
The system may take a few minutes to process the release. You will receive a notification when the process is complete.
When uploading a release, all included layouts are added to the Layout Library if they do not already exist. If the release was assigned to a flow in the testing instance, it will be automatically assigned to the same flow in the Production Instance. Field customizations applied to the release are incorporated into the layout’s variations, but they will not appear in the Fields and Customizations tab on the layout’s details page. To learn more, see Adding a New Release.
After the import is finished, click View Release in the Notification Center to view the release’s details.
Exporting and importing Classification models
Exporting Classification models
You can export Classification models through Training Data Management in v40.1 and later. Learn more in TDM for Classification.
Follow the steps below to export a Classification model:
Go to Library > Models.
Click on Classification Models in the drop-down list at the top of the page.
Click on the name of the model you want to export.
Click the menu () in the upper-right corner of the page, and click Download Classification Model.
The system may take a few minutes to prepare the file. You will receive a notification when it’s ready.
When notified, go to Notifications, find the entry for your file, and click Download.
or
On the model’s details page, scroll down to the Model Activity table.
Click the Download model button next to the last-trained version of your Classification model.
The ZIP file contains the following items:
Metadata for the model.
The model itself.
Note that the model’s training data is not included in the ZIP file.
Importing Classification models
Classification models can be uploaded only in v40.1 and later and only for live releases. Learn more in TDM for Classification.
Go to Library > Models.
Click Classification Models in the drop-down list at the top of the page.
Click Import Model.
Exporting and importing Identification models
Exporting Identification models
Follow the steps below to export your Identification models:
Go to Library > Models.
Find your Identification model and click its name.
On the model’s details page, scroll down to the Model History table.
Click the download button () in the Actions column to export the model.
The ZIP file contains:
Model metadata.
The model itself.
Note that the training data is not included in the ZIP file.
Exporting training data
To export the training data for your Identification model:
Go to Library > Models.
Open the model you want to export the training data for.
Click Actions, and then click Download training documents… in the drop-down list.
The system may take a few minutes to prepare the file. You will receive a notification when it’s ready.
When notified, go to Notifications, find the entry for your file, and click Download.
You must annotate your documents before downloading the training data.
The export consists of a training data ZIP file with the following elements:
A JSON file with training data.
Document images.
Layout version.
A training data ZIP file contains up to 500 pages. If a model has more than 500 pages of training data, the data is split into multiple ZIP files. For example, if a model has 900 pages of training data, two training data ZIP files will be available for download.
Importing Identification models
Follow the steps below to import your Identification model:
Go to Library > Models.
Click the name of your model to access the model management page.
From the Actions drop-down click Upload Model.
Once the model is uploaded, click Submit.
You can upload identification models only if their layouts are live. Make sure to match each model to its layout before uploading.
Importing training data
Using submission data in TDM
In v41.2, we’ve introduced a new setting called Send documents to Training Data Management for Identification and Classification models. This setting allows you to control whether submission data is used for model training. It is disabled by default and can be managed from the System Settings (Administration > System Settings).
Follow the steps below to import your training data:
After you’ve imported your model, open its details page and click Actions.
Click Upload training documents… in the drop-down list.
Click Upload Existing in the dialog box, and follow the instructions to complete the upload process.
Clicking Upload Existing allows you to upload training data for layouts that have been created in another instance.
Once you’re done, click Submit.
Only one training data bundle can be uploaded at a time.
Exporting Transcription / Finetuning models
You can export all finetuning models in a Transcription model, or you can download individual finetuning models.
Export all finetuning models in a Transcription model
To export all finetuning models in a Transcription model:
Go to Library > Models, and click on Transcription Models in the drop-down list at the top of the page.
In the Transcription Models table, click on the name of the transcription model whose fine-tuning models you want to download.
Click Download all models.
The models are downloaded as a ZIP file with the name confidence_thresholding_model_export.zip.
Export an individual finetuning model
To export a specific finetuning model:
Go to Library > Models, and then select Transcription Models in the drop-down list at the top of the page.
In the Transcription Models table, click on the name of the transcription model that contains the finetuning model you want to download.
Click on the tab that matches the type of fine-tuning model you want to download.
In the Available Models table, find the version of the model you want to download, and click Download Model.
The model is downloaded as a ZIP file with the name confidence_thresholding_model_export.zip
Importing Transcription models
Importing Transcription models from other versions
Transcription models trained on a different version than your current instance will be imported successfully, but will not appear in the model list. The list only includes models that match the current version of your instance.
Note that you can only import models created in v38 or later. For more information on model compatibility, see Compatibility Across Application, Flow, and Model Versions.
To import a model:
Go to Library > Models, and then click Transcription Models in the drop-down list at the top of the page.
In the Transcription Models table, find the transcription model you want to import a finetuning model for and click on its name.
Click Upload model.
You do not need to click the tab for the type of finetuning model you want to import. The system automatically detects the type of model during the import process.
Do one of the following:
Drag and drop the model’s ZIP file into the Import dialog box.
Click Choose Files, and find and open the model’s ZIP file on your machine.
Click Import.
Working with Transcription models
When importing or exporting Transcription models, keep the following factors in mind:
Manual vs. Automatic Training
Manual Training does not automatically deploy the newly trained Transcription model. Manual training allows you to:
Train the model in your production instance (where QA data resides).
Export the trained model, test it in a lower instance, and, if satisfied, re-import it into production for manual deployment.
Automatic Training, on the other hand, deploys the model immediately upon training. To validate the model before deployment, it’s recommended to disable automatic training.
QA Data Migration
It is not possible to migrate QA training data from production to a lower instance due to internal safeguards. Instead, you can:
Use the manual training method to train and validate models in your lower instance before deployment.
If you are unable to train a Transcription model, check your flows. Ensure that the Transcription Automation Training setting under the Semi-Structured Document Transcription settings type is enabled. To learn more about editing flow settings, see Document Processing Subflow Settings.
Transcription model training logic is based on settings from the last-edited flow, so it’s important to confirm this setting is enabled in all applicable flows.
Exporting and importing system settings
To move system settings between multiple instances that are on the same major version, follow the steps outlined in this section.
Exporting system settings
To export system settings:
Go to Administration > System Settings
Click Export at the top of the page.
Deselect the system settings that you do not want to export.
Click Download Settings.
The system settings are exported in a JSON file. You can then use this JSON file to import these system settings into another instance that uses the same major version of the application.
Importing system settings
To import system settings:
Go to Administration > System Settings.
Click Import at the top of the page
Drag and drop your settings file and click the Import button. You can also click Browse to find the settings file on your machine and open it.
Deselect the settings you do not want to import. All settings that you choose not to import will keep their current value.
Click Apply Changes now.
Exporting and importing permission groups
Exporting Permission Groups
You can use your custom permission groups in other instances. To do so, export the groups, then import their JSON files into any instances where you would like to use the permission groups.
To export permission groups:
Go to Users > Permission Groups, and select the checkboxes for the groups you want to export.
Click Actions, and then click Export.
The system creates a JSON file for each exported permission group, which is then downloaded to your machine. If you’ve exported multiple groups, the system creates a ZIP file containing a JSON file for each permission group.
Importing permission groups
To import a permission group:
Go to Users > Permission Groups.
Click Add Permission Group in the upper-right corner.
In the Add Permission Group dialog box, click the Upload Existing tab.
Do one of the following:
Drag and drop the permission group’s JSON file to the dialog box.
Click Choose File, and find and open the permission group’s JSON file on your machine.
Click Upload.
Best practices for assets migration
Migrate dependent components in the correct order:
Flows → Releases → Classification Models → Identification Models → Training Data
Disable Continuous Model Improvement.
Disable settings such as Continuous Field Locator model improvement and Continuous Classification Model Improvement to prevent migrated models from being retrained automatically.Learn more in Identification Settings.
Train models manually in a lower instance before migration.
Maintain high-quality training data.
Use validated training datasets when retraining models after migration.
Poor-quality annotations or QA data can negatively affect model performance. Review training data quality before reusing it in another instance. Learn more in our Model Maintenance section.
Retain a reliable and validated Dataset in a lower instance for model training.
Validate imported artifacts.
Verify that flows are associated with the correct releases.
Verify that models are associated with the expected releases, layouts, and training data.
Retain older instances until validation is complete.
Keep historical data accessible until the migration has been successfully validated.
After migration, validate model performance and automation rates before deprecating older instances. To learn more, see Monitoring Model Performance.