On migration from classic site to modern site in SPO, the action in question is how to migrate classic pages to modern pages in SPO.
Step #1:
To prevent this issue avoid overwriting the "Site Pages" library to ensure the out of the box "Site Pages" library schema remains intact:
a) Add a List filter to filter out the library.
Or
b) Configure a Custom Copy mode to prevent the library from being overwritten.
Step #2:
Copy just the pages from source to target using "Paste All List Items" job.
Step #3:
You should then be able to transform the classic pages to Modern pages without any issues with the assistance of Pnp library offered by Microsoft.
Reference here.
Notice: If you don't filter out the pages library and run a full copy migration of the pages library from source that would overwrite the default one that was create automatically as part of the site creation, you may notice the following error message when trying to apply the pnp Powershell :
Sorry, something went wrong.
+ ConvertTo-PnPClientSidePage -Identity "Home.aspx" -Library "SitePages
+ CategoryInfo : WriteError: (:) [ConvertTo-PnPClientSidePage], ServerException
+ FullyQualifiedErrorId : EXCEPTION,SharePointPnP.PowerShell.Commands.ClientSidePages.ConvertToClientSidePage
Column 'ClientSideApplicationId' does not exist. It may have been deleted by another user. /sites/Lab-TeamSite/SitePages
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center