How to get started with XPlica Quick Content Migration?

In order to migrate the contents successfully from one SharePoint environment to another SharePoint environment using XPlica Quick Content Migration Task Options, you need to ensure the following things before commencing the migration process:

  1. XPlica Server Agent: This tool should run in the remote servers (both source and destination with the specified port numbers) through out the migration process. The steps to run the XPlica Server Agent is described here.
     
  2. Temp Storage Location: This location should be a common network share to the following components of XPlica:

    a. XPlica - The user who is running the XPlica in the client side should have the rights to read and write in the 'temp storage' location.

    b. XPlica Server Agent (Source) - The credentials you are providing to connect the source SharePoint should also have the rights to read and write in the temp storage location.

    c. XPlica Server Agent (Destination) - The credentials you are providing to connect the destination SharePoint should also have the rights to read and write in the temp storage location. 
The XPlica Quick Migration task options are: 
  • Site Collections: This task type allows you to create a task to migrate site collections from one SharePoint location to another SharePoint location as specified in the batch descriptor file. In order to migrate site collections, we request you to create an empty site collection (not blank site, empty site collection differs from blank site) in the destination SharePoint environments. Steps to migrate site collection using XPlica Quick Content Migration task type. 

  • Webs: This task type allows you to create a task to migrate site or sub-web from one SharePoint location to another SharePoint location as specified in the batch descriptor file.  You are not required to create an empty site in the destination SharePoint environment like site collections task type.  Steps to migrate site or sub-web using XPlica Quick Content Migration task type.

  • Lists/libraries: This task type allows you to create a task to migrate list/library from one SharePoint site to another SharePoint site specified in the batch descriptor file. You are not required to create any destination list/library. Steps to migrate list/library using XPlica Quick Content Migration task type.

  • Folders: This task type allows you to create a task to migrate folder from one SharePoint location (library/list) to another SharePoint location (library/list) as specified in the batch descriptor file(Steps).

Requirements for successful migration: 

·    Ensure that sufficient disk space is available in destination SharePoint content database and temp storage location.

·    Use an empty site collection as the destination for migrating Site Collection task type. 

·    Install all required features, assemblies used in source site on the destination server to work those features properly.

·    Required Language Packs need to be available in destination.

·    Ensure that quick migration tasks are not running parallel.

·    Ensure that all feature definitions of features activated on the site collection exist on the source server.

·    Ensure that the ‘XPlica Client’ and ‘XPlica Server Agent’ which is deployed in target servers is running with the same ports before starting migration. Also ensure that these ports are configured in windows firewall in respective servers.

·    Also ensure that  ‘XPlica Client’ and the user accounts (Credentials) you are specifying to perform migration are having the rights to access the ‘Temp Storage Location’.

Limitations of XPlica Quick Content Migration tasks: 

By using XPlica Quick Content Migration Tasks, you cannot migrate the following:
  • Workflows (Definitions).
  • Workflow State & Tasks.
  • Workflow History.
  • Check in/check out state.
  • System dates and system users for folders (Created date, modified date, created by and modified by) when migrating lists and folders.
  • Audit logs.
  • Usage Logs.
  • Site collection settings (Site Collection Ownership, Quota, email notification settings).
  • Personalized views.
  • Alerts.
  • Recycle bin state/items including admin and user Recycle bin items.
  • Inconsistency in discussion boards.
  • Features, solutions or assemblies associated with site/web (Must be manually migrated if separate farm and exist on destination).
  • Taxonomy (The term set values will be migrated from source to destination).
  • No support for Claims Authentication.