- Release Notes
- Getting started
- Notifications
- Projects
- Datasets
- Data Labeling
- ML packages
- About ML packages
- Upload file
- Using out of the box packages
- Importing and exporting ML packages
- Managing ML packages
- Out of the box packages
- Pipelines
- ML Skills
- ML Logs
- Document UnderstandingTM in AI Center
- AI Center API
- Licensing
- AI Solutions Templates
- How to
- Basic Troubleshooting Guide
Importing and exporting ML packages
You can move your ML models when migrating between tenants or when moving from one account to another.
In order to do this, you first need to download the package you want to migrate and import it into the new environment.
You can export an already created package and import it in a different or the same environment.
Follow these steps to download an already created package:
- In the ML Packages page, select an already created package from the list.
- In the Version tab, click on the ⁝ icon of the package.
- Click Download.
After clicking Download, two files will be downloaded:
- A
zipfile containing the package - A
jsonfile containing the package metadata, such as name, version, and other information. This information is needed to map the downloaded package to the right one in the new environment.
Follow these steps to upload a package exported from UiPath® AI Center:
- In the ML Packages page, click the Import ML Package button. The Import new package page is displayed.
- In the Upload package field, add the
zipfile downloaded using the Downloading ML Packages procedure. - In the Upload metadata json field, add the
jsonfile downloaded using the procedure above. - Click Create.
Private packages
- The imported package will have the same name as in the export environment, taken from the metadata file. If a package with
the same name already exists, the
versionfield from the metadata will be checked next. If the version is the same, a new minor version will be created. For example, if you import a package namedNew Package, version7, and you already have a package with the same name, but version7.3exists, the new imported package will be version7.4. If there is no version, the created package will have the next available major version. - If the name from the imported package metadata does not exist in the destination environment, the new package name is created in the destination environment.
Public packages
- The imported package will have the same name as in the export environment, taken from the metadata file. If a package with
the same name already exists, the
sourcePackageVersionfield from the metadata will be checked next for thesourcePackageVersionin the destination environment. After this, the next minor version will be uploaded. Make sure to either change the version in the destination environment, or change thesourcePackageVersionfield in the metadata file to the available version in the destination environment. -
If the name from the imported package metadata does not exist in the destination environment, the new package name is created in the destination environment.
Note:For the moment there are currently some limitations when importing a package from a different environment:
- In case of private packages, if the major version of the imported package is different than the already existing one, an error is displayed.
