We have a site configured as http://www.stage.abc.com . This site is built using custom site definitions and have lot of features attached to it. All are Publishing based site

Now we need to create a new stage copy as http://www.stage.bac.com with the same data and the

reason for this is we are planning for a rebrand for this site with alterations in content What is the best way to accomplish this? Later we will configure a content deployment from this site to the new webapplication created in Production

3 Answers 3


Backup/restore process should do the the thing. But it's necessary to perform restore to a separate content database. SharePoint doesn't allow two site collections with the same ID in one database.


I think the best and simplest way is to create site collection backup and restore it on new url. It even will deploy libraries to GAC if needed.

  • What will happen to the wsp references? will that reference be added to the newly created site?
    – Thomson
    Commented Feb 8, 2012 at 5:29
  • I don't know in details but I do it myself. I created a backup of site collection with some custom field types in lists and Visual Studio workflows in order to create second test environment. It works great although I had to redeploy project on new site collection via Visual Studio automatic deployment - something was broken and I'm not sure what it was. But the whole concept works quickly and fine from my experience.
    – Alex Boev
    Commented Feb 8, 2012 at 6:03
  • WSP Reference are based on web app. If they are not referenced you can activate it from the solution management.
    – user994521
    Commented Jul 16, 2012 at 6:46

You might want to try exporting the entire site then importing the site into the new url. One of the reasons for doing this is GUID reference. I do not think the GUID references will come across the way you need them to with the backup/restore method. When you extract the site in its entirty, the GUIDs in the Requirements.xml file will be the same as your site along with all of your list, so nothing should break as far as list go. try running this script to export:

stsadm -o export -version 1 -filename yourfilename -includeusersecurity -url https://whereyouwantit -nofilecompression

the -nofilecompression will allow you to go into each xml file and make sure you GUIDs match along with the ability to quickly add or remove groups, users, or anything else you might want to change on the fly then run this to import:

stsadm -o import -updateversions 2 -filename yourfilename -includeusersecurity -url yournewurl -nofilecompression

give this a try.

  • 1
    instead I would prefer stsadm -o backup command with site collection as the export command is not suitable for site collection.
    – user994521
    Commented Jul 16, 2012 at 6:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.