You can export and import website content and settings from one Xperience instance to another. You can use the import and export features to manually move websites or selected objects between development, testing and production (live) servers.
The export does not include the files of the 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).
See also: Deploying sites to a live server
Exporting between different Xperience versions
When transferring data via import packages, we strongly recommend using exactly the same version for all of your instances. Importing of packages between different versions is possible with the following limitations:
- You can import packages exported from older versions of Xperience, but the support only extends back to the previous major version. For example, only packages from Kentico 12 and Xperience 13 can be imported to Xperience 13.
- You CANNOT import packages from newer versions to older versions (including minor hotfix versions).
Export folder structure – learn how the folder structure of the Xperience web project is affected during export and import.
Export/import package directory browsing – protect your exported packages against file enumeration attacks.
Excluding files and folders from export – you can leave out specific files and folders from the export.
Importing a site or objects – import exported website packages or object packages.
Export and ID values
The system cannot ensure that pages and objects have the same ID values after being exported from one environment to another. However, the export process preserves GUID values. Use GUID fields if you need to identify pages or objects that have been transferred across multiple environments.
Was this page helpful?