Import/Export options

When using the Import/Export functionality, we recommend the following:

  • Always have one source environment and one target environment.

  • Avoid manually creating entities in the target environment that duplicate entities that already exist in the source environment. This is to avoid conflicts caused by mismatched identifiers.

  • Apply changes to the source environment before creating the export package and importing it to the target environment.

  • Make sure that your configuration was pushed before executing an upgrade when exporting changes from a development or quality environment to a production environment. This is to avoid having your development or quality environment upgraded before your production environment when there are changes that have not been exported.

  • Complete a full export from the source environment and import the entire package to the target environment.

When exporting or importing a subset of the configuration, consider the following:

  • Portal pages - when you export portal pages include entity definitions, taxonomies, and publish definition configurations. A problem could occur if you export a portal page that references an entity definition that has not been exported.

  • Entity definitions - when you transfer entity definition changes, export the following:

    • Export profiles if changes have been made
    • Portal pages
    • Publish definition configurations
    • Taxonomies. If you added a new taxonomy definition, make sure to also export the taxonomies that already have values created.
    • Policies including security policies (and referenced entity definitions or taxonomies). For example, you may want a user group to access all assets linked to ProductLineToAsset that have the value of X.

    If you import a significant number of entity definitions that require re-indexing, the re-indexing could result in a large number of graph messages (for example, changing an asset property to include in the content).

  • State flows - when you export state flows, we recommend including:

    • Entity definitions. If state flows are enabled for a definition, also export the definitions.

    • Publish definition configurations - always export together with entity definitions.

    • Portal pages - state flow actions are most likely added when a new state flow is added.

    • Policies - policies and User-to-User-group assignments are typically updated when a state flow is defined. Be sure to include all taxonomies that are referenced by the policies.

    • Triggers - triggers are usually required to initiate a state flow only when a condition is met. Always include the trigger conditions in the export. Be sure to also include all scripts linked to the triggers.


With state flows, when the target environment has triggers enabled, this can result in the triggers firing if conditions are met while importing a package (particularly triggers related to creation and update). For example, you have a trigger on newly created or updated asset types. If your package imports a new asset type, your trigger, and its flow will execute.


Any entity referred in a portal page, and its components must be available in the target environment before the import.

Can we improve this article ? Provide feedback