How to Move Your Server to the Cloud: A Step-by-Step Plan

Most small businesses can retire the server in the closet, and most of them should. Email and files have better homes, identity no longer needs a domain controller, and the box that beeps at 2 a.m. is a liability the business stopped needing a while ago. But “move everything to the cloud” is a slogan, not a plan, and some things genuinely do not belong in the public cloud. This is the plan we use with clients: an inventory, a destination for each workload, identity, files, backups, the cutover and what to do with the applications that still need a real server.

The short answer: moving a server to the cloud rarely means copying it somewhere else. Email, files and sign-ins move into Microsoft 365, applications move to their vendors’ cloud editions where those exist, and anything that still needs Windows Server runs on a hosted virtual machine, so the office usually ends up with no server at all. If your server runs Windows Server 2016 there is also a deadline: Microsoft ends its security updates on January 12, 2027.

Move the server as it is, or retire it?

There are two ways to move a server to the cloud. The first is lift and shift: copy the whole server, as a virtual machine, into Microsoft Azure, Amazon Web Services or a hosting provider’s data center. It is quick, nothing changes for your staff, and it suits an application whose vendor insists on Windows Server. But you still have a server to patch, license and back up, a virtual machine that runs all month costs more in the public cloud than most owners expect, and shared files feel slower over the internet than they did down the hall.

The second is to retire the server: give each job it does a better home, until nothing is left for it to run. That is the plan below, and it is the right answer for most small businesses. Lift and shift still has a place for the one or two workloads that genuinely need a server, which is why the plan sends those to a hosted server or to a virtual machine under our cloud support.

Step 1: Inventory what the server actually does

Before anything moves, write down every job the server performs and who depends on it. Shared folders and who uses each one. Applications installed on it, with the vendor’s name and the version. Databases. The domain controller role, printers, scanners that save to it, backup jobs, scheduled tasks nobody remembers, and integrations between systems. The list is always longer than the owner expects, and every item on it needs a destination. Under a managed IT plan most of this documentation exists already; if it does not, this step is a week of work and worth every hour.

Step 2: Give every workload a destination

The pattern that emerges is usually this: email, files and identity go to Microsoft 365; applications go to their vendors’ clouds where they exist; and one or two things remain that need a Windows server. Those go to a hosted or colocated server, which gets them out of your closet without forcing them into a public cloud that suits them badly. Our article on the pros and cons of hybrid cloud covers that middle ground.

Step 3: Identity without a domain controller

The domain controller is the part owners assume they must keep. For most small businesses they need not. Windows computers join Microsoft Entra ID directly, people sign in with their work account, and Intune applies the settings a domain used to: encryption, password rules, software, printers. Conditional Access replaces the office firewall as the thing that decides who gets in. The transition involves re-joining each computer, which is a planned afternoon per group of machines. Where an application still requires Active Directory, the domain controller becomes a small virtual machine in hosting, synchronised to Entra ID, and the office keeps no server at all.

Step 4: Files, the slow part

Files take longer than email because nobody has cleaned them up since the last server. Decide the structure first: department libraries in SharePoint, personal files in OneDrive, a plan for the archive. Migrate with Microsoft’s tools in passes, a first copy while the old share is still live and a final delta at cutover, so the switch is quick. Check the limits before you start: path length, unsupported characters, libraries with hundreds of thousands of files that will not sync well to laptops. The exceptions, large media, CAD, anything a scanner or machine writes to, go to a hosted file server or Azure Files and are mapped as a drive the way they always were.

Step 5: Backups before, during and after

Take a full, verified backup of the server before the first migration pass and keep it until well after cutover. Then set up the backups for the new arrangement: Microsoft 365 data needs its own backup, because deleted mail and files fall out of the recycle bins on a schedule and Microsoft’s responsibility ends at keeping the service running. Any hosted server needs the same daily backup to a separate location it had in the office. Our article on whether cloud data needs backing up explains why, and the backup pricing calculator gives the monthly figure.

Step 6: Security and access

