Mailbox migration, simplified
Move mailboxes between Microsoft 365 and IMAP with guided connect, discover, map, validate, and run.
Sign in
Sign in with your Liquid C2 account to continue.
Projects
Configured migrations for this org — open a project to manage accounts and jobs.
| Project | Direction | Jobs | Status |
|---|
Project
| Source | Destination | State | Copied | Error |
|---|
No mapped jobs yet — continue setup to import and map mailboxes.
Completion report
Update IMAP credentials
New migration
Follow each step — connect, discover, map, validate, then run.
Step 1 of 5 · Connect
- 1Connect
- 2Discover
- 3Map
- 4Validate
- 5Run
Connect sources
Name the project, then connect source and destination. Microsoft 365 uses admin consent — no secrets to paste.
Source
Sign in as a Microsoft 365 admin. Your tenant consents to Hermes — you never paste app secrets.
IMAP passwords are encrypted at rest and removed when you purge sensitive data after migration.
Destination
Sign in as an admin on the destination tenant.
IMAP passwords are encrypted at rest and removed when you purge sensitive data after migration.
Discover
Free scan of source mailboxes — sizes, item counts, and a license estimate. No licenses are consumed.
| Mailbox | Folders | Messages | Size | Ready |
|---|
Map users
Match each source mailbox to a destination account. Auto-match uses email address; you can override any row.
| Source | Destination | Status |
|---|
Validate
We check permissions and credentials before any mail is copied.
Technical details
Run or schedule
Start migration now, or schedule for later (leave schedule empty to run immediately). Requires enough licenses for the discovery estimate.
Initial copy finished. Watching for new mail until you finalize (cutover).
| Mailbox | Status | Copied | Error |
|---|
Technical details
Settings
Purge sensitive data
GDPR erasure of credentials and mapping PII. Active jobs must be cancelled first.