Codemeister

Update: I fixed it. I ran the SharePoint Diagnostic Tool (https://docs.microsoft.com/nl-nl/microsoft-365/enterprise/page-diagnostics-for-spo?view=o365-worldwide) first, but despite the plug-in not showing any errors or recommendations, I was not able to execute the PowerShell commands. The solution: connect to SharePoint Online using PowerShell (Connect-SPOService), don't run any commands just yet. Now, visit the URL you want to migrate and run the diagnostic tool (see link above) from your browser. Any yellow or red warnings need to be fixed before you can actually migrate! If all checks are green, run the diagnostic tool again. Then wait a few seconds and run the PowerShell-commands to migrate the site. Using the -force parameter is not required. Now the command should work. If it does not, make sure that: - the PowerShell session is started before you run the diagnostic tool- your PowerShell-session was started using Global Admin- or (at least) SharePoint Admin-credentials- you are running PowerShell as administrator - you are logged on to the same account on both the PowerShell session and the browser you're using (the diagnostic tool will do a background check to check if the username matches) Otherwise I would recommend contacting Microsoft Support through the 365 Portal. Let me know if this worked for you!

New update on my support case:

So I created a second tenant without getting 10,000 standard licenses, and: the "replace site" button appeared. So it seems 10,000+ licenses does matter.

Same for us. But shouldn't be a problem: https://www.microsoft.com/nl-nl/microsoft-365/roadmap?filters=&searchterms=57309 and https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/sharepoint-and-onedrive-security-compliance-migration-admin-and/ba-p/960871 In short: Microsoft started enabling the site-swap functionality for 'large' tenants starting from March 2020 and as the first URL above shows 'Launched' it should be possible. But perhaps I'm wrong.

Unfortunately not, I did speak to the technical engineer again, but no luck yet. Still getting the same error. If I have new info I'll let you know.

I've created a support ticket with Microsoft. Spoke on the phone with one of the SharePoint engineers and explained the problem, we also did a remote session to show I have all required permissions. Case is now being forwarded to a senior engineer. I will keep you updated.

Did you manage to solve the error you mentioned? I'm seeing the same error. I'm administrator and owner on both sites but no luck.