AI agents: the content index is at /llms.txt. Every page is also available as Markdown — send the request header Accept: text/markdown, or append .md to the page URL.
Xperience Docs

Cookie consent

We use necessary cookies (opens in a new tab) to run our website and improve your experience while browsing. Additional cookies are only used with your consent. You may revoke your consent on the Cookies Policy (opens in a new tab) page or in your browser at any time.

Configure (opens in a new tab)
  • Documentation
    InstallationUsing the Xperience interfaceDeveloping websitesConfiguring XperienceManaging usersSecuring websitesDeploying websitesManaging website contentMultilingual websitesMacro expressionsExternal utilitiesIntegrating 3rd party systemsCustom developmentE-commerce featuresOn-line marketing featuresRelease notes - Xperience 13Xperience terminology glossary
  • Tutorial
    Using the Xperience interfaceDeveloper tutorialBusiness tutorialResource hub for marketers
  • API Examples
    ConfigurationContent managementDevelopmentE-commerceOn-line marketingSocial media
  1. Home
  2. Deploying websites
  3. Exporting and importing sites
  4. Export folder structure

Export folder structure


Was this page helpful?

Send us feedback Go back to top
  • Community Questions & Answers (opens in a new tab)
  • Contact support (opens in a new tab)

Xperience instances organize files used by the administration interface within the CMS folder.

The following list describes the main folders and how they are affected during the import and export process.

Color

Meaning

red

System folders. Do not make any changes or place your files here unless you want to modify the administration interface.

blue

Folders for custom files, part of the export package.

green

Folders for custom files, part of the export package. You may need to create these folders manually.

black

Service folders (import files, import/export).

  • Admin

  • App_Data

    • CMSModules\<module_name> (folders of custom modules)
  • CMSAdminControls

  • CMSEdit

  • CMSFormControls (all form controls selected in the export process are exported with any site)

  • CMSGlobalFiles (exports with any site if the Export global folders option is selected during the export process)

  • CMSImportFiles

  • CMSInstall

  • CMSMasterPages

  • CMSMessages

  • CMSModules

    • <module name> (folders of custom modules)
  • CMSPages

  • CMSResources

  • CMSScripts (CMSScripts\Custom is a folder intended to hold custom JavaScript files for the administration interface, and is part of the export package)

  • CMSSiteUtils

  • CMSVirtualFIles (stores virtual objects when using deployment mode)

  • CMSWebParts (all web parts selected in the export process are exported with any site; if the web part uses additional files, they must be placed in a folder in format <webpartCodeName>_files; files that are not registered as web parts are not included in the export package)

  • <site code name> (exports with the given site, needs to be created manually or may be created automatically when storing files on the disk; the folder is exported if the Export site folders option is selected during the export process)

    • Files (the default folder for storing files if the system is configured for saving files on the disk)
  • Old_App_Code

    • CMSModules\<module_name> (folders of custom modules)
    • Global (exports with any site, if the Export global folders option is selected during the export process)
    • <site code name> (exports with the given site if the Export site folders option is selected during the export process)
  • Old_App_WebReferences