Help & Documentation
Open Support Ticket

Exporting Objects with Import/Export Utility

It is possible to migrate Objects from one instance to another using Import/Export Utility. Once Elements in staging environments are ready for production you can export/

Export (dump) procedure exports an Object from a source instance as a .tar.gz file. All export changes are stored in Import/Export History section.

Additionally, Import/Export Utility can work in conjunction with Export Locations allowing for Utilities > Import/Export

Select [+New Custom Export]

2. Select a Metadata Type to Be Exported

This example shows adding a Portal Page, but the process is intuitive and essentially the same for other types.

NOTE:

  • Dependent Portal Page Layouts, Templates, and Assets will be added to Export automatically.
  • For Portal Page code iteration, it is recommended to upload new Portal Page Assets rather than

    Here’s the uniqueness checking algorithm:

    1. The Utility checks the source_name and source_idof all Elements on the target system 
      • If there is a match, that means that the Element from the source system was already migrated to the target system once in the past, and it needs to be updated. The Utility will proceed to the next step
      • If there’s none, it means the new Element has to be created. The Utility will proceed to the next step
    2. The Utility checks all existing Elements on the target system to see if there is a match by name, type or segment_id
      • If there’s no match, the Utility updates the Element or creates a new one
      • If there is a match in all three parameters, the Element from the source system won’t be migrated and the error message will occur

    The Migration Utility also ensures the uniqueness of Portal Pages. It checks name, internal_name, and URL of every Portal Page existing on the target system. If all three match, the Portal Page from the source system won’t be migrated and the error message appears.