Short version. A San Antonio small business with 5 to 15 users typically spends $6,000 to $14,000 to move email and file shares into Microsoft 365. Add a line of business server and the project lands between $14,000 and $38,000. The monthly run rate after the move sits at $150 to $290 per user once licensing, Azure, backup and support are counted together.
Cloud migration costs a San Antonio small business $6,000 to $85,000 as a one-time project, depending on how many servers move and whether anything needs rebuilding. Most 10 to 40 person companies here land between $14,000 and $38,000, then pay $150 to $290 per user monthly to run what they moved.
That is the number. Our cloud services in San Antonio page covers what gets managed after the cutover. Now the honest part. The project fee is rarely what breaks a budget in this market, and the reason is specific to San Antonio rather than generic to the cloud. We publish these ranges from real engagements at Uprite Services, a Texas managed IT and cybersecurity provider that has run migrations out of Houston, San Antonio and Dallas-Fort Worth since 1999.
What does cloud migration actually cost in San Antonio?
Cloud migration is the one-time project of moving email, files, applications and servers off equipment you own and onto a hosted platform such as Microsoft 365 or Azure, and it finishes on a date you can circle on a calendar. It is priced as a project, not a subscription. Two separate budgets. The recurring cloud bill that follows is a separate line, and confusing the two is the single most common budgeting error we see.
Here is what the project side looks like by company size.
| Company size | Typical scope | One-time project cost | Calendar time |
|---|---|---|---|
| 5 to 15 users | Email and file shares to Microsoft 365 | $6,000 to $14,000 | 3 to 5 weeks |
| 16 to 40 users | Above, plus one line of business server to Azure | $14,000 to $38,000 | 6 to 10 weeks |
| 41 to 75 users | Above, plus SQL, VPN retirement, identity rebuild | $38,000 to $85,000 | 10 to 16 weeks |
| 76 to 150 users | Multi-site, compliance evidence, phased cutover | $85,000 to $190,000 | 4 to 8 months |
Those bands assume a reasonably healthy starting point. One domain. Documented licensing. Someone who knows where the data lives. Strip any of those away and the number climbs, because discovery stops being a checklist and turns into archaeology. Ask about all three.
Which workloads cost what, line by line
Quotes get compared badly because providers bundle differently. One firm prices per user. Another prices per workload. A third quotes a flat number and hides the shape of the work entirely. Break it into workloads and the comparison gets honest fast. Line by line.
| Workload | What actually moves | One-time cost | What moves the price |
|---|---|---|---|
| File server to SharePoint and OneDrive | 200 GB to 4 TB, permissions rebuilt | $3,500 to $12,000 | Depth of nested folder permissions |
| Email to Exchange Online | Mailboxes, shared boxes, public folders | $95 to $220 per mailbox | Source platform and archive size |
| Line of business app to an Azure VM | 1 to 3 servers, licensing, firewall rules | $7,000 to $26,000 | Whether the software vendor supports it |
| SQL to Azure SQL or managed instance | Database, scheduled jobs, reporting | $9,000 to $34,000 | Whether the app needs code changes |
| Backup and disaster recovery re-platform | Repository, retention, restore testing | $2,800 to $9,500 | Retention length and recovery point target |
The file server line is the one people underestimate. Always. Every time. A 15 year old share with 40,000 folders and permissions granted to individual people instead of groups cannot be lifted. It has to be redesigned, and redesign is consulting time rather than copy time, which is why two quotes for the same terabyte can differ by a factor of three without either provider being dishonest. Our Microsoft 365 migration checklist for Texas businesses walks the pre-work that keeps this line from doubling.
The costs that never appear in the quote
Five lines show up after signature far more often than they show up before it. None of them are exotic. They are omissions. Each one is easy to leave out of a proposal that wants to look competitive, and easy to bill for later once the work is already underway and nobody is shopping around any more.
- Discovery and readiness. Two to five days of scoping before anything moves. Skipping it is how a fixed-fee project becomes a change order.
- Identity remediation. Stale accounts, shared logins, no multifactor. This gets fixed during migration or it gets migrated forward, and one of those is much worse.
- Parallel running. Old servers and new cloud tenant both live, both licensed, both paid for. Usually 30 to 90 days.
- Circuit and bandwidth. A 100 Mbps connection that was fine for a local file server is not fine when every file open crosses the internet.
- Decommission and disposal. Wiping, certifying and removing the old hardware. Small line. Frequently forgotten entirely.
Parallel running is the expensive one. It is also the one nobody argues about in the sales cycle, because it feels like prudence rather than cost. Put a decommission date in the contract. Not a decommission intention. Write the date down.
What you pay every month after the move
Project ends. Bill does not. Plan for both. Microsoft repriced its business plans on July 1, 2026, which changed the arithmetic for anyone renewing after that date.
| Recurring line | Per user per month | Note |
|---|---|---|
| Microsoft 365 Business Premium | $22.00 | Held flat through the July 2026 repricing |
| Microsoft 365 Business Standard | $14.00 | Rose from $12.50 on July 1, 2026 |
| Microsoft 365 Business Basic | $7.00 | Rose from $6.00 on July 1, 2026 |
| Azure compute and storage | $18 to $70 | Only if servers moved instead of retiring |
| Cloud backup with real retention | $6 to $14 | Microsoft does not keep a restorable copy for you |
| Managed support and monitoring | $125 to $200 | Tracks local San Antonio managed IT pricing |
Business Premium holding at $22.00 while Standard rose to $14.00 narrowed the gap between them to $8.00 per user monthly, and Premium is the tier carrying Intune, Defender and conditional access, which most migrations end up buying separately anyway. Anyone renewing on Standard should re-run that comparison rather than assume last year’s answer still holds. Run it before renewal. Our Microsoft 365 services in San Antonio page breaks the tiers apart properly.
One licensing detail is worth real money and almost never makes it into a quote. Microsoft 365 Business Premium already sits on Microsoft’s eligible license list for Azure Virtual Desktop on Windows 11 and Windows 10 Enterprise multi-session. If you hold Business Premium, the desktop access right is already bought. That surprises people. What is not bought is the Azure infrastructure underneath, which Microsoft bills separately as virtual machines, storage and networking. And if the session hosts run Windows Server instead of multi-session Windows, Business Premium does not cover them at all, because that build requires Remote Desktop Services client access licenses with Software Assurance. Two very different numbers hiding behind one word. Ask which build.
Why San Antonio does not price like the national average
National cost guides quote a national labor pool. San Antonio is different. This metro does not have one, and the 2025 county figures show the local pool getting tighter rather than looser, which is the opposite of what a national average would lead you to budget for.
Bexar County held 1,230 private computer systems design firms employing 9,912 people in 2025, according to Bureau of Labor Statistics county employment data. In 2024 it had 1,293 firms and 10,319 people. So that sector shed 63 firms and roughly 400 jobs inside a single year, while total private employment across Bexar County moved the other way entirely and grew from 777,264 to 780,620 over the same twelve months. People who run migrations here got scarcer in a county that got busier. Read that twice.
Their pay went up too. Average annual pay in that sector reached $107,579 in 2025 against a county-wide average of $66,454. Migration labor is not a commodity in this market. It is priced like a shortage, because it is one. Scarcity has a price.
| Role | San Antonio annual mean | Fully loaded at 1.43x | Cost per hour |
|---|---|---|---|
| Computer and information systems manager | $166,630 | $238,281 | $114.56 |
| Computer network architect | $97,370 | $139,239 | $66.94 |
| Database administrator | $107,990 | $154,426 | $74.24 |
| Computer network support specialist | $76,790 | $109,810 | $52.79 |
Those means come from the May 2025 occupational wage survey for the San Antonio metro. The 1.43 multiplier is the current ratio of total compensation to wages in the federal employer cost series, so it captures the payroll taxes, insurance and paid leave that a salary figure quietly hides from a budget conversation.
Run the arithmetic on doing it yourself. Do it now. A 200 hour migration handled by one network architect is $13,388 of loaded internal labor, and that figure assumes the architect stops doing every other thing on their plate for five straight weeks. Most small companies here do not have that person at all. Not even part time. The entire metro contains only 600 computer network support specialists.
The deadline forcing most San Antonio migrations right now
Windows Server 2016 reaches its extended end date in January 2027, per Microsoft’s published lifecycle. That is one budget cycle away. Plenty of San Antonio companies bought that server in 2017 or 2018, virtualized a couple of workloads onto it, and have not given the box a single deliberate thought since the day it was racked. Nobody has. It still runs payroll.
Three options exist. Pick one deliberately. Buy new hardware and repeat the cycle. Pay for extended security updates, which get more expensive every year they continue. Or move the workload and stop owning the problem. The third is usually cheapest across a five year window, though not always, and any provider telling you it always is has not looked at your line of business application yet.
Compliance sharpens the deadline further for one slice of this market. Companies in the Joint Base San Antonio supply chain carry Department of Defense contract requirements that an unsupported server quietly violates. If that is you, sequence the work against CMMC compliance in San Antonio rather than treating the migration as a standalone IT project, because the evidence you have to produce afterwards depends on choices made at design time. Healthcare and financial firms hit the same wall through different rules, and the fix is the same. Sequence the compliance work first. The security spend that rides alongside it is worth pricing separately, which our guide to cybersecurity costs in San Antonio handles in detail.
Where cloud migrations go over budget
Three failure modes account for most of it. Worst first.
- Scope discovered mid-flight. An application nobody mentioned. A database the accounting team runs from a desktop under someone’s desk. This is a discovery failure, and discovery is the cheapest phase to pay for properly.
- The parallel window that never closes. The old environment stays live because one report still runs there. Six months later you are paying for both.
- Rightsizing that never happens. Servers get provisioned generously for cutover and then never trimmed. Flexera’s 2026 State of the Cloud report, drawn from 753 cloud decision makers, puts wasted cloud spend at 29%, the first increase in five years.
Notice what is not on that list. Data egress fees, the thing every migration article warns about. At small business scale they mostly do not matter. Almost never. AWS gives every account 100 GB of free outbound data transfer per month, aggregated across services and regions. A 30 person company will not touch that ceiling in normal operation. Egress is a genuine problem for media and analytics workloads. For everyone else it is a scare line, and we would rather you spend that worry on rightsizing.
When moving to the cloud is the wrong call
Sometimes it is. A few honest cases.
CAD, video editing and large design files opened directly across the network usually perform worse in a cloud file service than on a local server, and no amount of bandwidth fully fixes it. Latency is physics. A line of business application whose vendor will not support a cloud deployment should stay exactly where it is until the vendor moves or you replace the application outright. Neither of those is a reason to avoid the cloud entirely. They are reasons to move some things and leave others, which is what most honest 2026 designs look like anyway.
The industry has been quietly correcting on this point. Buyers who moved everything on principle a few years ago are now moving selected pieces back onto hardware they own, which reads as a design correction rather than a verdict on the cloud itself. That nuance gets lost. The right question was never whether to be in the cloud. It is which workload belongs where, and what each option costs across five years instead of one.
How to read a cloud migration quote
Take whatever proposal is in front of you and get answers to these in writing before signing.
- Is discovery included in this price, or billed separately once it starts?
- Which specific workloads are in scope, named individually rather than described as a category?
- How many days of parallel running are budgeted, and who pays if it runs long?
- Is data cleanup and permission redesign included, or is the assumption a straight copy?
- What is the projected monthly cloud bill at month 3 and at month 12, not just at cutover?
- Who owns the tenant, the subscription and the administrator credentials when the project ends?
- What does leaving look like, and what does it cost?
The last two get skipped almost every time. Ask them anyway. Get it in writing. A provider who cannot answer the exit question comfortably is telling you something useful about the relationship you are about to enter.
How Uprite scopes a San Antonio migration
We price discovery as its own phase, deliver a written workload inventory, and quote the migration against that inventory rather than against a guess. Decommission date goes into the contract. Not the appendix. Projected monthly run rate goes into the proposal beside the project fee, because a client who gets surprised by an invoice in month 3 was not sold to properly back in month zero.
We have run this work across Texas since 1999, with local delivery through our managed IT services in San Antonio team alongside Houston and Dallas-Fort Worth. If you want to talk through what your specific environment would cost to move, our pricing page is the place to start, and small business IT support in San Antonio covers what ongoing management looks like once the migration is finished. Backup design is worth settling before the move rather than after, which is why we fold backup and disaster recovery in San Antonio into the same conversation.
Questions San Antonio owners ask before they move
How long does a cloud migration take for a 25 person company in San Antonio?
Six to 10 weeks for a typical 25 person migration covering email, file shares and one line of business server. Discovery takes the first 1 to 2 weeks. Cutover is usually a single weekend. What stretches a timeline is data cleanup and application testing rather than the copying itself, which runs unattended overnight while everyone sleeps.
Is it cheaper to move to the cloud or buy a new server?
Across five years the cloud is usually cheaper for small businesses, but not always. A single server supporting one stable application with predictable load can still win. Run both numbers. Compare total five year cost including hardware, licensing, power, maintenance and the eventual replacement cycle rather than comparing a one-time purchase price against a monthly fee.
What does cloud migration cost per user in San Antonio?
Roughly $400 to $900 per user as a one-time project cost for a straightforward Microsoft 365 move, then $150 to $290 per user monthly once licensing, backup and managed support are counted. Per user pricing gets misleading above 40 users, because server work does not scale with headcount.
Will my internet connection handle everything moving to the cloud?
Usually yes, but check upload speed rather than download. Check upload speed. Most business plans in San Antonio are heavily asymmetric, and cloud work consumes far more upload bandwidth than a local file server on the same network ever did. Budget for a circuit review during discovery. It is a much cheaper conversation before cutover than after.
Do we lose our data if we leave the cloud provider later?
No, provided you own the tenant and the subscription rather than sitting inside a provider’s account. Own both. Insist on it. Ask for the exit process in writing before you sign anything, including who holds the global administrator credentials and exactly how a full data export gets produced and handed over.
Does Microsoft back up our Microsoft 365 data?
Not in the way most owners assume. Microsoft protects the platform and offers limited retention windows, but it does not keep a restorable historical copy of your mail and files the way a backup product does. Third party backup for Microsoft 365 runs $6 to $14 per user monthly and is not optional.
Can we migrate in phases instead of all at once?
Yes, and above roughly 40 users that is the better design. Phase it. Email moves first, then files, then applications. Phasing costs slightly more in total because the parallel window runs longer, and it materially lowers the risk of a bad weekend that nobody in the building will forget. Set a firm end date for every phase.
