You can import all of the assets in an export file or select the assets that you want to import.
When you import assets, you specify the following information:
The assets in the export file that you want to import and the projects in which to import them.
Whether to overwrite assets in the target project with assets in the export file when there is a name conflict.
The connections and runtime environments to use for the imported assets.
Whether to publish taskflows when you import them.
To import an asset, you need the following privileges and permissions:
Your user role must have privileges to import assets.
If you import an asset into the target project as a new asset, you must have create, update, and read permissions on the asset.
If you overwrite an asset in the target project, you must have update and read permissions on the asset.
Additionally, to overwrite a source-controlled asset in the target project, you must have the asset checked out.
The target organization must have all of the required licenses for the assets being imported. For example, to import a
task, the target organization must have all of the licenses required for the
task. This includes the licenses required for the mapping on which the
task is based.
page lists the assets that are in the export file. You can select which assets you want to import, and then specify which project to import the assets to. You can accept the default project, which is the same project name as the source project, or you can select a different project. If the project does not exist in the target organization,