SharePoint Add-In retirement in Microsoft 365

Hi BertJansen ,

We are trying to migrate the AppWeb data to the HostWeb because the AddIn model is being deprecated.

We want to use the SharePoint Migration API because of the large volume of data an AddIn instances we have on our clients.

We tried to do a basic test, regular site to regular site Migration using the Migration API and ran into problems.

When using SharePoint migration API with CreateSPAsyncReadJoband CreateMigrationJob we have an issue where CreateMigrationJob can’t parse the manifest that the CreateSPAsyncReadJob creates. It throws an error [System.Xml.Schema.XmlSchemaValidationException] [The 'Description' attribute is not declared.].

Question would be: is this is how it is intended to be used or does the manifest need to be somehow edited/modified before using it with CreateMigrationJob? If this is how it’s meant to be used then we would like guidance on resolving this bug/issue.

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

PnP.Core

Developer environment

Windows

Additional environment details

• PnP.Core 1.14.0
• PnP.Framework 1.17.0
• WindowsAzure.Storage 9.3.3

Bug / error description

1. Using CreateSPAsyncReadJob to create the migration package which works fine:

                           ClientResult<AsyncReadJobInfo> output = sourceContext.Site.CreateSPAsyncReadJob(

              listUrl,

               new AsyncReadOptions

               {

                  IncludeDirectDescendantsOnly = false,

                  IncludeSecurity = false,

                  IncludeExtendedMetadata = true,

               },

               null,

              manifestUrlReadWrite,

              reportQueueUrlReadAddUpdateProcess);

          sourceContext.ExecuteQuery();

1. Move the packages to root level of azure container.
2. Start migration job using CreateMigrationJob

          var migrationJobId = targetContext.Site.CreateMigrationJob(

             targetContext.Web.Id,

             sourceContainerUrlReadList,

             manifestUrlReadListWrite,

            reportQueueUrlReadAddUpdateProcess);

          targetContext.ExecuteQuery();

After the third step the migration job is started, after it runs for a while (processing security and other xml’s it fails on parsing the manifest.xml

[System.Xml.Schema.XmlSchemaValidationException] [The 'Description' attribute is not declared.]

Steps to reproduce

1. Create the manifest file using the CreateSPAsyncReadJob method
2. Copy and create snapshot for all xml files at the root of the container
3. Create the Import job using CreateMigrationJob method

Expected behavior

When import is started, the manifest file should be parsed without errors by the migration job, and migration of manifest content should be started.

Additional information

Migration is being done on a very simple list, just with one column “Title” and few items.

We tried using many different options, and using our Azure Storage, we could could not get it fully migrated end to end.