Server migration · Irvine and Orange County

Server and file server migration to new hardware or Azure

IT Perfection moves Windows servers and file servers to new hardware, a virtual host or Azure. We map dependencies first, check backups, carry over shares and permissions, keep a rollback plan ready and test with users after cutover.

Backup checked before cutoverRollback plan readyBased in Irvine
Server technician checking servers with a laptop
1 · ReviewWe list roles, data, applications and everything that depends on the server.

When to call us

Signs it is time to migrate a server

  • The server is old, out of warranty or running out of storage
  • File access is slow and the disks keep filling up
  • The operating system is near or past end of support
  • Nobody knows which apps and drive maps depend on the server
  • You are not sure the backups would restore if it died
  • You want to move the server to Azure or a virtual host

What you get

What a server migration includes

We plan around what depends on the server, not just the box itself.

File server migration

Shares, NTFS permissions, drive maps and data are copied and checked so users find files where they expect. Data is copied in advance and topped up with a final sync at cutover, so the window when files are read-only is short.

File server management

Windows Server upgrades

Unsupported Windows Server systems are moved to a current version on new hardware or a VM. A clean build on the new version is preferred to upgrading the old installation, since it leaves years of leftovers behind.

Windows Server end-of-support upgrade

Domain controller moves

New domain controllers are added and old ones retired, with DNS, FSMO roles and replication checked. Sign-in continues throughout, because old and new run side by side until the move is complete.

Domain controller upgrade and migration

Physical to virtual or Azure

Servers are moved to Hyper-V, VMware or Azure, sized for the workload with backup and access planned. The size is based on what the old server actually used, measured over time, not on its original specification.

Azure migration

Dependency review

DNS records, DHCP, static IPs, app paths, printers and service accounts are listed before any change. Anything that refers to the old server by name or address is found in advance: shortcuts, scripts, scanner settings, backup jobs and other applications.

Backup and rollback

A tested backup before cutover, a go or no-go point and a clear way back if something fails. The old server is left untouched and powered off, not wiped, until the new one has run for an agreed period.

Methods

The ways to migrate a server, and when each fits

The right method depends on what the server does and how old its installation is.

  • Rebuild and move: a new server is built clean, and roles, data and applications are moved to it. Best for old installations and operating system upgrades
  • Lift and shift: the whole server is copied as it is to a virtual machine or Azure. Fastest, and suited to applications that are hard to reinstall
  • Replace with a service: the role moves to Microsoft 365 or another cloud service and the server is not rebuilt. Suits file shares and email
  • In-place upgrade: Windows is upgraded on the same installation. Used only where the application leaves no alternative
  • Side by side: for domain controllers, new ones are added, roles move and old ones are demoted

The name and address problem. Users and applications find a server by its name and address. After a migration, either the new server takes over the old name, or everything that pointed to the old one is updated. We decide which before the move and test it, because a forgotten scanner or shortcut is the usual complaint on the morning after.

What makes a migration go wrong. Rarely the copy itself. The usual causes are an application license tied to the old hardware, a database nobody knew was there, permissions that did not carry over, or a service account whose password nobody has. The discovery step exists to find these before the cutover window, not during it.

What you receive

What you have when the migration is finished

Everything where users expect it, and a record of how it got there.

  • The new server running, with roles, shares and applications tested by users
  • A record of what moved, from where to where
  • Permissions verified against the old server
  • Drive maps, printers and shortcuts pointing to the right place
  • A tested backup of the new server
  • Updated server records and network diagram
  • The old server powered off and kept for an agreed period, then wiped and retired

Several servers, one plan. When more than one server is moving, they are sequenced so dependencies move in the right order, usually domain controllers first, then file and application servers. Larger moves run under our IT project management service.

How the work runs

How a server migration project runs

  1. Discover

    List roles, data, apps, dependencies, backups and who uses the server.

  2. Plan

    Choose the target, set the cutover window, rollback point and user notice.

  3. Migrate

    Check the backup, then move data, roles and apps following the cutover plan.

  4. Verify

    Test shares, permissions, drive maps, apps, printing, sign-in and backups.

  5. Handover

    Update server records and diagrams, then plan the old server's retirement.

Every engagement starts with a written scope and a clear quote, so you know the expected cost before work starts. How pricing works

Technology and guides

Platforms we migrate to and from

Windows ServerActive DirectoryDFS NamespacesHyper-VVMware vSphereAzure Virtual MachinesAzure MigrateVeeam Backup and Replication

Free guides from our IT library on this topic:

Who we do this for: dental offices · law firms · CPA firms · healthcare practices · construction and engineering · manufacturing · multi-location businesses

Ali Hassani, CISSP and Certified CISO, IT Perfection

Who does the work

Ali Hassani, CISO

IT Perfection is led by Ali Hassani, who has 25+ years of experience in IT operations, Microsoft infrastructure, networking and cybersecurity. Design, implementation and troubleshooting work is planned and reviewed by Ali personally.

ISC2 CISSP certification badgeEC-Council Certified CISO badgeCisco CCNP Routing and Switching badgeMicrosoft Certified Solutions Expert Server Infrastructure badgeMicrosoft Certified Systems Engineer badgeMicrosoft Certified Systems Administrator badgeCisco CCNA Cybersecurity badgeMicrosoft Certified IT Professional badge

Need an independent security audit, compliance readiness or vCISO support instead? IT Perfection handles design, implementation and day-to-day IT; OC Security Audit is the related cybersecurity brand for audits, compliance readiness and vCISO work.

Larger or multi-vendor project?

We run it under IT project management: one written plan, one point of contact, vendors coordinated, and a tested rollback for every cutover.

IT project management

Related services

Often needed together

Physical to virtual migration

View service

VMware to Hyper-V migration

View service

Server hardware installation and upgrades

View service

Azure migration services

View service

File server management services

View service

Questions

Server migration: common questions

Do you migrate file servers?

Yes. We copy the data with its permissions and keep or update share paths and drive maps. After cutover we test that users can open their files.

Can you move a server to Azure?

Yes. We size the Azure VM, plan networking, VPN, backup and identity, and give you a cost estimate before anything moves.

Will users lose access during the move?

There is usually a short cutover window, scheduled outside working hours where possible. Users are told in advance and access is tested right after.

Why does a server migration need a rollback plan?

If the cutover hits a problem, you need a set point to stop and a tested backup to return to. We agree both before work starts.

How much does a server migration cost?

It depends on the number of servers, the amount of data, which apps move and the target platform. The first 30-minute review is free, and you get a written quote before work starts.

How long does a server migration take?

Preparation takes most of the time: discovery, building the new server and copying data in advance. The cutover itself is a short planned window. The written plan gives the schedule for your servers.

Should the new server keep the old server's name?

Often yes, because it avoids changing every shortcut, mapped drive and application setting. Sometimes a new name with an alias for the old one is cleaner. We choose with you during planning and test it before cutover.

What happens to the old server afterwards?

It is powered off and kept unchanged for an agreed period as a fallback. Once you confirm nothing is missing, it is removed from the domain and its disks are securely erased or destroyed.

Move your server before it fails on its own schedule.

Start with the free 30-minute review. No obligation, and you leave with a clear list of what is fine and what needs attention.

On site across Orange County: Irvine · Newport Beach · Costa Mesa · Tustin · Santa Ana · Lake Forest · Anaheim · Fountain Valley