In the lifetime of a SharePoint deployment, we need to restructure sites like:
- Copy one site to another parent
- Move one site to another parent
Surely there are PowerShell, STSADM, and Server Object Model ways of doing it. But here I describe the SharePoint Web Interface way of doing it.
The advantage is that we can do it without the help of SharePoint Administrator & Central Administration.
Content Database
Each site collection resides in a content database. In the case of a web application, there could be multiple content databases.
Copying Site
Now let us see how to copy a site from one location to another. Open your SharePoint site & choose "Site Actions" > "Site Settings".
Choose "Site Administration" > "Content and Structure". In the page that appears, choose the sub site & context menu, then "Copy item".
You will get the following dialog to choose the destination site.
We are copying the site from one parent to another parent.
Choose your Destination Parent & click the "Ok" button. Your copy operation should begin now.
Wait for a few minutes until the contents are copied. You can see the new site created.
You can try accessing it using the URL.
The site appears as in the following:
Moving Site
For moving a site, you can use the Move context menu item & then choose the destination parent site.
Note: If you cannot see the Site Content and Structure link then you need to activate the SharePoint Server Publishing Infrastructure feature from "Site Settings" > "Site Collection" command.![]()
References
http://bit.ly/102VB0C
Summary
In this article we have seen how to move/copy a site without using PowerShell.

Jean PaulPosted Feb 17, 2014, 11:52 AM
Thank You Kiran for the good words! Enjoy sharepoint > change the world > change your life :)
Kiran Kumar TalikotiPosted Feb 17, 2014, 4:32 AM
Thanks Jean For Sharing This Article :)
Jean PaulPosted May 19, 2013, 9:54 AM
Thank You Mahesh for the good words. Yes! You can move it with lot of data too.. The recommended data of a site collection content db should be less than 200 GB, in my experience admins keep it below 50 GB for making the operations smooth. I recommend you use Squadron to analyze the db size & do a move. Plus, if you are moving data then make sure your LIST GUID are retained/updated.
Mahesh BabuPosted May 19, 2013, 7:38 AM
Hi jean Paul, great post and everybody can understand easily... Can we use this way, if Site contains lot of data?