Coming at release: Office 365 email export and import
The biggest single addition in V2 has nothing to do with SharePoint. V2 will move mailboxes. It came out of the same problem the rest of the product exists for: the supported route is a scripting exercise, and the tools that are not a scripting exercise are priced for a migration project rather than for an admin who needs to move four mailboxes.
Exporting Office 365 mailboxes to PST
Two modes are planned, and the difference is who you are signing in as:
Your own mailbox
Sign in as yourself and export your own mail to a local .pst file.
No administrator rights involved, so you do not have to raise a ticket to get a
copy of your own mailbox.
Other mailboxes
Sign in as an administrator and pick which mailboxes to export. This is the departing-employee case, and the "we are being audited and need the last three years of one mailbox" case.
Importing into Office 365
The other direction is planned to take four sources, all of them into a Microsoft 365 destination over the Graph API:
| Source | How it connects |
|---|---|
| Another Microsoft 365 tenant | Sign in with MSAL and read across from the source tenant. This is the merger and demerger case, where mail has to move between two tenants you both control. |
| Generic IMAP | Any host that accepts password authentication. This is how mail arrives from a hosting provider or an older on-premises server. |
| POP3 | Any RFC 1939 host, read-only. Less capable than IMAP by nature, but it is sometimes the only thing an old mail host offers. |
| PST file | An archive already sitting on a file share or a laptop, brought back into the mailbox it belongs in. |
Where more than one mailbox is moving, source and destination will be paired up before the run starts, and the pairing can be reviewed or driven from a CSV rather than clicked through one at a time. Jobs report progress with an estimate as they go, and a run that is interrupted resumes rather than restarting, which matters when a mailbox is large enough that the transfer is measured in hours.
What "complete rebuild" actually means
V1 grew over a decade and it shows in the places you would expect: a single window doing too many jobs, work that could not be paused or resumed, and errors that surfaced as a dialog with no way to copy the text out of it. V2 is a separate application built from scratch rather than a refactor, which is why it installs alongside V1 instead of upgrading it.
The parts most likely to matter on a first run: long operations report progress properly and survive being interrupted, the app updates itself rather than asking you to download an installer, and the sign-in flow asks for what it needs once rather than interrupting a job halfway through to ask again.
Being honest about what beta means
It means a build that is genuinely in use and genuinely unfinished. Some paths have had a lot more real-world mileage than others. If you are planning a migration with a hard deadline and no fallback, run it on V1, which is the version this site sells and the one with the years behind it. If you have a job where you can afford to find a rough edge and tell us about it, the beta is the right place to be, and that feedback is the entire point of running one.
How to get in
Ask. The group is selected rather than closed, so there is no waiting list to join and no qualification to meet. Send a request and mention roughly what you would be pointing it at, whether that is SharePoint migration, mailbox export, or the tenant-to-tenant case. That tells us which scenarios are getting real coverage and which ones we are guessing about.
Request beta access See what V1 does today
Frequently asked questions
How do I get into the beta?
Ask. It is a selected group rather than a closed one, and anyone can request access. Say a little about the tenant you would be running it against, since that helps us prioritise which scenarios get tested.
Does V1 stop working when V2 is released?
No. V1 continues to work and continues to be supported. V2 is a separate application, not an in-place upgrade, so nothing changes on your machine until you install it yourself.
What email migration paths does V2 support?
None of them in the beta. The tooling is built but switched off for every licence right now, and the Email Tools tile says so. At release the plan is export from Office 365 to a local PST, either your own mailbox with no admin rights or other mailboxes with an administrator sign-in, and import into Office 365 from another Microsoft 365 tenant, a generic IMAP host, a POP3 host, or a PST file. Anything involving a PST will need Outlook installed.
When is V2 released?
We are aiming for 1 September 2026. If the beta turns up something that needs more time, we would rather move the date than ship to it.