When you export assets, Informatica Intelligent Cloud Services creates an export ZIP file that contains the assets that you selected for export.
You can select individual assets to export, or you can select an entire project or folder. When you export a project or folder, the export file includes all of the assets in the project or folder.
To export an asset, you need the following privileges and permissions:
•Your user role must have privileges to export assets.
•You must have read permission on the asset.
Note: Informatica recommends that you include no more than 800 objects in an export file.
Make assets exportable
If you create APIs or policies starting from October 2025, the assets are automatically enabled for export. However, if you had created APIs or policies before October 2025, you will need to use the Make Exportable option to prepare and mark the assets ready for export or import.
You need to make the assets exportable first to ensure that assets and their dependent objects are properly prepared for a smooth and error-free export or import process.
Making design APIs exportable
You can refresh existing design APIs to make them export-ready without changing other properties. Starting October 2025, editing and saving an existing design API automatically prepares it for export. After you create and save an API, any non-exportable policy linked to that API is automatically synced and becomes export-ready.
Perform the following steps to make an API exportable:
1Open a design API.
2Click Make Exportable on the icon toolbar.
A message appears confirming that the API is made exportable.
3Alternatively, if you edit the design API properties and save the API, the API is automatically made exportable.
Making policies exportable
You can refresh existing policies to update their status as exportable without changing other properties. You can also edit and save existing policies to auto-update them to be export-ready.
Perform the following steps to make a policy exportable
1On the Policies page, click the Actions menu on the row of the selected policy, and then click Make Exportable.
A message appears confirming that the policy is made exportable.
2Alternatively, if you edit the policy properties and save the policy, the policy is automatically made exportable.
You can use the Make All Exportable option to make all the policies exportable in one action. This eliminates the need to mark each policy individually, saving you time when managing multiple policies in your organization.
Export files
The export file retains the file structure of the source organization's Explore page for projects, folders, and assets. The export file includes a spreadsheet that lists the objects within the file.
Object names
Each asset is contained in a ZIP file along with its associated metadata and JSON file. The zip file includes the asset name appended by the asset type.
Exporting assets
You can select a single asset, multiple assets, or a project to export.
You can select one or more assets within a folder. Or, select a project or folder to export all of its assets.
1On the Explore page, navigate to the assets that you want to export.
2Select the assets.
To export a single asset or project, select the asset or project.
To export multiple assets, select the check box to the left of each asset that you want to export. Or, select the check box for each project or folder that contains the assets that you want to export.
3From the selection menu, select Export.
4On the Export Assets page, change the job name or accept the default name.
5Select whether to include dependent objects for the assets.
Note: The Export Assets page lists the assets in the export operation and indicates the total number of assets to export. You can sort and filter the list.
6Click Export.
7To see the progress of the job, go to My Import/Export Logs page and click the Export tab.
Click the name of the log to open the log details page.
8To download the export file, click Download next to the export job on the My Import/Export Logs page.