A Microsoft 365 migration moves your email, files, and collaboration into a Microsoft-hosted tenant, and the move itself is rarely what fails. Licensing, identity, and file-path decisions made in week 1 are what cost you in month 3.
Most Texas migrations run 2 to 8 weeks and break in 3 predictable places. Licensing does not price the way it did before July 2026. SharePoint silently skips any file whose decoded path runs past 400 characters. And switching on a Conditional Access policy turns security defaults off, which can leave a tenant briefly running neither. This checklist is ordered by what breaks, not by calendar phase.
Microsoft 365 migrations get sold as a weekend project. Move the mailboxes, point the DNS, done by Monday. For a 12-person company with clean data, roughly true. For everyone else the mailbox move is the easy part, and our Microsoft 365 managed services team sees the expensive decisions get made about 2 weeks earlier, before anyone touches a mailbox at all.
What follows is the checklist we actually work from, written for companies between 20 and 300 users. It is organized around failure modes rather than a tidy before, during, and after structure, because the tidy version is where the 400-character files and the 50 GB mailboxes get missed. If you are specifically shopping for a provider rather than planning the work, our guide to Microsoft 365 migration services in Houston covers vendor selection instead.
What a Microsoft 365 migration actually moves
A Microsoft 365 migration transfers mailboxes, file shares, and collaboration data from an existing system into a Microsoft 365 tenant, then repoints authentication and mail flow to that tenant. The source is usually an on-premises Exchange server, Google Workspace, a hosted IMAP provider, or an older Microsoft 365 tenant after an acquisition.
Underneath those 4 workloads sits the part nobody puts on the project plan. Identity. Every mailbox, file permission, and Teams membership resolves back to a user object in Microsoft Entra ID, and if that layer is wrong the rest of the migration inherits the problem. We have seen technically clean mailbox moves land users into a tenant where shared calendars, distribution groups, and folder permissions all needed rebuilding by hand. Group membership was never mapped. That is a 3-day cleanup nobody scoped.
- Exchange Online for mailboxes, shared mailboxes, resource calendars, distribution groups, and public folders
- OneDrive for individual user documents, which is usually the messiest source data in the whole project
- SharePoint Online for department shares, project folders, and anything currently living on a mapped drive letter
- Microsoft Teams for chat history, channel files, and meeting configuration
- Microsoft Entra ID for user accounts, groups, licenses, and the authentication rules that govern all of the above
Why so many Texas companies are migrating right now
Three deadlines converged, and they explain most of the migration volume we are seeing across Houston, Dallas, and San Antonio this year. None of them are optional and all 3 have already passed their announcement window.
Support for Exchange Server 2016 and 2019 ended on October 14, 2025. Microsoft no longer ships security fixes, bug fixes, or time zone updates for either version. If you are still running one, you have been unpatched against new vulnerabilities for over 9 months, and an internet-facing Exchange server is not a quiet risk to carry.
Then pricing changed. Microsoft announced increases on December 4, 2025 that took effect July 1, 2026. Business Basic went from $6 to $7 per user per month and Business Standard from $12.50 to $14. Business Premium held at $22. That last detail is the one worth sitting with, and we come back to it below.
Third, basic authentication for SMTP client submission is on its way out. Microsoft revised the timeline in January 2026, and the current position is that basic auth for SMTP AUTH stays available through December 2026 before being disabled by default. Every scanner, copier, alarm panel, and line-of-business app that emails through your server is affected. Inventory them during migration, not after.
| Forcing function | Date | What it means for your plan |
|---|---|---|
| Exchange 2016 and 2019 end of support | October 14, 2025 | No security patches. Migrate or move to Exchange Server SE |
| Microsoft 365 price increase | July 1, 2026 | Standard rose 12%, Premium did not move. Re-run your tier math |
| Basic auth for SMTP AUTH disabled by default | End of December 2026 | Audit every device and app that relays mail before you cut over |
The discovery work that decides everything else
Discovery is 2 questions. What do you actually have, and what license do you actually need. Get those wrong and every later step inherits the error, which is why we will not quote a migration timeline before this is finished.
Inventory before you price anything
Run this against real data, not against what the last admin documented. The gap between the two is usually where the schedule slips.
- Total mailbox count, split into user, shared, and resource mailboxes, plus the size of the largest 10
- Total file share volume in GB and file count, because 400 GB across 90,000 files behaves nothing like 400 GB across 4 million
- Every device or application that sends mail through your current server, including copiers, ERP systems, and monitoring tools
- Public folder usage, which is the single most common reason a 4-week project becomes a 9-week one
- Anyone under a legal hold, since held mailboxes are blocked from several native migration paths
- Current DNS host, registrar login, and who is authorized to change records, which is a surprisingly frequent day-of blocker
Pick the license tier before you pick the migration method
This is the recommendation that changed 30 days ago and has not made it into most migration checklists yet. Before July 2026 the gap between Business Standard and Business Premium was $9.50 per user per month. Standard went up, Premium did not, so that gap is now $8. For a 60-person company that is a difference of about $5,760 a year, and Premium is what carries Microsoft Intune for device management, Microsoft Entra ID P1 for Conditional Access, and Microsoft Defender for Business.
Choosing Standard to save money at migration therefore buys you a second project later to add the security tooling you skipped, at a moment when the price difference is smaller than it has ever been. We do not think Premium is right for every company. We do think the arithmetic materially changed on July 1 and most people making this call have not noticed.
There is a second constraint hiding in the tier choice. Business plans and Exchange Online Plan 1 cap user mailboxes at 50 GB. Plan 2, E3, and E5 raise that to 100 GB and add a 1.5 TB auto-expanding archive. Now picture an on-premises Exchange server where 3 executives have grown 70 GB mailboxes. A Business Standard license will not hold them. You find that out mid-migration rather than during planning, which is the worst possible week to be renegotiating licenses.
| Plan | Per user, per month | Mailbox cap | Best fit |
|---|---|---|---|
| Business Basic | $7 | 50 GB | Web-only users, frontline staff, no desktop Office apps needed |
| Business Standard | $14 | 50 GB | Small teams with simple security needs and no device management |
| Business Premium | $22 | 50 GB | Under 300 users wanting Intune, Conditional Access, and Defender in one SKU |
| Microsoft 365 E3 | $39 | 100 GB | Over 300 users, large mailboxes, or advanced compliance requirements |
Prices above reflect annual-commitment rates after the July 1, 2026 change. If you are weighing the platform itself rather than the tier, our comparison of Microsoft 365 versus Google Workspace is the better starting point.
The 400-character problem and other things that fail quietly
Here is the failure mode that produces the angriest phone call, usually about 10 weeks after everyone declared the project a success. SharePoint Online and OneDrive reject any item whose entire decoded file path exceeds 400 characters, counting the folder path and the file name together.
The word doing the work in that sentence is “decoded.” Spaces and special characters expand during URL encoding, so a path that looks comfortably short in File Explorer can blow past the limit once it lands in SharePoint. Deeply nested project folders on a legacy file server hit this constantly. Here is the part that hurts. The migration tool does not stop and warn you. It skips the file, logs it, and keeps going. Nobody reads a 40,000-line migration log.
Alongside path length, Microsoft blocks a specific set of characters and names. The characters ” * < > ? / \ | are not permitted in file or folder names, leading and trailing spaces are rejected, and reserved names like CON, PRN, AUX, NUL, and desktop.ini will not migrate. Individual files also cap at 250 GB, which almost nobody hits, and libraries cap at 30 million items, which large engineering firms occasionally do.
So scan the source before you migrate anything.
- Run a path-length report across every share and fix anything over roughly 350 characters, leaving headroom for the destination site URL
- Bulk-rename files containing blocked characters and strip trailing spaces and periods
- Delete or archive anything untouched in 5 years rather than paying to move it twice
- Reconcile the source file count against the destination file count after migration, then investigate the difference instead of assuming it is noise
- Keep the source file server read-only for at least 30 days post-cutover so recovery is a copy rather than a restore
Honest correction on our own advice here. We used to run the path-length scan as a post-migration cleanup item, on the theory that the tool would surface failures loudly enough. It does not. Moving that scan to pre-flight is the single change that has removed the most rework from our migration projects.
How long a Microsoft 365 migration really takes
Your timeline is set by physics and data hygiene. Not by how motivated your provider is. Microsoft throttles migration traffic deliberately, and no amount of project urgency changes the rate at which bytes land in a mailbox.
Cutover migration, where every mailbox moves at once, is supported up to 2,000 mailboxes, though Microsoft notes that the time required makes it impractical much above 150 users. Past that, batched or hybrid migration is the realistic path, and it runs longer by design because coexistence is the point.
| Organization size | Realistic window | What actually gates it |
|---|---|---|
| Under 25 users | 1 to 2 weeks | Mostly scheduling and user comms. The data moves fast |
| 25 to 75 users | 3 to 5 weeks | File share cleanup and the largest mailboxes |
| 75 to 200 users | 5 to 8 weeks | Batching, coexistence, and application mail relay remediation |
| 200 users and up | 8 to 16 weeks | Hybrid identity, public folders, and per-department SharePoint architecture |
| Tenant to tenant after an acquisition | 8 to 12 weeks minimum | Licensing, domain release from the source tenant, and a 4 to 8 week coexistence period |
Acquisitions deserve their own line because they are consistently underestimated. Microsoft shipped a native cross-tenant migration orchestrator into public preview in December 2025, which handles Exchange mailboxes and OneDrive. It does not carry SharePoint sites, Teams channels, or Power Platform automations, and it requires a per-user add-on license on top of E3 or E5 on both tenants. Anyone quoting you a 3-week tenant merge has not read the tool documentation.
The cutover sequence for DNS and mail flow
Cutover day is the only part of a migration where the order of operations genuinely cannot be improvised. Run it in this sequence.
- Drop the TTL on your MX and Autodiscover records to 300 seconds at least 48 hours before cutover, so the change propagates in minutes rather than hours
- Complete a final delta sync of mailbox data while mail is still flowing to the old system
- Change the MX record to Microsoft, then verify propagation from several external resolvers rather than trusting a single lookup
- Update Autodiscover, then confirm that a freshly profiled Outlook client resolves to the new tenant
- Publish or update SPF, DKIM, and DMARC records for the new mail path, because this is where deliverability quietly breaks
- Reconfigure every scanner, copier, and application relay you inventoried during discovery
- Watch the message trace for 72 hours and keep the old system reachable but not authoritative
- Restore the original TTL values once mail flow is stable
Expect a tail. Even with correct records, some clients keep resolving to the old Autodiscover endpoint for a day or more while caches expire. That is normal and it is not a reason to roll back. Warn users in advance that a single Outlook restart or profile rebuild fixes it, or your help desk will absorb every one of those calls as a separate ticket.
Do the identity and security work before cutover, not after
Most checklists put security at the end, filed under hardening. That ordering creates a real exposure window, and there is a specific trap inside it worth spelling out.
New tenants ship with security defaults switched on, which enforces MFA registration and blocks legacy authentication protocols. Conditional Access is the more granular replacement. What catches people is that the 2 are mutually exclusive. The moment any Conditional Access policy exists in your tenant, in any state, security defaults can no longer be enabled.
So an admin creates one Conditional Access policy in report-only mode, just to test it. Security defaults switch off. The report-only policy enforces nothing. The tenant now has neither control active, and it usually happens in the exact week when mailboxes are landing and attention is elsewhere. Build the full Conditional Access policy set first, validate it in report-only, then move the policies to enabled and confirm enforcement before you disable anything.
- MFA enforced for every user, with admins on phishing-resistant methods rather than SMS
- Legacy authentication blocked, which is what closes the door on password-spray attacks against Exchange Online
- Break-glass accounts created, excluded from Conditional Access, and stored somewhere that is not the system you just migrated
- Least-privilege admin roles assigned, so nobody is running daily work as Global Administrator
- External sharing defaults set on SharePoint and OneDrive before users start uploading, because retrofitting this is painful
- Audit logging and alerting confirmed as running, since the default retention window is shorter than most people assume
What Microsoft does not back up for you
Microsoft operates a shared responsibility model. Microsoft guarantees the infrastructure and the uptime. Your data, and its recoverability, stay yours. The Microsoft Services Agreement itself recommends third-party backup, which is a strong hint about where the line sits.
Two features get mistaken for backup. Neither one is. Retention policies preserve data in place for compliance and legal purposes, which is not the same as a restorable point-in-time copy. Litigation hold only preserves from the moment it is switched on, so anything deleted before activation is simply gone. And neither one protects you from a ransomware event that encrypts data locally, then obligingly syncs the encrypted version up to the cloud.
Add third-party backup during the migration while you are already touching every workload, not as a follow-up project that competes with next quarter budget. Our breakdown of business continuity versus disaster recovery covers how the recovery objectives should be set, and disaster recovery in Texas covers the regional considerations, hurricane season included.
The 30 days after cutover that most projects skip
Technical success and business success are different outcomes, and the gap between them is training. Published adoption research puts Microsoft 365 usage at roughly 30% to 40% without structured change management, rising to 70% to 85% within 90 days when it is present. You can migrate perfectly and still have most of the company emailing attachments to each other from a SharePoint site nobody opens.
- Short, role-specific training close to go-live rather than one long session weeks beforehand
- A named internal champion per department who fields the small questions instead of routing them to IT
- A license true-up 30 days out, removing seats for departed staff and converting individual mailboxes to shared where appropriate
- A file count reconciliation against the source, run once and documented
- A formal decommission decision on the source environment, with a date, rather than letting an unpatched Exchange server run indefinitely
That last item matters more than it reads. The most common thing we find during a new client assessment is a still-running, still-unpatched on-premises Exchange server that everyone forgot about because email had been working fine from the cloud for 2 years.
Texas-specific items worth adding to the list
A migration is the cheapest moment to fix a compliance posture, because you are already reconfiguring every control. A few items are specific to what we see across Texas industries.
Texas SB 2610 offers a safe harbor from certain data breach damages for businesses under 250 employees that maintain a recognized cybersecurity framework. Migration is when you can align to one without a separate project, and our guide to Texas SB 2610 covers what qualifies. Healthcare organizations need a signed Business Associate Agreement with Microsoft plus correctly scoped retention before any protected health information lands in the tenant.
Defense and aerospace suppliers around San Antonio and Fort Worth have a harder constraint. CMMC and NIST 800-171 requirements generally mean Government Community Cloud rather than commercial Microsoft 365, and that decision has to be made before the tenant is created, since migrating between the 2 later is a second full project. Our CMMC compliance overview covers the assessment path. Energy firms handling seismic and reservoir data should confirm file size and library item limits against their actual datasets rather than assuming, because that sector hits the ceilings other industries never see.
When to run it yourself and when to bring in a partner
Plenty of companies should just do this themselves. Under about 25 users, coming from a hosted email provider, with files already in a cloud sync tool and no compliance obligations, a capable internal admin can run the whole thing with Microsoft documentation and a free weekend. We would rather say that than pretend every migration needs a signed engagement.
The calculus shifts when any of 4 things are true. You are coming off on-premises Exchange with hybrid identity. You hold more than roughly 500 GB of unstructured file share data. You carry a regulatory obligation. Or you are merging tenants after an acquisition. Each one turns a linear project into a dependency graph. At that point the failure cost stops being an inconvenience and starts being a quarter.
Uprite has managed Microsoft environments for Texas businesses since 1999, with offices in Houston, San Antonio, Dallas, and Katy so on-site cutover support does not depend on someone driving in from another metro. Every ticket carries a sub-10-minute triage commitment, our average first response runs about 5 minutes, and every engagement includes a 120-day satisfaction guarantee and a first-year rate lock. We earned our 7th consecutive MSP 501 recognition in 2026 at No. 264.
For the ongoing side of the platform, see cloud services in Houston, cloud services in San Antonio, or managed cloud services in Dallas. If you are moving providers at the same time as platforms, switching MSPs without downtime is the companion read, and the Texas MSP Pricing Index shows what ongoing managed IT services run per user across the 3 metros.
Want your migration scoped before you commit to a date?
We will run the mailbox inventory, the file path scan, and the license tier math, then give you a realistic timeline and the list of things that would have failed quietly. You keep the assessment whether or not you work with us. Call (866) 570-3065 to start.
What Texas teams ask before they migrate
How long does a Microsoft 365 migration take for a 50-person company?
Plan on 3 to 5 weeks end to end. Roughly 1 week of discovery and remediation, 2 to 3 weeks of staged mailbox and file movement, and a cutover weekend followed by a support tail. What stretches it is almost never the mailboxes. It is unstructured file share data and applications that relay mail through the old server.
Will our email go down during the migration?
No, if the cutover is sequenced correctly. Mail continues flowing to the old system until the MX record changes, and messages arriving during the switch queue and deliver rather than bounce. What users do notice is a brief Outlook reconnect and occasional stale calendar data for a day while Autodiscover caches expire.
Do we lose our old emails and files during a migration?
Nothing should be lost, but verification is on you. Migration tools skip items they cannot move, most often files past the 400-character path limit or names using blocked characters, and they log the skip rather than stopping. Reconcile source and destination counts after the move and keep the source read-only for 30 days.
Should we choose Business Standard or Business Premium?
Premium, for most companies with 20 or more employees. Since the July 1, 2026 price change the gap narrowed to $8 per user per month, and Premium is what includes Intune device management, Entra ID P1 Conditional Access, and Defender for Business. Buying Standard usually means funding a second security project within the year.
Can we migrate from Google Workspace to Microsoft 365?
It is a well-trodden path and the data moves cleanly enough. Gmail, Drive, and Calendar all transfer, though Google Docs files convert to Office formats and complex sharing permissions rarely survive intact. Budget extra time for shared drive permission mapping, which is consistently the messiest part of a Workspace move.
What does a Microsoft 365 migration cost in Texas?
Project pricing typically runs a few thousand dollars for a small straightforward move up into the tens of thousands for hybrid Exchange or tenant-to-tenant work. The variables are mailbox count, file share volume, and whether identity is hybrid. Licensing is separate and ongoing, starting at $7 per user per month.
Do we still need backup if everything is in Microsoft 365?
Yes. Microsoft protects the platform, you remain responsible for your data. Retention policies preserve content in place for compliance and litigation hold only captures data from its activation date forward. Neither gives you a restorable point-in-time copy after a ransomware event or a mass accidental deletion.
