Microsoft tells us (yet again) that no custom code is needed in the new version of Sharepoint. However I'm curious how to export Web Application(s) | Site Collection(s) and Site(s) structure including navigation and style to a production site? Is that even possible, and if so what steps are required?


There are a few things you can try like:

  1. Export/Import
  2. Content deployment
  3. Cross-site publishing (new)

If you're using SharePoint 2013, be sure to check out cross site publishing!

In any case, you'll still have to deploy your customizations to both sides.

| improve this answer | |
  • Thanks for your reply! Isn't content deployment really a deploy of content and not only structure? Is there a risk when using content deployment that I delete existing content on the production site? – Benny Skogberg Jan 15 '13 at 10:37
  • When using content deployment, you can't touch anything in production anymore or you'll run into problems. This is best suited for staging > production publishing scenario's. What are your requirements? – Thomas Vochten Jan 15 '13 at 12:01
  • Requirements are kleeping content as is on the target production site and deploy changes to structure such as new sites/site collections - changes to navigation and overall structure of SharePoint instances, without the use of custom code (.wsp projects). – Benny Skogberg Jan 15 '13 at 12:08
  • Content deployment uses the export/import API's that require a blank starting site. No manual modifications in the target site are supported :/ I think you're looking at custom code or 3rd party tools here. – Thomas Vochten Jan 15 '13 at 12:24
  • I would say that Cross-site publishing solves the problem, where you can have an OOTB Authoring site. Thanks for the link! – Benny Skogberg Jan 15 '13 at 18:48

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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