ConvertTo-PnPPage previously migrated a classic page successfully as of May 2025, but no longer works #5115
Unanswered
dbauer2019
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have a requirement to convert over 1300 classic wiki pages to modern pages.
Classic pages were originally in a classic site (Pages lib). I used Sharegate to migrate these pages to a modern site (SitePages lib). Both sites are in the same tenant.
I connect successfully defining the URL and the client ID.
( Connect-PnPOnline -URL $Url -ClientID $ClientID )
I am a SCA for both source and target sites
The account I use has the SharePoint Admin Role
Entra API App Registration permissions are as follows-
o Sites.FullControl.All
o Group.ReadWrite.All
o TermStore.ReadWrite.All
o Admin consent granted for all permissions.
After defining the URL and the site page that needed to be converted, I ran the following:
ConvertTo-PnPPage -Identity "PageTest.aspx"
In May, the page was successfully converted to modern with a new pagename, "Migrated_PageTest".aspx
This command no longer works and I receive the error message,
"ConvertTo-PnPPage: The property or field has not been initialized. It has not been requested or the request has not been executed. It may need to be explicitly requested."
Has there been a change to this command?
What property or field must I initialize now, that didn't need to be initialized in May 2025?
Beta Was this translation helpful? Give feedback.
All reactions