Los Angeles · Chicagoland · Phoenix
Server and Cloud Migration Before Windows Server 2016 Support Ends
Most small and mid-sized businesses still have at least one server doing something important: sign-ins, shared drives, an accounting or practice application, a database. BTI finds out exactly what each server does, decides with you where each piece should go, and moves it with a tested fallback.
Call the IT team: Los Angeles 323-510-8003 · Chicagoland 312-492-2613 · Phoenix 480-272-8728
Free consultation
No cost. Business inquiries only. Already a BTI client? Use the dedicated support number assigned to your organization.
- ✓Over 40 years in business
- ✓400+ engineers
- ✓24/7 NOC/SOC
- ✓Microsoft Partner
- ✓Cisco Select Partner
- ✓ISO 27001 compliant governance, independently reviewed through the TAG ISO 27001 Compliance Program
Windows Server end of support dates
| Product | Support ends | Status on October 25, 2026 |
|---|---|---|
| Windows Server 2012 / 2012 R2 | October 10, 2023 (paid ESU ended October 13, 2026) | Unsupported |
| SQL Server 2016 | July 14, 2026 | Extended support ended; paid ESU only |
| Windows Server 2016 | January 12, 2027 | About 11 weeks left |
| Windows Server 2019 | January 9, 2029 | Supported |
| Windows Server 2022 | October 14, 2031 (mainstream ended October 13, 2026) | Supported, security updates only |
| Windows Server 2025 | November 14, 2034 | Supported |
Source: Microsoft Lifecycle pages for each product (learn.microsoft.com/lifecycle, checked October 25, 2026). Microsoft lists each end time as early morning on the following day; the table shows the last supported day.
Value engineer, scope, deliver, commission, then managed support
Value engineer, at no charge
BTI compares where each workload should run (a new server, Azure or Microsoft 365), what hardware or licensing can be reused, and what can be retired, so you pay only for what you need.
Scope
Every server role, application, database and backup, with costs for each destination, in an itemized proposal.
Deliver
New server or Azure environment built, secured, added to backup and monitoring, then workloads migrated on a planned window.
Commission
Applications tested with the people who use them, a test restore from backup, failover tested where it is part of the design, and as-built documentation in your company's name.
Managed support
After go-live, BTI can run the new environment with your team through co-managed IT (add people through IT staff augmentation), or for you through fully managed IT.
Finance 100% of your server and cloud migration
New servers, storage, licensing and the labor to migrate add up. BTI can arrange 3.99% vendor financing for 100% of the project, including equipment, labor and consulting, for qualified buyers, subject to credit approval. Many bank loans run 10% or more today and ask for far more collateral. Our vendor financing is secured by the new equipment itself.
What is your server actually doing?
Before anything moves, BTI inventories every role on every server. The list is usually longer than people think:
- Sign-ins and permissions (Active Directory), DNS and DHCP.
- Shared drives and mapped folders.
- Line-of-business applications and their databases.
- Printing, scanning to folders and scheduled tasks.
- Certificates, remote access and vendor connections.
- Backups, and what is actually being backed up.
Where should each workload go?
| Workload | Common destination | When it fits |
|---|---|---|
| Exchange Online in Microsoft 365 | Almost always. See Microsoft 365 migration. | |
| Shared drives | SharePoint and OneDrive, or a new file server | SharePoint for collaboration; a server for very large files or on-site applications |
| Sign-ins | Entra ID, often with a smaller on-site domain controller during transition | Depends on devices, applications and printers that still need the local domain |
| Line-of-business application | New on-site server, Azure VM, or the vendor's cloud version | Decided with the software vendor's requirements in hand |
| Database | New SQL Server version on site or in Azure | Version and licensing set by the application |
| Old apps nobody uses | Archive and retire | Cheaper than migrating them |
Four ways to migrate a server
Fresh server, roles moved across
New hardware or VM, current Windows Server, roles and data migrated. The cleanest path, with the old server kept as fallback.
In-place upgrade
Faster where supported, but it carries old problems forward and is harder to undo.
Lift and shift to Azure
The server is copied to an Azure VM with Azure Migrate. Quick, but it moves the same version and the same problems unless the server is also upgraded.
Re-platform
The workload moves to a service (Microsoft 365, a SaaS version of the application, Azure SQL). Less to maintain afterwards; more planning up front.
On-premise to cloud: an honest comparison
| New on-site server | Azure | |
|---|---|---|
| Cost shape | Purchase, then support | Monthly, based on size and hours running |
| Hardware refresh | Every few years | None for you |
| Speed for on-site users | Fast on the local network | Depends on internet connection |
| Internet outage | Office keeps working | Cloud workloads unreachable unless planned for |
| Disaster recovery | Needs an off-site copy | Built into the design if planned |
Many businesses end up hybrid. BTI shows the numbers for your workloads before you decide. Cloud strategy and longer-range planning live on cloud consulting.
How BTI runs the migration
Inventory and assess
Roles, applications, data, dependencies and backups.
Decide
Destination for each workload, with costs.
Build
New server or Azure environment, secured and added to backup and monitoring.
Test
Applications tested with the people who use them, and the software vendor where needed.
Migrate
Data copied ahead, final sync and cutover on a planned window.
Verify and retire
Old server kept until verified, then wiped and retired. Everything documented in your company's name.
Backup and recovery are part of the project
Every new server and cloud workload goes into backup before cutover, following the 3-2-1 rule. BTI works with Veeam and Datto backup. Agree your recovery point and recovery time goals during planning so the backup design matches them. See backup and disaster recovery.
Keeping servers on premises? BTI offers managed data center hosting in Phoenix at the Iron Mountain data center, where BTI's Phoenix office is located, with smart hands, co-managed monitoring and support, and disaster recovery failover. Many of BTI's larger Los Angeles clients with on-premises systems colocate network equipment and servers in Phoenix for business continuity against earthquakes and other natural disasters in Southern California, with disaster recovery failover.
What drives the cost
- Number of servers, roles and applications.
- Destination: new hardware, Azure, Microsoft 365 or a mix.
- Data volume and how long the final sync takes.
- Windows Server and SQL Server licensing.
- Software vendor involvement and after-hours cutovers.
Each item is a separate line in the proposal. BTI can arrange 3.99% vendor financing for 100% of the project, including equipment, labor and consulting, for qualified buyers, subject to credit approval.
Server migrations in your city
Los Angeles and Southern California
From Santa Fe Springs, BTI migrates servers for firms across Los Angeles and Orange County, including server rooms being retired during an office move. Call the LA IT team at 323-510-8003.
Chicagoland
From Downers Grove, BTI replaces and migrates servers for Loop and suburban organizations, including moves to Azure. Call the Chicagoland IT team at 312-492-2613.
Phoenix and Tucson
Call the Phoenix team at 480-272-8728. Desert heat is hard on server closets, which is one more reason to plan the move. Tucson on-site work is delivered through contractors.
Why BTI for server and cloud migration
- Microsoft Partner working with Windows Server, Azure and Microsoft 365.
- Workload-by-workload decisions, not "everything to the cloud".
- Over 40 years in business and 400+ engineers, counting BTI's own engineers plus the 24/7 NOC/SOC and help desk staff who work as part of BTI's team.
- ISO 27001 compliant governance, independently reviewed through the TAG ISO 27001 Compliance Program.
- Itemized proposals and documentation in your company's name.
Glossary: the terms in this page, spelled out
- EOL / EOS (end of life / end of support)
- the date a vendor stops selling, patching or supporting a product. Examples: Windows Server 2016 reaches end of support on January 12, 2027. A firewall past EOL stops getting security signatures.
- ESU (Extended Security Updates)
- Microsoft's paid program that keeps security updates flowing to a product for a limited time after support ends. Examples: Windows 10 PCs that cannot move yet are enrolled in ESU. ESU buys time; it is not a plan.
- Active Directory (Active Directory Domain Services)
- Microsoft's on-premises directory that controls sign-ins and permissions on a Windows network. Examples: Domain controllers on Windows Server 2016 need to move before support ends. User accounts sync from Active Directory to Entra ID.
- File server
- a server that holds shared drives and folders for staff. Examples: The P: drive lives on the file server. File server data moves to SharePoint or a new server.
- LOB app (line-of-business application)
- software a business runs on, such as accounting, ERP, practice management or design tools. Examples: "Test the LOB app on the new server before cutover." The vendor of the LOB app must approve the new server version.
- Hypervisor
- software that runs several virtual servers on one physical server. Examples: Three old servers become virtual machines on one host. Hyper-V and VMware are common hypervisors.
- VM (virtual machine)
- a server that runs in software on a hypervisor or in the cloud instead of on its own hardware. Examples: The accounting app moves to a VM in Azure. "Snapshot the VM before the upgrade."
- IaaS (infrastructure as a service)
- renting servers, storage and networking from a cloud provider such as Azure. Examples: Running a file server VM in Azure is IaaS. IaaS shifts hardware refresh costs to a monthly bill.
- Azure (Microsoft Azure)
- Microsoft's cloud platform for servers, storage, networking and backup. Examples: A line-of-business app VM runs in Azure. Backups are copied to Azure storage off-site.
- Azure Migrate
- Microsoft's service for discovering, assessing and moving servers to Azure. Examples: Azure Migrate sizes the VMs and estimates the monthly cost. Servers are replicated with Azure Migrate before cutover.
- Lift and shift
- moving a server to the cloud largely as it is, without redesigning the application. Examples: A line-of-business app VM is moved to Azure unchanged. Lift and shift is fast but rarely the cheapest long term.
- Hybrid
- running on-premises systems and cloud services together, connected, during or after a migration. Examples: Hybrid Exchange keeps some mailboxes on-site while the rest move. A hybrid server setup keeps one app on-site and moves files to the cloud.
- 3-2-1 backup
- three copies of data, on two kinds of media, with one copy off-site. Examples: Local backup appliance, a second copy in the cloud, and the live data. An off-site copy that ransomware on the network cannot reach.
- RPO / RTO (recovery point objective / recovery time objective)
- how much data you can afford to lose and how long you can afford to be down. Examples: An RPO of one hour means backups at least hourly. An RTO of four hours means systems back within four hours.
Frequently asked questions
When does Windows Server 2016 reach end of life?
Microsoft lists January 12, 2027 as the last day of extended support for Windows Server 2016. After that date it gets no more security updates under standard support.
Is Windows Server 2012 R2 still supported?
No. Standard support ended October 10, 2023, and the paid Extended Security Updates program ended in October 2026. Any 2012 R2 server still running should be a priority.
Should we replace our server or move to the cloud?
It depends on each workload. Email and shared files usually move to Microsoft 365, some applications run well in Azure, and others belong on a new server on site because of cost, speed or the software vendor's requirements. BTI goes through it workload by workload.
Can we upgrade Windows Server in place?
Sometimes, but a fresh server with the roles and data migrated onto it is usually cleaner, especially when skipping versions. It also leaves the old server running as a fallback until the new one is proven.
Which Windows Server version should we move to?
For new servers, Windows Server 2025 has the longest support (extended end date November 14, 2034). Windows Server 2022 is supported to October 14, 2031. Your line-of-business software vendor may require a specific version.
Is the cloud cheaper than a new server?
Not always. Azure turns a purchase into a monthly cost and removes hardware refreshes, but a server that runs all day for years can cost more in the cloud. BTI compares both for your workloads before you decide.
What happens to our backups during the migration?
Backups are confirmed before anything moves, and the new server or cloud workload is added to backup before cutover. Old backups are kept for as long as your retention rules require.
Do we need managed IT to do a server migration?
No. The migration is its own itemized project. Afterward your team can run the new environment, add co-managed IT, or have BTI manage it.
Tell us what your servers run today. An engineer will tell you the options, the risks and the deadline you are working against. The first consultation and the initial IT assessment conversation are free. The assessment scope is set on the initial engineering consult call.
Los Angeles 323-510-8003 · Chicagoland 312-492-2613 · Phoenix 480-272-8728
After go-live: keep your team in charge, add BTI where you need us.
Projects are where most relationships with BTI start. When the work is done, you choose what happens next: co-managed IT first, fully managed IT when it makes sense, and BTI back for your next project.
Co-managed IT
Your IT person or team stays in charge. BTI adds the help desk, a 24/7 NOC/SOC and engineers for the next project, with a written responsibility matrix. Need people rather than a service? Add an engineer or help desk coverage through IT staff augmentation. See co-managed IT
Fully managed IT
BTI runs IT end to end for one itemized monthly price, $60 to $290 per user per month. Managed IT · Itemized pricing
Security baseline
A cybersecurity assessment shows where the new environment stands before attackers or insurers look. Cybersecurity assessment
The first consultation and the initial IT assessment conversation are free. The assessment scope is set on the initial engineering consult call. Los Angeles 323-510-8003 · Chicagoland 312-492-2613 · Phoenix 480-272-8728
Already a BTI client? Use the dedicated support number assigned to your organization.