Moving business email and files to Microsoft 365 without downtime takes a documented plan, not luck — this guide walks through the exact steps, from mailbox audit to DNS cutover, that keep inboxes and shared drives running during the switch in 2026.
- Cutover migration fits under 150 mailboxes; staged or hybrid handles larger teams that migrar para Microsoft 365.
- Keep MX TTL at 300 seconds before cutover and dual delivery active for at least 72 hours.
- Audit PST files over 50GB before you start — Outlook rejects oversized files mid-migration.
- Voll ships Microsoft 365 licenses in 24-48h nationwide, so licensing never blocks your migration date.
Why this matters
A botched email migration means bounced client invoices, missing calendar invites, and staff locked out of shared drives during business hours. Companies that migrar para Microsoft 365 without a written cutover plan lose the most time re-syncing mobile devices and rebuilding distribution lists after the fact, not during the actual mailbox move.
The technical part — moving mailboxes and files — is well documented by Microsoft. What breaks projects is sequencing: DNS changes made before mailbox verification, licenses assigned before the tenant domain is confirmed, or file permissions copied without checking who actually needs access. Fix the order and the migration becomes routine.
What you'll need
- A full inventory of current mailboxes, shared mailboxes, and distribution lists
- Admin access to your current mail server and your domain's DNS records
- Microsoft 365 licenses assigned per user — Voll carries these with same-day quoting and 24-48h delivery for Portuguese businesses
- A file inventory of shared drives, including total storage in GB and folder permission structure
- A migration window of at least one weekend for teams under 50 users, longer for anything above that
- A rollback plan in case DNS propagation stalls
The steps
1. Audit your current mailboxes and files
List every mailbox, its size in GB, and whether it's a shared mailbox or a real user. Flag any PST files over 50GB — Outlook and the Microsoft 365 import service both reject files past that size, and you'll need to split them before migration day. Do the same for file shares: total storage, folder depth, and who has write access versus read-only.
Skipping this step is the single biggest cause of migration overruns. A 40-mailbox company that skips the audit routinely discovers three abandoned shared mailboxes and one 80GB archive PST on migration weekend — both of which add hours nobody budgeted for.
2. Choose a migration method
Cutover migration moves everything in one batch and suits organizations with fewer than 150 mailboxes. Staged migration works for 150 to 2,000 mailboxes, moving users in batches over several weeks. Hybrid migration keeps some mailboxes on-premises indefinitely and suits organizations above 2,000 mailboxes or with regulatory reasons to keep certain data local.
Most small and mid-size Portuguese businesses fall into the cutover category. Pick staged only if downtime for the full team at once isn't an option.
3. Set up the Microsoft 365 tenant and verify the domain
Create the tenant, add your business domain, and verify ownership through a DNS TXT record. Do not assign licenses yet — verify the domain first, because licenses tied to an unverified domain create duplicate accounts that are painful to merge later.
Once verified, assign one license per active mailbox. Confirm the license tier covers the storage each user actually needs — some plans cap mailbox size lower than others, and a sales team with large attachment volume will hit that cap within months if under-licensed.
4. Lower DNS TTL before touching mailboxes
Set your MX record TTL to 300 seconds (5 minutes) at least 24 hours before migration day. This is the step teams forget, and it's the one that turns a clean cutover into a two-day mail outage. A high TTL means old DNS caches linger for hours after you switch, sending mail to a server nobody is checking anymore.
5. Migrate mailboxes in batches
Run the migration batch through the Exchange Admin Center or your migration tool of choice, starting with a pilot group of 3-5 users. Verify mailbox item counts match between source and destination before moving the rest of the company. Expect roughly 1-2GB of migrated mail per hour per mailbox, depending on attachment volume — a 20GB mailbox typically finishes in under a day.
Common mistake: migrating everyone in one giant batch with no pilot group. If something breaks — permission errors, throttling, missing folders — you find out after 50 mailboxes are affected instead of after 3.
“If dual delivery ends before every device has re-authenticated, mail starts bouncing.”
6. Migrate files to OneDrive and SharePoint
Map your current file share structure to SharePoint document libraries before copying a single file — permissions get messy fast if you copy first and organize later. Use the SharePoint Migration Tool for shares under 1TB; anything larger benefits from a staged folder-by-folder approach over several nights to avoid saturating office bandwidth during work hours.
Expected outcome: files land with owner and editor permissions intact if the mapping was done correctly. If permissions look wrong after migration, it's almost always because folder-level access wasn't documented in step 1.
7. Cut over DNS and train users
Switch the MX record to Microsoft 365's mail servers and enable dual delivery for 72 hours minimum — this keeps mail flowing to both the old and new system while devices catch up. After 72 hours with no mail landing on the old server, disable dual delivery and reset MX TTL back to a normal 24-hour value.
Run a 20-minute Outlook and Teams walkthrough for staff the same week. Mobile devices need to re-authenticate manually — this is the step that generates the most support tickets in the first 48 hours after cutover.
Need Microsoft 365 licenses fast?
Business licenses ship in 24-48h across Portugal, quoted without IVA.
Troubleshooting
- Migration batch fails partway through — check for mailbox items over the size limit or throttling from too many simultaneous connections; retry in smaller batches of 10-15 users.
- Mail bounces after cutover — dual delivery was disabled too early or the MX TTL wasn't lowered 24 hours in advance; re-enable dual delivery immediately and wait the full 72 hours next time.
- Files migrate but permissions are wrong — the folder-to-library mapping skipped a permission group; re-run the migration for that specific library rather than the whole share.
- Distribution lists disappear — these often live outside the mailbox export and need to be recreated manually as Microsoft 365 groups post-migration.
- Mobile devices won't reconnect — users need to remove the old account profile manually before adding the new one; auto-detection rarely handles the switch cleanly.
- Shared mailboxes show as duplicate accounts — this happens when licenses were assigned before domain verification finished; delete the duplicate and reassign after verification.
Tools and resources
- Exchange Admin Center for batch mailbox migration and endpoint configuration
- SharePoint Migration Tool for file shares under 1TB
- A DNS management panel with access to lower MX TTL ahead of cutover
- Microsoft 365 licenses sized to actual mailbox and storage needs, available through Voll
- For accounting practices moving client mailboxes with retention requirements, the Microsoft 365 for accounting firms guide covers compliance-specific batching
What to do next
Once mailboxes and files are stable, review access controls and retention policies specific to your sector — a law firm handling client files under confidentiality rules needs a different SharePoint permission structure than a retail business. The Microsoft 365 for law firms guide walks through that setup in detail.
FAQ
How long does it take to migrar para Microsoft 365?
A cutover migration for under 50 mailboxes typically finishes in a single weekend in 2026, including DNS propagation. Staged migrations for 150+ mailboxes stretch over 2-4 weeks in batches.
What's the best migration method for a small business?
Cutover migration is the best fit for businesses with fewer than 150 mailboxes. It moves everyone in one batch and avoids the multi-week coordination that staged migration requires.
How much does a Microsoft 365 migration cost?
Cost depends on license count and whether a partner handles the cutover for you. Licenses themselves are quoted per user without IVA through business suppliers like Voll, with delivery in 24-48h.
Will employees lose email during the switch?
No, if dual delivery stays active for at least 72 hours after DNS cutover. Mail keeps flowing to both the old and new system until every device has re-authenticated.
Can PST files over 50GB be migrated directly?
No, files over 50GB need to be split before import — Microsoft 365's import tools reject oversized PST files outright. Splitting by year or by folder usually solves this.
Is staged migration better than cutover for larger teams?
Yes, for organizations with 150 to 2,000 mailboxes. Staged migration moves users in controlled batches, which limits the impact if something goes wrong mid-project.
Do shared mailboxes need separate licenses?
Shared mailboxes under 50GB generally don't require a paid license, but they do need to be created after domain verification to avoid duplicate account errors.
One last thing
Most migration failures aren't technical — they happen because dual delivery gets switched off on day one instead of day three. The 72-hour window exists because mobile devices and cached Outlook profiles don't all re-authenticate at the same speed, and cutting delivery early strands whichever device hasn't caught up yet. Set a calendar reminder for 72 hours out before you touch the MX record, not a mental note.