Update: Please see our later post on why Local Move Requests should not be used as a troubleshooting tool and why they are not supported: Local Move Requests in Exchange Online – Why They’re Not Supp...
Updated Jan 08, 2026
Version 2.0
Blog Post
In my case the New-MoveRequest was the only way to complete a public folder onboarding from onprem to Exchange Online. As you know, the onboarding process is all or nothing, and might takes days to sync the data from on-premises to Exchange Online. In all 4 attempts, the Exchange Online DB load scheduler actually locked down the target databases, preventing us from completing the migration. The only solution that worked after 2 SEVA tickets was to actually move the PFmailboxes using the CMDlet.