Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.
Please consider addressing the following when creating your topic:
I am trying to export the specific objects through one tenant via Visual Studio Code. It is exported successfully but when trying to import the same file that got generated, import is not working in the different tenant.
If anyone have faced this issue or know how to do the export and import, please let me know.
What’s happening is the export contains tenant-specific IDs and references (like sourceId, owner, identityProfile, etc.). In the target tenant those don’t exist, so the import fails or does nothing.
Quick fix:
Remove or update IDs in the JSON
Make sure dependencies (sources, identity profiles, transforms) exist in the target tenant
Then re-import
So it’s more of a mapping/dependency issue, not a permission difference between tenants.
Config Hub is a pretty powerful tool for moving objects as well. You’re able to customize object mappings in cases where maybe your source names are different, and it’ll take care of translating owner ID’s and most other unique identifiers automatically between environments.
@Jadhikary - Jeebina - There are two strategies involves to manage these tenant specific identifiers and dependencies.
SailPoint Configuration Hub (Recommended) - Configuration Hub is the official and recommended tool for promoting configurations between different Identity Security Cloud tenants (e.g., from Development to QA to Production). It is designed to handle the complexities of cross-tenant object migration, including the translation of tenant-specific IDs and the management of dependencies.
Manual Exported JSON (Alternative for Specific Cases) - Export Objects using the VS Code extension to export the desired objects from the source tenant.
If you adopting Configuration Hub for the migration process, will reduces errors, and ensures the integrity of your Identity Security Cloud environment across its lifecycle stages.
Configuration hub is the best option to import from one tenant and to export to another.
In the first tenant, you have to select the objects that needs to be imported, and in second tenant create draft for those objects and replace the id’s according to the tenant and then deploy. This is easy to import and export.