Switching email systems always sounds bigger than it actually is. The truth is, an IMAP to Microsoft 365 migration is one of the most straightforward moves an IT admin or small business owner can make — once you know the order of operations.
This guide breaks down exactly what IMAP migration does, what it doesn’t do, and how to move your mailboxes from Gmail, Yahoo, cPanel, Zimbra, or any other IMAP-based provider into Microsoft 365 without losing data along the way.
What Is IMAP Mailbox Migration?
IMAP (Internet Message Access Protocol) is how most email clients read and sync messages stored on a mail server. Because so many providers support it, IMAP is one of the most common ways to move email into Microsoft 365 — this is what people mean when they talk about migrating IMAP to Office 365.
If you’re not sure how IMAP compares to the other common protocol, our guide on IMAP vs. POP3 explains the difference in plain terms.
IMAP migration works with almost any provider that exposes IMAP access, including:
- Gmail and Google Workspace
- Yahoo Mail
- cPanel-hosted email
- Zimbra and Kerio Connect
- Older on-premises Exchange servers
If you need the exact server, port, and app-password details for a specific provider before you migrate, check our setup guides for Gmail IMAP settings or Yahoo Mail settings.
What Gets Migrated (and What Doesn’t)
This is the part most people miss. IMAP only moves email — not the rest of your mailbox data.
| Data Type | Migrated with IMAP? |
| Emails | ✅ Yes |
| Folders (Inbox, Sent, etc.) | ✅ Yes |
| Attachments | ✅ Yes |
| Contacts | ❌ No |
| Calendar events | ❌ No |
| Tasks | ❌ No |
If your team relies heavily on shared calendars or contact lists, plan a separate export/import step, or use a migration tool that supports more than mail.
Why Migrate from IMAP to Office 365
Most teams move for a mix of these reasons:
- Built-in collaboration — Teams, SharePoint, and OneDrive alongside the mailbox
- Bigger storage — up to 50 GB or more per user, depending on plan
- Stronger security — MFA, anti-phishing, and compliance tools out of the box
- One login — email, files, chat, and calendar in a single account
- Room to grow — licensing scales as your team does; see our Microsoft 365 plans comparison
If you’re currently on Google Workspace specifically, our dedicated Google Workspace to Microsoft 365 migration guide covers a few extra steps that apply only to that platform.
Requirements and Limitations to Know First
Before you start, get familiar with IMAP migration’s boundaries. For more information straight from the source, Microsoft’s official IMAP migration documentation lays out the technical requirements in full.
| Limitation | Detail |
| Data migrated | Email and folders only |
| Max mailboxes per CSV batch | Up to 50,000 |
| Max message size | 35 MB per email — see our Office 365 message size limit guide |
| Mailbox storage cap | Varies by plan — see Microsoft 365 mailbox size limitations |
| Archive/retention items | May be flagged “missing” if governed by MRM policies |
| Original data | Copied, not deleted — the source mailbox stays intact |
You’ll also need:
- Microsoft 365 mailboxes already created and licensed for every user
- Admin or per-user credentials for the source IMAP server
- A verified domain in your Microsoft 365 tenant
How to Migrate IMAP to Microsoft 365, Step by Step
Here’s exactly how to migrate IMAP to Office 365, from setup to cutover. This is the same IMAP migration to Office 365 step by step process people search for when they want an IMAP migration step-by-step they can follow without guessing.
Step 1: Prepare Your Microsoft 365 Environment
Add each user in the Office 365 admin center, assign a license, and verify your custom domain before touching the source mailboxes.
Step 2: Gather IMAP Server Details
You’ll need the IMAP server name (e.g., imap.domain.com), the port — usually 993 for SSL — and login credentials for each mailbox.
Step 3: Build a Migration CSV File
Create a CSV with three columns: EmailAddress, UserName, Password. Example:
EmailAddress,UserName,Password
user1@domain.com,user1@domain.com,password123
user2@domain.com,user2@domain.com,password123
Step 4: Create a Migration Endpoint
In the Exchange admin center, set up an IMAP migration endpoint. This is the connection Microsoft 365 uses to reach your old server and pull the data.
Step 5: Start a Migration Batch
Upload your CSV, select the endpoint, and launch the batch. Migrate everyone at once, or split large teams into smaller batches to keep an eye on progress.
Step 6: Monitor the Migration
Track status, error counts, and completion reports as the batch runs. Large or slow mailboxes will naturally take longer than small ones.
Step 7: Update MX Records and Go Live
Once mailboxes are verified, update your MX records so new mail routes directly to Microsoft 365. Ask users to log in and confirm everything looks right.
Where Does the Data Actually Land?
Every mailbox migrated this way ends up in Exchange Online — which is why admins often call the whole process IMAP migration to Exchange Online rather than just “Office 365 migration.” Exchange Online is the hosted mail server behind every Microsoft 365 inbox, so once your batch completes, your mail, folders, and attachments are stored there.
Manual Migration vs. Using a Migration Tool
| Feature | Manual (Admin Center/PowerShell) | Migration Tool (e.g., SkyMigrate) |
| Setup time | Longer — CSV files, endpoints, scripting | Minutes — guided wizard |
| Technical skill needed | Moderate to high | Low |
| Best for | Small batches, IT-savvy admins | Any team size, non-technical users |
| Progress tracking | Basic logs | Real-time dashboard |
| Error handling | Manual troubleshooting | Automated retries |
| Folder/date filtering | Limited | Usually included |
Both approaches land you in the same place. Microsoft’s built-in admin center and PowerShell are effectively a free IMAP migration tool — no extra cost, but more hands-on setup. A dedicated IMAP to Office 365 migration tool trades a small fee for a guided workflow, live tracking, and far less manual cleanup.
Best IMAP to Office 365 Migration Tool
If you’d rather not manage CSV files, endpoints, and PowerShell manually, SkyMigrate is built specifically to handle IMAP to Microsoft 365 migration from start to finish:
- ✅ Connect source and destination mailboxes in a few clicks
- ✅ Migrate emails, folders, and attachments with structure intact
- ✅ Filter by date range or folder before you migrate
- ✅ Track progress live with detailed completion reports
- ✅ Automatically retries failed items — no manual re-runs
For more information on how it works end to end, see our overview of what happens during email migration, then get started with SkyMigrate.
Backup Your IMAP Mailbox Before You Migrate
Migration always carries some risk, so back up the source mailbox — the IMAP account you’re migrating from — before you move anything. There’s nothing to back up on the Microsoft 365 side yet, since that mailbox is empty until the migration runs.
- Download a full local copy of the IMAP mailbox using a desktop client. If you haven’t connected the account yet, our guide on how to set up an IMAP email account in Outlook walks through the connection first.
- If your source is Gmail, use Google Takeout — see how to download your Gmail data. If it’s Yahoo, see how to backup Yahoo Mail.
- Export the downloaded copy to a PST file and store it somewhere outside the source server. Not sure where Outlook keeps it? Check how to find your PST file location in Outlook.
- Note down folder and message counts before you back up, so you have a number to check against once migration finishes.
- Keep the original IMAP account active and untouched until you’ve verified everything landed correctly in Microsoft 365 — IMAP migration copies data, but a local backup is still your safety net if something goes wrong mid-transfer.
Once migration is complete and verified, it’s worth setting up an ongoing backup routine for the new Office 365 mailbox too. Our guides on how to backup an Office 365 mailbox and how to export PST from Office 365 cover that next step.
After Migration: What to Check
Once mailboxes land in Microsoft 365, a few quick checks save headaches later:
- Confirm folder structure and message counts match the source
- Enable archive mailboxes for users with large mail history
- Set up a retention policy so nothing gets deleted too early
- Turn on MFA for every migrated account before go-live
Common Mistakes to Avoid
- Skipping the pre-migration mailbox audit. Know your total data size before you start.
- Forgetting contacts and calendars. IMAP only moves email — plan for the rest separately.
- Migrating during business hours. Run large batches overnight or on weekends.
- Not telling your team. Login details and email client settings will change.
- Skipping verification. Always spot-check folders and counts after migration finishes.
- No backup before cutover. Always have a backup ready in case something needs a redo.
Pros and Cons of IMAP Migration
Pros IMAP Migration
- Works across almost any email platform
- Simple to set up for small to mid-sized teams
- Doesn’t delete or alter the source mailbox
Cons IMAP Migration
- Only migrates email — not contacts, calendars, or tasks
- Requires per-user credentials
- Large mailboxes can slow the process down
FAQs
How do I migrate my email to Microsoft 365? Create licensed Microsoft 365 mailboxes, set up a migration endpoint for your source server, then run a migration batch through the admin center, PowerShell, or a tool like SkyMigrate. Verify folders afterward.
How long does IMAP migration take? It depends on mailbox size and item count. Small mailboxes often finish in hours; migrations covering thousands of accounts can take several days when run in batches.
What is the best migration tool for Office 365? It depends on your team’s technical comfort. For a guided process without PowerShell scripting, SkyMigrate is purpose-built for IMAP to Microsoft 365 migration.
How can I migrate my mailbox to Office 365? Set up your target mailbox, gather source IMAP credentials, create a migration endpoint, and start a batch. A migration tool turns this into a simple, click-through workflow.
Do emails get deleted from the old server during IMAP migration? No. IMAP migration copies data — it doesn’t remove anything from the source. Your original mailbox stays untouched until you decide to decommission it.
Can I migrate IMAP to Microsoft 365 for free? Yes. If you’re looking for an IMAP migration tool free of extra cost, Microsoft’s admin center and PowerShell are included with your subscription and work well for smaller migrations, though they need more manual setup than a dedicated tool.
Conclusion
An IMAP to Microsoft 365 migration is manageable once you know what to prepare, what IMAP does and doesn’t move, and what to check afterward. Create your mailboxes, back up your data, follow the steps above, and you’ll land on Microsoft 365 without losing a message.
If you’d rather skip the manual setup entirely, SkyMigrate can handle the full IMAP to Office 365 migration for you — from connection to verification. Start your migration with SkyMigrate today.
