Requirements and restrictions

Required role

You need Admin or Editor role in the project to export project assets.

Restrictions

• You cannot export assets larger than 500 MB.

• Project name, description, tags, and members are not exported.

• You cannot export job run metadata. Job run information is not available after you import.

• If your project is marked as sensitive, you can't export data assets, connections or connected data from the project.

• Be mindful when selecting assets to always also include the dependencies of those assets. Dependencies might include the data assets or connections for a data flow, a notebook, connected data, or jobs. There is no check for dependencies. If you don't include the dependencies, subsequent project imports do not work. For example, if you export a tuned prompt template asset from a space and import it into a new space, only the prompt template asset is moved to the new space. You must explicitly export the associated tuned model as well as the tuned prompt template to successfully deploy the prompt.

• You can only export and share assets across projects created in watsonx.ai. You can't export project assets from Cloud Pak for Data as a Service and import it into watsonx.ai, or the other way around. You can however, move projects between Cloud Pak for Data as a Service and watsonx.ai. See Switching the platform for a project.

• Exporting project assets from one region and importing the assets to a project or space in another region can result in an error creating the assets. The error message An unexpected response was returned when creating asset is a symptom of this restriction.

• Exporting project assets is not available for all watsonx.ai Studio plans. See watsonx.ai Studio plans.

Exporting project assets to desktop

Exporting project assets packs what you select into a single ZIP file that can be shared like any other file.

To export project assets to desktop:

1. Open the project you want to export assets from.

2. Check whether the assets that you include in your export, for example notebooks or connections, don't contain credentials or other sensitive information that you don't want to share. You should remove this information before you begin the export. Only private connection credentials are removed.

3. Optional. Add information to the readme on the Overview page of your project about the assets that you include in the export. For example, you can give a brief description of the analytics use case of the added assets and the data analysis methods that are used.

4. Click the Export icon from the project toolbar.

5. Select the assets to add. You can filter by asset type or customize the project export settings by selecting preferences (the settings icon to the right of the window title) which are applied each time you export the project.

6. Optional: Change the name of the project export file.

7. Supply a password if you want to export connections that have shared credentials. Note that this password must be provided to decrypt these credentials on project import.

8. Click Export. Do not leave the page while the export is running.

   When you export to desktop, the file is saved to the Downloads folder by default. If a ZIP file with the same name already exists, the existing file isn't overwritten.

   Ensure that your browser settings download the ZIP file to the desktop as a .zip file and not as a folder. Compressing this folder to enable project import leads to an error. Note also that you cannot manually add other assets to an exported project ZIP file on your desktop.

   The status of a project export is tracked on the project's Overview page.

Learn more

• Administering a project
• Importing a project

Parent topic: Administering projects