---
title: "Contents of exported packages"
slug: "contents-of-exported-packages"
abstract: "Overview of the contents of export packages."
---
# Contents of exported packages

Exporting any or all of the available data sets, also known as targets, creates a download order that packages the selected items into a ZIP file. This package contains a [meta file](https://doc.sitecore.com/ch/en/users/content-hub/contents-of-exported-packages.html#meta-file), an [environment profile](https://doc.sitecore.com/ch/en/users/content-hub/contents-of-exported-packages.html#environment-profile) file, and a separate folder for each target.

> [!note]
> An export package cannot include system-owned settings.

> [!warning]
> Do not manually edit, move, or delete folders in import or export packages as modifying the package structure will cause failures. If you do encounter a problem after importing a modified package, we recommend you export the package again and then re-import it without any modifications.

## Meta file

The **meta** file contains the information required to import the package, namely:

- The version of the export instance.
- The name of the user who created the export package.
- A list of all items exported, grouped by target.
- The date the exported targets were last modified.

<details>
<summary>Sample meta file</summary>

```json
{
  "Version": "3.0.0",
  "MVersion": null,
  "User": "Administrator",
  "Source": "<instance identifier>",
  "Data": {
    "since": null,
    "items": [
      "copy_profiles",
      "schema",
      "export_profiles",
      "media_processing_sets",
      "option_lists",
      "policies",
      "portal_pages",
      "publishdefinitionconfigurations",
      "rendition_links",
      "scripts",
      "settings",
      "state_flows",
      "taxonomies",
      "transformations",
      "triggers",
      "actions"
    ],
    "requested_items": [
      "copy_profiles",
      "schema",
      "export_profiles",
      "media_processing_sets",
      "option_lists",
      "policies",
      "portal_pages",
      "publishdefinitionconfigurations",
      "rendition_links",
      "scripts",
      "settings",
      "state_flows",
      "taxonomies",
      "transformations",
      "triggers"
    ]
  },
  "include_system_owned": false,
  "StateFlowsSetting": null,
  "engine_version": "V2",
  "digest": "c3178a7b1e8b966139aa2896195e8abd61d5672325c12fa33c54a2df79909d0c"
}
```

</details>

## Environment profile

You can also include a file named **EnvironmentProfile.json** in an export package. This contains generic values that you can configure based on the target environment, such as the required authentication. This makes it simple to configure packages for different environments.

The **EnvironmentProfile.json** file must be placed in the package root, along with the **meta** file.

> [!note]
> The **EnvironmentProfile.json** file is only supported in the legacy version (V1) of the export package.

<details>
<summary>Sample profile content</summary>

```json
{
  "key1": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress",
  "key2": {
    "Key": "aKey",
    "Secret": "secret"
  },
  "key3": 5,
  "key4": true
}

```

</details>

<details>
<summary>Sample resource file</summary>

```json
{
 "version": "1.0.0",
 "data": {
  "properties": {
   "M.Setting.Name": "Authentication",
   "M.Setting.Value": {
    "UsernameClaimType": ##{key1}##,
    "EmailClaimType": ##{key1}##,
    "ReCaptcha": ##{key2}##,
    "MinutesToLockout": ##{key3}##,
    "EnableRegister": ##{key4}##,
   }
  }
}

```

The template is in the form of `##{key}##`, where `key` depends on the profile values.

</details>