By continuing to use this site, you agree to the storing of first- and third-party cookies on your device to enhance site navigation; analyze site, product, and service usage; and assist in our marketing and promotional efforts. Cookie Policy

Skip to Content


Cloning creates a copy of one of your existing sites that can then be modified without affecting the original. This includes all designs and resources files. If you need to create a new site, it is often easier to clone an existing one and then change it as needed, rather than creating a brand-new site and building it from the ground up.

Determine whether just the site record (the staging server information and all site settings) or both the site record and the site staging files will be cloned. If you are trying to duplicate an existing site with all its resources and templates, select the "Include Staging Files" checkbox. 

The following features are cloned with a site:

FeatureClone Site RecordClone Staging FilesNotes
Staging Server FilesNoYesEverything under Content > Pages.
Site SettingsYesYesWith the exception of those that need to be reconfigured for the new site.
Production Server FilesNoNo 
Binary FilesNoYes, if binary management is enabledIf the original site has binary management on and the clone doesn't, binary files are still copied to staging.
Dependency TagsNoNoThe site files are cloned, the dependency tags for the site are reverted, and then the site is rescanned, producing new dependency tags.
Recycle Bin LocationYesYes 
Recycle Bin ContentsNoNo 
LDP RegistrationNoNo 
RSS FeedsNoYes 
RSS Feed AssignmentsNoYes 
RSS Feed XMLsNoNo 
RSS GroupsNoYes 
RSS ItemsNoYes 
Snippets and Snippet CategoriesNoYesIf the snippet isn't already available in all sites, then the newly-cloned snippet is added to the list of sites that can access the snippet. Snippets already available account-wide aren't cloned.
AssetsNoNoAssets don't need to be cloned because they're available site-wide unless otherwise restricted. Any pages subscribing to assets remain subscribed to the original asset.
Access Settings (Pages and Folders)NoYes 
Access Settings (all others)NoNo 
ComponentsNoNoComponents don't need to be cloned because they're available site-wide unless otherwise restricted. Any component instances on pages are cloned with those pages and subscribe to the original component. 
Directory VariablesNoYes 
Find and Replace "Last Replace" ResultsNoYes 
File Status (Checked Out, Pending Approval, etc.)NoNo 
Template GroupsNoYes 
Facebook PagesNoNo 
Twitter AccountsNoNo 
Default Tweet/Wall PostYesYes 

Account-wide features such as users, groups, toolbars, etc. don't need to be cloned, as they are available to all sites. Gadgets with site-specific information won't include the old site's history when viewed on the new site.

How ToLink to this section

The length of time required to clone site files depends on the size of the site in terms of number of files and file sizes. A high number of files, particularly large media files, can take a considerable amount of time to clone.

Cloning a site with copying files should only be done when all users are logged out, to prevent them editing files during the site clone and potentially causing errors or discrepancies. To clone a site:

  1. Navigate to Setup > Sites.
    • If you are cloning to a site that is a subfolder of the original site, then revert the original site, so that the cloned links point to the new site.
  2. Click the More Actions More Actions menu menu for the site.
  3. Click Site > Clone.
  4. Type a unique site name.
  5. Select the "Include Staging Files" checkbox to duplicate the existing site.
  6. Fill out the site settings as necessary.
    • FTP Root, FTP Home (optional), and HTTP Root must form a unique combination.
    • If FTP Root is different from the default of the cloned site (i.e., public_html) and not using local templates, then the path for templates needs to match. For example, if FTP Root is /public_html/art then the template folder would be /public_html/art/_resources/ou/templates.
  7. Click Create.

Once the site is cloned, take these additional steps should be taken before going live.

  • Build the search index in the site settings.
  • Publish the site.
  • Initialize the DirectEdit button.
  • Review any site access settings.
  • Fix any internal hard-coded URLs pointing to the old domain name, if necessary. Find and replace can be used. Similarly, if the new site is a subfolder of the old one, then paths should be updated as necessary.

Dependency ManagerLink to this section

Whether or not dependency manager is enabled during the cloning process, for both the source site and the clone site, has differing effects on the links in the cloned site, should files be copied over. There are four possible scenarios:


Source Site
Dependency Manager On

Source Site
Dependency Manager Off
Clone Site
Dependency Manager On

All dependency tags point to clone.

Dependency tags may or may not point to the clone.
Clone Site
Dependency Manager Off
No dependency tags. Any dependency tags on the source site that existed before dependency manager was turned off are copied over and point to the source site.

Any dependency tags in the source site that point to locations other than the source continue to point to the same location in the clone.

If binary management is not turned on, and all links to binary files point to the production server, then those links on the clone site need to be updated via find and replace.