Geek Answers Handbook

Best way to migrate site content to a new SharePoint site

My team is working on a project to migrate a .com site to SharePoint.

After all of our appearance elements, main pages, content types and page layouts are created, we need to actually "move" the actual site pages to SharePoint.

I am trying to come up with the most efficient way to do this. Our topology consists of a development and production environment. We plan to use SharePoint Content Deployment to populate Production from Authoring.

However, we obviously need to make some initial set of Authoring environments. I don’t want to use Content Deployment to populate Authoring from the development environment because I don’t want to create Authoring from the empty space definition first.

Here are the options I came up with, like some of the reviews that you think would be best:

  • Create site content in a development environment and use a tool like SPDeploy to transfer it to the development environment

  • Create content directly in Authoring

  • Use a method similar to how you can instantiate a list instance in a function. We created and filled all our content using functions

    • I'm not sure if this is really doable, but got the idea because I know that you can instantiate a list of elements when creating a list in a function. After all, our Pages library is a list of pages — however, there are several types of content.

Thanks for your suggestions!

+4
source share
3 answers

If it's just about file transfer, you can use the content transfer infrastructure. The main classes of this structure are the SPExport and SPImport classes in the Microsoft.SharePoint.Deployment namespace. You can export individual files to disk with fairly little code and import them again to a new location. Alternatively, try the SharePoint Content Deployment Wizard on CodePlex here: http://www.codeplex.com/SPDeploymentWizard . This will save you from coding.

+1
source

Backing up and restoring the database.

0
source

Can you explain why you do not want to use content deployment to create your original Authoring site? Why don't you want to start with a clean site definition? In any case, it will be overwritten during the deployment process. What about stsadm -export / -import?

Sorry, but I still do not understand the whole situation. You have a development environment (presumably where the structure is created, but not some content intended for production), a development environment (which I understand as a blocked environment in which content is entered and approved), and then a read-only read-only environment who approved the items. If so, I can say that I have a similar setup in one of my projects.

In my case, I initially developed the site structure in my dev environment, then backed up and restored to authoring and prod. Subsequent structural changes in both environments are manual. Building is structurally almost exactly the same as prod. Only security is different. Several times a day, content is deployed from authoring to prod. We make content changes directly to the development environment.

0
source

More articles:


All Articles