PikoSystem IT engineering services
فا Emergency Talk to an engineer
Network & Virtualization

Physical-to-Virtual and Cloud Server Migration

Old physical servers tend to be the ones nobody dares to touch. Our cloud migration work starts with a full inventory of services and dependencies, followed by a test run on a copy. The live service moves only after you sign off, and the old server stays powered off and untouched until the test period ends.

Get a quote 021-00000000
Tools & technology cloud-migration
  • Proxmox VE
  • VMware ESXi
  • virt-v2v
  • Disk2vhd
  • Clonezilla
  • qemu-img
  • VirtIO
  • rsync
  • Veeam Backup & Replication
5work areas
4deliverables
4steps

What is Cloud & VM Migration?

Cloud migration is moving servers and their services from old physical hardware or another virtualization platform onto virtual machines, a data center or cloud servers, with a tested plan and a way back. It is typically needed when a core application still runs on Windows Server 2008, a VMware license won't be renewed, or cloud servers were bought and nobody knows where to start. PikoSystem documents each server's services, ports, databases and hardware-bound licenses, converts physical machines with Disk2vhd, Clonezilla or virt-v2v, and moves VMware VMs to Proxmox with its import tool or qemu-img. Every server is trial-migrated on a copy first, and the old one stays untouched until the agreed test period ends. You receive a migration plan with rollback steps, a post-migration test report per service and destination documentation.

When you need Cloud & VM Migration

  • Our core application still runs on Windows Server 2008.
  • Our VMware license won't be renewed and the VMs have to move.
  • We want our servers out of the office closet and into a data center.
  • We bought cloud servers but don't know where to start the move.

What Cloud & VM Migration includes

01

Service and dependency inventory

For each server we document services, ports, databases, hardware-bound licenses and links to other systems.

02

Physical to virtual (P2V)

Windows and Linux servers are converted to VMs with tools such as Disk2vhd, Clonezilla or virt-v2v, and drivers are fixed afterwards.

03

VMware to Proxmox migration

VMs are moved with the built-in Proxmox import tool or qemu-img, VMware Tools are removed and VirtIO drivers installed.

04

Move to cloud or data center

We move VMs to cloud servers or colocation, set up addressing, DNS and firewall rules at the destination, and connect it securely to your office.

05

Cutover and rollback plan

For each service we write down the downtime window, migration order and the path back to the old server.

What you get from Cloud & VM Migration

  • Service and dependency list for every server
  • Migration plan with schedule and rollback path
  • Post-migration test report per service
  • Destination environment documentation and admin access

Cloud & VM Migration: a practical guide

VMware to Proxmox migration: what breaks it

The classic failure is a Windows VM that won't boot and shows INACCESSIBLE_BOOT_DEVICE, because its disk was attached to VirtIO SCSI before the driver was installed. Attach the disk as SATA first, install virtio-win, then switch the controller.

VMs that booted with UEFI on VMware need OVMF firmware on Proxmox. On Linux, the NIC name changes, for example from ens192 to ens18, and the static IP no longer applies. Windows sees a new adapter and leaves the IP settings on the old one. Since Proxmox VE 8.2, the built-in ESXi import tool handles much of this work.

Physical to virtual conversion on Windows and Linux

Disk2vhd copies a running server using a VSS snapshot, but databases such as SQL Server are only crash-consistent that way. Stop the database service or take a separate database backup first.

On Linux, the physical server's initramfs usually lacks VirtIO modules and has to be rebuilt with dracut or update-initramfs before it boots in the new environment. A Windows OEM license bought with the hardware does not move to a VM, so proper licensing for the virtual environment is needed.

Servers that shouldn't be moved as-is

We generally don't P2V a domain controller. Building a new DC, transferring FSMO roles and demoting the old one is safer, because restoring an old copy of a DC can cause USN rollback and break replication.

Windows Server 2008 machines can be moved, but they no longer receive security updates. If the application can't run on a newer OS, keep the VM in an isolated VLAN with tight access. Applications that open files from an office share become very slow once the server sits in the cloud, so check the architecture before migrating.

Hidden costs and risks of a cloud server move

Beyond CPU and RAM, cloud cost includes outbound traffic, backup storage, extra public IPs and a reliable office-to-cloud link. Once every user reaches services in the cloud, an office internet outage cuts access to everything, so a second link matters.

Keeping your only backup with the same provider is a risk too. Before the final cutover, lower DNS TTLs so IP changes take effect quickly, and check legal requirements on where data may be stored.

How Cloud & VM Migration works

  1. 01

    Discovery

    We review servers and services and document dependencies.

  2. 02

    Planning

    Migration order, downtime windows and rollback are agreed with you.

  3. 03

    Trial migration

    We copy each server, boot it at the destination and have key users test it.

  4. 04

    Final cutover and handover

    Final data is synced and the service is switched over. The old server is kept until the agreed test period ends.

Cloud & VM Migration: frequently asked questions

How much downtime does a VMware to Proxmox migration cause?

Downtime depends on disk size and network speed, and we estimate it per VM. Less critical VMs move during working hours, core ones at night or on a weekend. If something goes wrong, the original VM is powered back on in VMware.

What about software that uses a hardware dongle?

Many USB dongles work inside a VM through USB passthrough or USB over IP. Licenses tied to hardware IDs may need reactivation by the vendor. We check these cases before the move.

Should we rent cloud servers or put our own hardware in a data center?

It depends on the type of data, legal requirements, monthly cost and how much control you need over hardware. During discovery we lay out the options side by side with cost and risk, so the decision is well informed.

Related searches

  • cloud server migration
  • physical to virtual conversion
  • P2V
  • VMware to Proxmox migration
  • data center server move
  • cloud migration services

Related services

Quote

Tell us what you need, we'll come back with a plan and a price

A few lines on where things stand and what you want is enough. An engineer calls you back, not a sales rep.

  1. 01We read your request and call if anything is unclear.
  2. 02If needed, we do a quick remote review or a site visit.
  3. 03You get a written proposal with scope, timeline and cost.

Your details are only used to answer this request.