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.

NOTES:  

§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.

NOTES:  

§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.

It is possible to migrate your SharePoint Designer (SPD) customized Form pages when migrating a SharePoint list, library, site, or Site Collection.

When migrating between the same versions of SharePoint, Metalogix Content Matrix will copy the customized Form page to the target environment, and all customizations will be preserved.

If migrating between two different versions of Metalogix Content Matrix will only migrate the contents of the Content Area - PlaceHolderMain on the Forms page. This is because not all of the file content is compatible between SharePoint versions. Each Forms page only has one Content Area, so Metalogix Content Matrix will search the page for the Content Area tag, and will migrate the contents of "PlaceHolderMain" to the target.

The Content Areas are marked with the tag:

<asp:Content ID="Content7" ContentPlaceHolderId="PlaceHolderMain" runat="server">

NOTE: Depending on the Form page customizations in your source environment, the Content Areas tags may appear different from the tag listed above.

If content is found under the tags in the content area, then Content Matrix will move that data to the same section of the content area on the target SharePoint Form page. Only the content of these tags are migrated to the target, instead of migrating the actual page itself. If any of the customizations actually block Content Matrix from finding these tags on the source page, then the contents will not be migrated because Content Matrix will not be able to find anything to migrate (but the web parts will still be migrated).  In fact, when the Copy Customized For Pages option is selected, Content Matrix will automatically select the Copy Web parts on Form Pages check-box option (under the Classic Web Part Options tab) because web parts must be copied if migrating Form page customizations.

InfoPath forms can be migrated through the same process as migrating a SharePoint list.

IMPORTANT:  InfoPath forms can only be migrated to the Enterprise edition of SharePoint 2019.

NOTE:  Currently, if Office 365 OAuth with MFA Authentication is used, Content Type InfoPath forms will not be migrated, and browser enabled InfoPath form templates will not be browser-activated at the target.

Criteria for Link Correction

When migrating InfoPath forms, Metalogix Content Matrix will automatically try to run link correction, provided the Enable Link Correction option in the General Options tab is enabled, on any items that meet the below criteria:

·If the BaseTemplate for the list is a FormLibrary.

·If the item contains ".XML" in its FileName field.

NOTE: If an XML file is manually uploaded to a forms library it will undergo this link correction process as well. However, since these XML files will not actually have the necessary InfoPath form links to correct, no links will be corrected for the file. No logging will occur for the link correction in these types of files.

If the item does not meet both of these requirements, then the link correction process will not try to correct the link data for InfoPath forms.

If the Verbose logging option under the General Options tab is not enabled, then this link correction will not be reported in the migration logs. However, if the Verbose option is enabled, then any successfully corrected links in the InfoPath forms will be reported in the migration logs.

NOTE: A mandatory InfoPath Item Content Link Corrector transformer for this InfoPath link correction ability can be found in the Transformations tab, under the SharePoint Items transformer definition.

Before continuing into the SharePoint workflow migration process, it is a good idea to have a better understanding of what each of these workflow pieces are.

·A workflow association contains all the data necessary to run the workflow at a given level (i.e. all the variables). For example, they contain all the parameters for a workflow Instance, default values, a list of steps that need to be taken, and other tasks (such as sending email to specified users). Workflow associations can be present in the following:

§In SharePoint 2007, they can be found in lists, libraries, and content types.

§In SharePoint 2010, they can be found in sites and site collections.

§SPD 2010 platform workflow associations can be found in sites and site collections, and SPD 2010 platform and Out-of-Box workflow associations can be found in lists and content types.

§SPD 2013 platform workflow associations can be found in sites, site collections, and lists.

Only the most recent version of the workflow associations will be migrated.

·Metalogix Content Matrix can also migrate the workflow template, so long as the template is defined locally on the source SharePoint server (and is in a hidden list called "Workflows") and is not defined at the server level. This is usually the case for SharePoint Designer (SPD) workflow templates and  Nintex workflow templates. Basic Out-of-Box (OOB) templates are not defined locally (they are not listed in this "Workflows" folder), so OOB Templates are not supported for migration. However, Metalogix Content Matrix will look for these OOB templates on the target, and while it cannot migrate the OOB templates themselves, it will activate the required features to enable them.

·Metalogix Content Matrix is also able to migrate workflow instances.

EXCEPTION: Migration of SPD 2013 platform workflow instances is currently not supported.

The instances are the actual running processes of a workflow, and are only present on items. Each instance is attached to an association, so if the associations are not migrated, the instance cannot be migrated either. Additionally, only the running or completed workflows that are associated with the latest workflow instance version will be migrated.

IMPORTANT:  For workflow instance migration to be enabled, migration of workflow associations and a switch that allows Metalogix Content Matrix to write the data directly to the database must be enabled.  

·Workflow histories are currently always migrated from SharePoint 2010 and never migrated from SharePoint 2013 and later, regardless of whether workflow instances are migrated.