--- title: Exporting sites related: - https://docs.kentico.com/13/deploying-websites/exporting-and-importing-sites/importing-a-site-or-objects.md - https://docs.kentico.com/13/deploying-websites/content-staging.md --- > Agent instructions: > **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown. > > - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version. > - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt). The system allows you to export entire websites, including settings and related objects (such as page types, workflows, etc.), into a single file archive. You can then import the archive on other Xperience instances (of the same version or up to one major version newer). The export does NOT include the files of the separate MVC project that handles the presentation of the the live site. You can use the export to transfer the content and objects stored for the site in the Xperience database, but you need to deploy the related MVC project manually (using FTP, the Visual Studio Publish function, or another deployment option). ## Exporting a site 1. Open the **Sites** application. 2. Click **Export site** () for the site you want to export. The Export wizard starts. 3. Fill in the name of the export package and choose the object pre-selection type: | Option | Description | | --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | File name | Sets the name of the export package. The wizard creates a zip file containing the export data in the _\~/CMSSiteUtils/Export_ folder. | | Preselect all objects | Preselects all objects related to the site. | | Preselect objects changed after specific date | Preselects all objects changed after the specified date. | | Use previous export settings | Preselects objects based on the settings of a previous export.
**Tip**: To clear the history of previous exports, open the **Sites** applications, click **View export history** among the header actions and delete the items on the **History** tab. Deleting export history items does not remove the corresponding packages from the file system. | Select an option and click **Next**. 4. Select which objects you want to export. The tree separates objects into categories according to the related functionality. These reflect the product categories to which the objects are related. The **Website** category contains objects related to the selected website. The **Global objects** category contains global objects that can be used by all sites. Selecting a category opens a set of check boxes in the right part of the screen, allowing you to select which objects will be exported. > **Note:** **Note**: The _Pages_ of a website may require other objects to work correctly (for example the _Page types_ of the site's pages). To ensure that the exported pages can be successfully imported, you need to include the required objects into the package. > **Info:** See the [Export - Object selection settings](#export---object-selection-settings) section for details. ![Selecting objects for export](https://docs.kentico.com/docsassets/13/exporting-sites/Export_Object_Selection.png "Selecting objects for export") 5. After making all required selections, click **Next** to proceed. A log appears, showing you the export progress. You can abort the export by clicking **Cancel** at any time. When the export finishes, a message appears above the log, showing the file system path to the exported file along with a download link. 6. (Optional) Click the **download link** at the top of the the log if you wish to immediately download the export package. 7. Click **Finish**. The system returns you to the **Sites** application. You can now copy the exported package into the **\~/CMSSiteUtils/Import** folder of the target installation of Xperience, and use the **Import site or objects** wizard described in [Importing a site or objects](https://docs.kentico.com/13/deploying-websites/exporting-and-importing-sites/importing-a-site-or-objects.md). ## Export - Object selection settings The following options are available in the **Object selection** step of the Export wizard. Select the root of the tree (_All objects_) to access the following general export settings: | Global selection | | | ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Load default selection | Preselects all objects based on your selection in Step 1 of the export wizard. | | Select all objects | Selects all available objects. | | Deselect all objects | Unselects all objects. | | Export settings | | | Export tasks | If enabled, delete tasks (incremental deployment) will be included in the package. | | Export files | Some database objects are linked with physical files stored on the file system inside the web project. If you select this option, such files will be exported along with the corresponding database objects. | | Export global folders | If enabled, all files under the following folders will be added to the export package:
\~/Old\_App\_Code/Global/
\~/CMSGlobalFiles/
\~/CMSScripts/Custom/ | | Export custom assembly files | If enabled, custom assembly files (dlls) that store the classes of certain custom objects will be exported together with the given objects. Applies to translation services, payment options, integration connectors, scheduled tasks, advanced workflow actions, marketing automation actions and smart search analyzers.
The system considers assemblies as custom if their name does not start with the _CMS._ prefix. | | Export site folders | This option is only available when exporting websites, not just separate objects. If enabled, all files under the following site-related folders will be added to the export package:
\~/App\_Data//
\~//
\~/Old\_App\_Code// | The following categories contain extra options to be set: | Custom tables | | | ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Export custom table data | If selected, custom table records (the actual data stored in the tables) will be exported along with the selected custom tables. | | Pages | | | Export pages | If selected, pages will be exported. | | Export page histories | If selected, histories of all exported pages will be exported. | | Export page relationships | If selected, relationships of all exported pages will be exported. | | Export page level permissions | If selected, page security settings made in the **Pages** application will be exported. | | Forms | | | Export forms data | If selected, stored forms data will be exported together with the exported forms. | | Export physical files | If selected, physical files saved within form records (if there are some) will also be exported. | | Media libraries | | | Export media files | If selected, media files stored in the database will be exported. | | Export physical files | If selected, physical media files stored in the file system will be exported. This option is not selected by default as it may result in extremely large export packages. Instead, it is recommended to transfer these physical files manually. | | Modules | | | Seal the selected modules | If selected, the system seals the exported modules. When the modules are [imported](https://docs.kentico.com/13/deploying-websites/exporting-and-importing-sites/importing-a-site-or-objects.md) to another instance of Xperience, they will not be in development mode (i.e. it is not possible to edit the module's properties, or create new classes, UI elements, permissions and settings).
You cannot export a module again from instances where it is sealed. | > **Note:** If you have the **Log export tasks** setting enabled in **Settings -> Versioning & Synchronization -> Staging**, a list of object deletion tasks may be displayed at the bottom of the list. If you leave the boxes selected, the objects will be deleted after you import the package on the target server.