- Publishing content from a development server to a staging server and from a staging server to a production server. You can manually trigger the publishing process or drive it with a scheduled job.
- Allowing end users to export any list and content from a site and import it manually to another site inside or outside of the original server farm.
- Enabling third-party content management or collaboration solutions to generate data into the published XML schema and use the import capability to migrate content into SharePoint Foundation.
- Selecting components from a Volume Shadow Copy Service (VSS) restore for import to a SharePoint Foundation Web site.
In short, by using the content migration APIs, you can transfer the right content from the right location at the proper time to the correct destination.
There are three ways you can invoke the content migration APIs.
- Windows PowerShell
- Content Migration object model
Sourse Site that will be exported...
Now for exporting the site, we have to use Export-SPWeb command in the PowerShell prompt.
Once the site is exported, we have to use Import-SPWeb from the PowerShell prompt.
After the successful import, the destination site will be replica of sourse site.
Destination site after Import using PowerShell