Moving to the cloud moves the front door. Multi-factor authentication on every account, Conditional Access requiring a managed device for email and files, endpoint detection on every computer, and email filtering are the controls that matter once the data is reachable from anywhere. If you are on Microsoft 365 Business Premium, the tools are in the licence; our guide to what Business Premium includes lists them. Set them up before cutover, not after.

Step 7: Pilot, cut over, decommission

1. Pilot with one department for two weeks: their files in SharePoint, their computers joined to Entra ID, their application on its new home. Fix what they find.
2. Cut over the rest on a quiet weekend: final file delta, DNS changes if any, computers re-joined, old shares made read-only rather than removed.
3. Watch the first week with someone available every morning. The issues are always small and always urgent: a mapped drive, a scanner, a report that pointed at the old server.
4. Decommission after a month. Power the server off but keep it for a few more weeks, then wipe or destroy the drives and recycle the hardware through certified equipment recycling, with a certificate for your compliance file.

What it costs, honestly

Afterwards you pay per user per month for Microsoft 365, typically $14 to $22 depending on plan, plus any hosted application or server. The migration itself is a fixed-price project; for a business of 20 people with one server it is usually in the low thousands, more if an application has to be replaced. Against that you stop buying a server every five or six years, stop paying to cool, patch and back it up, and stop being the business whose whole day depends on one box. The public cloud is not always cheaper for steady workloads, which is why the hosted-server option exists, and we will say so when it applies. Our earlier article on whether moving data to the cloud is a good idea covers the trade-offs, and our cloud migration service handles the project end to end.

Common questions

How long does it take to move a small business to the cloud?

Six to twelve weeks for a business of 10 to 50 people with a single server, most of it planning and file clean-up. The cutover itself is usually a weekend. Businesses with a line-of-business application that has to be replaced take longer, because choosing the replacement is a project of its own.

What does it cost?

Two figures matter. The monthly licensing afterwards, typically $14 to $22 per user for Microsoft 365 plus any hosted application, and the one-time migration project, which for a small business is usually a fixed price in the low thousands. Against that, you stop replacing a server every five or six years and paying to keep it cool, backed up and patched.

Do we still need a domain controller?

Usually not. Computers can join Microsoft Entra ID directly, sign in with the work account and be managed by Intune, with no Active Directory anywhere. You keep a domain controller only if an application or a piece of equipment insists on one, and then it can be a small virtual machine in hosting rather than a server in the office.

What happens to the old server?

It is kept running, powered off but intact, for a few weeks after cutover in case something was missed, then the drives are wiped or destroyed and the hardware is recycled. We provide a certificate of data destruction for compliance files.

Can we move QuickBooks or our industry software?

QuickBooks Desktop moves to QuickBooks Online or to a hosted desktop; most industry applications now have a cloud edition or can run on a hosted server. Ask the vendor two questions: is there a cloud version, and if not, will it run on a server you do not own. Either answer gives you a path.

Why move from an on-premises server to the cloud?

Because the server is a single point of failure with a replacement bill every five or six years. Without it, people work from anywhere with the same security, Microsoft maintains the platform your email and files run on, and one failed box no longer stops the whole office. For a server on Windows Server 2016 there is a deadline as well: security updates end on January 12, 2027, and after that the choice is paid extended updates, a new server or the move.

What are the risks of moving a server to the cloud?

Mostly practical ones: a forgotten dependency such as a scanner or a scheduled task, a file library too large to sync well, an application separated from its database, and accounts left without multi-factor authentication once the data is reachable from anywhere. A full inventory, a verified backup before the first pass, a pilot group and security set up before cutover deal with each of them, which is why the plan above is built that way.

What should not move to the cloud?

Very large or latency-sensitive data such as CAD libraries and video, applications with licensing tied to physical hardware, systems attached to equipment, and steady workloads whose public-cloud bill would exceed the cost of a dedicated server. Those belong on a hosted or colocated server, which gets them out of your closet without putting them in someone else’s.

Talk to us

If you want to know what it would take to retire your server, we will inventory it and give you a destination and a price for every workload, free of charge. Call 952-548-5558 or contact us; the first conversation is free and there is no long-term contract.