In order for BDC or BCS data to be properly migrated:
· the Definition for the external data must be created on the target before migration.
·The name of the external content type on the target must match the external content type from the source, and there should be only one external content type with this name on the target (in SharePoint 2010 and higher there can be multiple external content types with the same name, but with a different name space).
·The appropriate account (depending on the connection type used), must have access to the external system:
§For the Local OM (Object Model) connection, the migrating user account
§For all other connection types, the application pool user account
·The Business Data Connectivity Service must be enabled and started on the target server before migration. This can only be done through a manual process, since the external data cannot be connected to or modified by Metalogix Content Matrix.
This definition can be imported from SharePoint 2007 into SharePoint 2010 or later, or it can be manually moved from/to SharePoint 2010 and later.
There are three basic types of BDC and BCS data connections that exist in SharePoint, and all three can be migrated with Metalogix Content Matrix, as described in the following table.
(SharePoint 2010 and later)
In Metalogix Content Matrix, BCS lists will appear as any other SharePoint list (listed under the SharePoint site), but will have a slightly different icon, as seen in the below image.
Since this data is read from the external system, the available actions on its Explorer View node are limited. The Items View tab can be selected to view the items within the external list. The items in the External list will also have a slightly different icon, as well as a BDC Identity column to give the item ID within the external data. This ID is also an encoded reference in the external system. In the case of an external Database (DB) connection, this ID will contain a primary key value.
NOTE: The Items View tab is not available for the DB connection.
BDC/BCS Web Parts
These are web parts within SharePoint that are connected to the external BDC or BCS data. Metalogix Content Matrix will migrate these web parts the same as any other web parts, provided that the web part itself has been installed, and the definition has been created on the target before migration. Once the web part has been migrated it will be reconnected to the BDC or BCS data.
EXCEPTION: Any web parts that have web part connections (which are connections between two web parts) will not have connections preserved in a migration.
These are columns that have been added to lists and libraries in SharePoint. These columns contain BDC or BCS data that comes from the external connection (from the external content type), and this data has been associated with items in the lists. These columns will automatically be added to the target SharePoint list and libraries when they are migrated, so long as the definitions have been created on the target before migration
The migration of SharePoint OneNote Notebooks relies on the Site Notebook feature being activated. This topic describes the basic steps for migration and lists some of the possible outcomes of a migration. This will allow you to have a better idea of any possible hurtles that might be encountered when migrating OneNote Notebooks.
Prerequisites and Requirements for Migrating OneNote Notebooks
In order to migrate OneNote Notebooks:
·On both the source and target, the Site Notebook feature must be activated.
§For SharePoint Online, the Site Notebook feature is activated by default.
§For SharePoint on premises, the Office Web Application Server must be deployed before the feature can be activated.
·The action must be a Full migrations (i.e. with Overwrite settings enabled).
NOTE: Incremental migrations are not supported.
·The Copy Subfolders recursively options must be checked in the List Content Options.
NOTE: If migrating a site, It is recommended that you also select the Copy Site Features option.
Overview of OneNote Migration Process
When running a migration of SharePoint OneNote Notebooks, Metalogix Content Matrix will make the following checks:
A.First Metalogix Content Matrix will check the target site (if it already exists) to ensure that the Site Notebook feature has been activated. If the target site does not already exist, it will check the parent site, and then will create the new target site and will try to activate the feature on the new site.
NOTE: If you initiated a list-, folder-, or item-level migration and the feature is not already activated, then Notebooks will not be migrated.
B.Next, Metalogix Content Matrix will check the target for a document library that corresponds to the library on the source where the Notebooks are kept. (This library is frequently called "Site Assets," but may be any document library.) If the library does not already exist, Metalogix Content Matrix will create it. Metalogix Content Matrix will also create a <Site Name> Notebook folder if one exists on the source but not on the target.
§If a <Site Name> Notebook folder exists on both the source and the target, the folder on the target will be overwritten.
§If the migration is performed on the root level, the target is SharePoint Online, and the Team Site template has been activated, a "Team Site Notebook" will be created in Site Asset Library instead of "<Site Name> Notebook".
Limitation on Migrating OneNote Navigation
While links to OneNote Notebooks will be copied as part of a full or navigation-only migration, the copying of OneNote navigation is not supported when migrating from SharePoint Online to SharePoint on premises.
The following points should be noted when migrating document versions with Metalogix Content Matrix:
·When migrating to a target SharePoint instance that is using a Native Web Service (NWS) connection:
§the user metadata for minor versions will not be preserved.
§the Modified and Modified By fields will not be preserved for any versions with the Rejected approval status.
·When migrating to a target SharePoint instance that is using a Client Side Object Model (CSOM) or Office 365 Tenant connection, the Optionally limit the number of versions to retain options are not preserved. This includes the Keep the following number of major versions and Keep drafts for the following number of major versions options. This means that all of the major, minor, and draft versions for a document will not be preserved.
·When migrating from a SharePoint 2003 source (SPS 2003 or WSS 2.0) there are some limitations for what version data can be migrated. Please see the SharePoint 2003 Version Migration Limitations page for more details.