Our Servers Are Getting Old. Can We Just Move Them to the Cloud?

Most server closets hold more than anyone remembers. We list what every box really does: server roles, shared folders, scheduled tasks, services running under someone's old account, license keys, anything plugged in by USB, and every copier or shortcut that points at the server by name. That list decides the plan. Skipping it is how a migration finds the forgotten job that ran payroll exports every Friday.

Active Directory is the piece people worry about most, and it is the piece we copy least. Rather than imaging an old domain controller into the cloud, we connect the office to the cloud network, build a fresh domain controller there, let Active Directory replicate to it, move the roles across and then retire the old ones. For some businesses the better answer is to move sign-in to Microsoft Entra ID and manage laptops with Intune, leaving no domain controller to look after at all. Which one fits depends on your applications, and we work that out during the inventory.

A file server rarely moves as one block. Departmental shares usually become SharePoint document libraries, personal home drives go to OneDrive, and data an application needs to reach through a normal file path can sit on Azure Files instead. Before anything copies, we clean up: paths too long for SharePoint, permissions granted to individuals instead of groups, duplicate folders, and years of files nobody has opened. Microsoft's SharePoint Migration Tool and Migration Manager do the copying. The cleanup is where most of the real work is.

Accounting, ERP and practice-management packages are usually why a physical server is still running. Each gets a call with its vendor: is cloud hosting supported, is the license tied to the hardware, and is there a hosted version that replaces the server entirely? The SQL Server database moves with its application, onto a cloud virtual machine as it is or onto a managed database service where the vendor supports it. Eligible licenses with Software Assurance may carry into Azure through Azure Hybrid Benefit, which we check before sizing.

Some things belong in the office. Print queues can move to direct printing or a cloud print service, but copiers that scan to a network folder need a new destination, and that has to be set up and tested. Door access controllers, camera recorders, phone systems and anything wired to equipment on a shop floor usually stay put. Applications nobody uses get retired with an archive taken first. That is the move-or-keep decision our cloud migration hub explains in full; here it is applied server by server.

Azure usually suits businesses already on Microsoft 365 and Active Directory, and Azure Migrate handles discovery, assessment and migration of physical servers. AWS fits businesses whose software already lives there, and it has its own replication-based migration tooling. A private or hosted cloud can suit a few servers that need predictable monthly cost or a vendor that requires a dedicated environment. Each option is costed side by side during the assessment.

Physical servers are moved with agent-based replication: a small agent on each server copies its disks to the cloud and keeps the copy current while the office keeps working. Before the real cutover we bring up a test copy in an isolated network, so it cannot clash with the live servers, and ask the people who use each application to log in and run their normal tasks. Problems found in the test cost an afternoon. Problems found at cutover cost a Monday.

Once the cloud servers are accepted, the old ones are powered off but kept intact for an agreed period in case something was missed. Then every drive is wiped with a recognized sanitization method or physically destroyed, with a written record of serial numbers. Last, we cancel what the closet used to need: warranty and support contracts, backup appliances and licenses that no longer apply.