Export a package
To configure Content Hub, you must either be a superuser or have the necessary permissions granted to you through user group policies.
Exporting a package lets you move a setup from one environment to another, back up your configuration, or share a solution with your team. The export bundles the items you choose into a single file that can be imported elsewhere, keeping related pieces together so they work the same after import. Along with the selected data, the exported package contains a meta file and an environment profile.
The following entity definitions are not included in the export package:
-
AUTOMATION.SM.Definitions.State.DefinitionName -
AUTOMATION.SM.Definitions.StateMachine.DefinitionName -
CHILI.ChiliPublicationDefinition.DefinitionName -
DRM.Contract.DefinitionName -
PROCESSING.AgentDefinition.DefinitionName -
PROJECT.BlockCollection.DefinitionName -
PROJECT.Task.DefinitionName -
UserDefinition.UserDefinitionName
To export a package:
-
On the menu bar, click Manage
. -
On the Manage page, click Import/Export.
-
On the Import/Export page, in the Export section, select the items you want to include in your export package.
NoteExporting Policies includes only user group policies that have configured rules, member security, or privileges. It does not export user groups.
-
If you only want to include items that were modified after a specific date and time, click the calendar icon. Then, use the date picker to select a date, and optionally click the clock icon to specify a UTC time.
-
Click Export. This generates a download order that you can download immediately or share via email.
You can see the progress of any active exports either on the Current activity tab of the Stats page, which you can access from the Manage page, or on the Recent processes page. An export is considered healthy if the majority of its finished jobs have completed successfully.
Export behavior
Files are not grouped by export type, such as portal_pages, but by resource type. Each folder contains resources as individual JSON files, clearly named using their unique name or identifier.
When exporting pages, the Modified since filter will also consider the components related to that page. If no components were modified since the specified date, the Related property in the JSON file for the exported page will be empty.
Exported scripts are published exactly as they were in the source tenant, with all linked actions and triggers intact. Unchanged scripts are skipped from export to keep the packages cleaner.
Do not modify exported files, because this can lead to unexpected results. We strongly recommend testing all your data packages in a sandbox or development environment before using them in production.