---
title: "Export behavior"
slug: "export-behavior"
abstract: "Export packages as JSON files grouped by resource type, with options to filter by modification date and track progress."
---
# Export behavior

> [!note]
> To configure Content Hub, you must either be a superuser or have the necessary permissions granted to you through [user group policies](https://doc.sitecore.com/ch/en/users/content-hub/user-group-policies.html "User group policies").

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.

> [!warning]
> Export packages might include references to filters that can not be exported, such as filters based on `M.Portal.Version` or saved searches. If these filters are referenced by other components, such as page or search components, remove the filters before the export; otherwise, the export will fail or complete with missing dependency errors.

When exporting [pages](https://doc.sitecore.com/ch/en/users/content-hub/pages.html "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.

> [!warning]
> 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.