{"id":603,"date":"2010-03-03T20:30:00","date_gmt":"2010-03-03T20:30:00","guid":{"rendered":"https:\/\/brainlitter.itgroove.net\/2010\/03\/03\/how-to-save-an-existing-site-as-a-template-to-move-to-another-location-with-content-and-what-you-need-to-know\/"},"modified":"2010-03-03T20:30:00","modified_gmt":"2010-03-03T20:30:00","slug":"how-to-save-an-existing-site-as-a-template-to-move-to-another-location-with-content-and-what-you-need-to-know","status":"publish","type":"post","link":"https:\/\/regroove.ca\/brainlitter\/2010\/03\/03\/how-to-save-an-existing-site-as-a-template-to-move-to-another-location-with-content-and-what-you-need-to-know\/","title":{"rendered":"How to save an existing site, as a template, to move to another location (with content) and what you need to know"},"content":{"rendered":"
\n

Ok, this is something that comes along once in a while.<\/p>\n

Problem<\/h2>\n

Site placed in a location the client doesn’t like. While there are better ways (that preserve timestamps, etc.), they are complicated (STSADM) and time consuming (see here for more on STSADM Export\/Import – http:\/\/brainlitter.com\/archive\/2009\/05\/11\/how-to-backup-and-restore-migrate-a-single-sub-site-of-a-sharepoint-site-collection-using-stsadm-%e2%80%93o-export-and-import.aspx<\/a>)<\/p>\n

Solution<\/h2>\n

But if the site is small enough, you can simply ‘save as template’ the site and then create a new site, based on that template.<\/p>\n

What You Need to Know<\/h2>\n

This technique has the following limitations:<\/p>\n