locked
SharePoint Migration RRS feed

  • Question

  • Hi

    We currently have a standalone SharePoint Server using SQL express for a QA enviorment.  We have a prouction area with 2 Web Front Ends and a Search Index Server.

    The plan was to recreate all sites and document libraries from scratch in production. We are thinking it might be better to do some kind of migration from QA to the SharePoint web farm. The QA box and the SharePoint Farm are in two seperate Forests.

    Is there a way to safely migrate everything from our QA Box into Production. Would there be a major impact on permissions and accounts since we are moving to another forest?
    Wednesday, June 17, 2009 5:05 PM

Answers

All replies

  • can use 
    SharePoint Content Deployment Wizard

    You can define if you want to migrate content with permissions/account or not.

    Recomend make a test first, if everything goes well

    Hope this help...

    André Lage Microsoft SharePoint and CRM Consultant
    Blog:http://aaclage.blogspot.com
    Codeplex:http://spupload.codeplex.com/http://simplecamlsearch.codeplex.com/
    • Marked as answer by Lu Zou-MSFT Thursday, June 25, 2009 7:28 AM
    Wednesday, June 17, 2009 5:17 PM
  • So you seem to be talking about SharePoint on-premise to SharePoint Online migration.

    Import/Export characteristics

    Since the Content Migration API is used, imports/exports have the following characteristics:
    dependencies of selected content (e.g. referenced CSS files, master pages) are automatically included in the export - check 'Exclude dependencies of selected objects' to disable this
    all required content types, columns etc. are automatically included in the export
    in contrast to STSADM export, it is possible to retain GUIDs during deployment (where objects are not being reparented) - check 'Retain object IDs and locations' to enable this
    no filesystem files (assemblies, SharePoint Solutions/Features etc.) are deployed - these must already be present on the target for the import to succeed)
    the following content does not get captured by the Content Migration API - alerts, audit trail, change log history, recycle-bin items, workflow tasks/state

    Reparenting

    Reparenting of objects such as webs and lists is possible with the following usage on the import:

    - enter the URL for the target web in the 'Import web URL' textbox
    - ensure 'Retain object IDs and locations' is not checked

    Permissions

    The Content Migration API (PRIME) is used to package the content as a .cmp file, which can be copied to another
    server for import. The application MUST be run from the SharePoint server(s), and MUST be run under the context
    of an account which has appropriate SharePoint permissions - currently the way to specify an alternative user
    to the currently-logged on user is by using the 'Run as..' feature in Windows 2003 (right-click on the .exe and
    select 'Run as..').

    Wednesday, June 3, 2020 12:47 PM