Since 2019, we have been providing IaaS services to our partners with the new Copaco VMware Cloud platform. This platform offers better performance with new hardware and also has more technical options for your customers. This is often also at a lower price per resource compared to the older Copaco Hyper-V Cloud platform. Most partners are now familiar with the VMware platform, but at the same time, we also see a few remaining partners with end customers active on our Copaco Hyper-V or Windows Azure Pack infrastructure.

End of Life

In order to fully focus on the growing Copaco VMware Cloud platform, it is time to migrate all remaining customers to VMware Cloud so that the Hyper-V Cloud and Windows Azure Pack infrastructure can be retired. As of 28-2-2022, we declare the Hyper-V Cloud and Windows Azure Pack infrastructure End of Life. This means that all your customers who are currently still using Copaco Hyper-V Cloud or Windows Azure Pack must be migrated to Copaco VMware Cloud before February 28, 2022.

You can find our full end of life policy in KB:


This guide will serve as a technical guideline on what you can expect during the migration phase and what things need to be considered before a migration can be executed. The Copaco Cloud support team is available to assist with any of the migration steps required, free of charge.

In this article:


Before we begin with a migration project it’s important to write down the current usage details of the infrastructure. This can help with ordering and preparing the new VMware subscription. Within the new VMware subscription, you will also need the details to set up a network, DNS, and security settings like NAT and firewall rules.

Collect resource usage

Similar to Hyper-V and Windows Azure Pack subscriptions, Copaco VMware Cloud uses a reservation-based subscription model. In this model, you order resources in advance before you can use them. This provides certainty on the monthly costs associated with the subscription. We need to look up the current resource usage of your virtual machines in order to properly size the new Copaco VMware Cloud Subscription.

Total assigned processor resources

Processor resources are calculated differently between Hyper-V and VMware platforms. Where Hyper-V is billed based on vCPU cores with a flexible amount of GHz per vCore, VMware bills based on the amount of GHz. A single virtual CPU core in VMware consists of a 2Ghz unit. We recommend that you do a 1 (core) to 2 (GHz) conversion to start with.

You might be able to further downsize processor resources at a later date depending on the customer's usage. The VMware Platform utilizes a newer generation of physical server hardware where a single CPU Core is capable of processing more instructions.

You can find the current total number of Cores by logging into the Windows Azure Pack control panel of your current subscription. Follow these steps and take the value of the used “Cores“:

Total assigned memory

Memory is calculated similarly between Hyper-V and VMware platforms. We recommend that you do a 1 to 1 conversion of the amount of needed memory. You can find the current total memory by logging into the Windows Azure Pack control panel of your current subscription. Follow these steps and take the value of the used “RAM“:

Total assigned storage

The calculation of needed storage in the Copaco VMware Cloud differs a little bit from Hyper-V subscriptions. In Hyper-V, the total disk space of Virtual hard disks is the minimum you need. In VMware, storage is calculated based on allocated virtual hard disk space and memory swap files for powered-on VM's.

To get the total amount of storage space that is currently assigned to your Hyper-V subscription, please log into the Windows Azure pack control panel. Follow these steps and take the value of the used “Storage“:

Please note: When purchasing the resources in Copaco VMware Subscriptions, you should take into account that the number of GBs of RAM must be added to the number of GBs in Storage. For example, if the VM has 300GB storage and 8GB RAM, then 300 + 8GB RAM = 308GB storage must be ordered in the new subscription. If there is no storage space available for the hypervisor memory swap file, your VM cannot be powered on.

Total assigned Public IP’s

For customers migrating from Windows Azure Pack subscriptions, public IP addresses can be assigned directly on your virtual machines and also on a Virtual Network Gateway. For Customers migrating from Copaco Hyper-V Cloud subscriptions, you only have Public IP addresses assigned to the Virtual Network Gateway.

In VMware Cloud, all Public IP addresses are assigned to the Edge Gateway. In case you need more than one Public IP address you should add additional Public IP’s when placing the order for a Copaco VMware Cloud subscription. Internal (private) IP addresses can be assigned without additional cost on your internal organization network.

To get the total amount of Public IPs that are currently in use on your Hyper-V subscription, please log into the Windows Azure pack control panel. Follow these steps and count all unique “External IPs “ that are used in NAT translation rules.

Please note: Windows Azure Pack subscription owners should also add the count of Public IPs that are assigned directly on your virtual machine network adapters.

(Optionally) Site-2-Site (IPSEC) VPN

In contradiction to Hyper-V subscriptions, you no longer have to order separate add-ons for site-2-site VPN tunnels. This feature is natively included in the new network edge device which is provided with every subscription. You should check if VPN tunnels are active for the customer’s subscription and write down the details. We will need to recreate the VPN tunnel on the VMware Edge device.

SPLA licensing

Similar to Hyper-V, SPLA licenses in VMware are included for the Windows Operating system in every subscription. You do not have to separately purchase the Windows OS license or report them.

If you want to use additional Microsoft software which requires SPLA licenses, Copaco offers them directly from a provider SPLA contract for all VMware subscriptions (at additional cost). As a partner, you can report the number of required licenses directly in the order process of your new subscription. The actual installation and accessing of the software or keys can be requested at Copaco Cloud Support.

If you migrate from a Copaco Hyper-V cloud subscription, your SPLA licenses reported earlier will be terminated automatically with the subscription. Customers that migrate from a Windows Azure Pack subscription have a separate subscription for SPLA reporting that should be canceled separately.

Prepare for migration

VMware Cloud Subscription

Create subscription

Based on the collected resources that are being used in Hyper-V and considering the additional storage requirements in VMware we can now submit the order to provision a new subscription for the customer.

Please note: If you have a need to keep your existing Public IPs during migration, please contact Copaco Cloud Support to review the available options before placing your order. There will be special requirements on a specific data center site if you want to keep your addresses. By default, you will be assigned new Public IP Addresses from a provider pool.

We prepared the following guide to help with the order process:

Configure Edge Gateway

Once the provisioning of your order is completed, the first thing you need to do is specify the organization network details (your internal virtual network). This can be done directly in the customer control panel. Because you are migrating from Hyper-V we recommend that you use the same IP range, DNS and Gateway IP as on your existing Hyper-V vNet.

More details on setting up the organization network on your edge gateway can be found in this KB:

Create Firewall rules

In contradiction to Hyper-V, The VMware Cloud Director edge offer an additional layer of security with a built-in firewall that can be fully controlled by the customer. By default, the network edge gateway will not allow inbound or outbound communication. You will need to open ports for each type of traffic you want to allow.
The following guide is prepared to help you with the initial configuration:

Create NAT rules

Just like you are used to on the Hyper-V virtual network in the Azure Pack control panel, you must specify NAT rules to translate external IPs to Internal IPs if inbound traffic is allowed. In contradiction to Hyper-V’s vNet, you also have full control of the outbound NAT translation rules, whereby default outbound traffic is not allowed.

We have the following two KB articles prepared to help with setting up inbound and outbound NAT rules.

(Optionally) Create site-to-site VPN

If you used a site-2-site VPN on your Windows Azure Pack or Copaco Hyper-V Cloud virtual network, you can achieve the same goal with an IPSEC VPN on the Copaco VMware Cloud Edge Gateway.

We recommend that you set up the new VPN tunnel before the migration and complete rerouting traffic through the VPN during migration.

We prepared a separate guide to show you how to set up a site-2-site tunnel in VMware:

Prepare virtual machines

You need to verify and take a few actions prior to the migration.

Update Operating System

Before we consider migration a virtual machine, make sure the operating system is up-to-date with the latest patches and is still supported by the operating system vendor. Servers that still need to apply updates when shutting down might significantly increase the downtime during the scheduled migration window.

Install VMware Tools (drivers)

Make sure that you install the VMware integration drivers while the VM’s are still running on Hyper-V. We prepared a knowledge base with instructions on how to complete this with a specially prepared installer for the drivers. Please follow:

Document network interface settings

Check if your virtual machines have a fixed IP address set on the network adapter, or if they are assigned by DHCP.

If you have set a fixed network address, make sure that the new network that you create on the Copaco VMware Cloud edge gateway uses the same IP range. You can always modify IP addresses after migration, but this might cause additional downtime.

If your network adapters are set to DHCP, a new IP address will be automatically assigned by the VMware edge gateway when the VM is started for the first time. If the VM is exposed externally, please make sure you update the DNS entries/NAT and Firewall rules to prevent inaccessibility after migration.

It’s always a good idea to write down the current IP configuration of your virtual machines. During the migration process, the network adapters should be reconfigured.

Delete Snapshots

Please make sure that available snapshots of virtual machine hard drives are removed and the merge of virtual disk files has been completed before the migration window. Virtual Machines with snapshots can not be converted to VMware’s Harddisk format.


Plan for downtime

Virtual machines are turned off during migration to make sure we get a consistent copy of all data. Depending on the size of the virtual hard drives, migrations can take several hours.

As an estimate, we recommend considering that about 100GB of data can be migrated per hour. In reality, migrations can complete quicker or slower, it depends on a number of factors. An exact number cannot be given. We can migrate multiple virtual machines in parallel which can significantly reduce the total downtime.

Prepare a list of DNS changes

In most cases, the Public IP address of the edge gateway will differ from the Public IP that was used on the Hyper-V Virtual Network. We recommend that you prepare a list of DNS changes that need to be made during migration. We also advise you to check the TTL setting on your domain name to make sure DNS propagation is refreshed every hour.

It is also good to check if customer devices connect to the hosting environment based on a DNS name and not a direct IP address. If Customers devices connect using an IP we recommend updating IPs to DNS names before the migration.

Please note: In case you requested to keep existing Public IP addresses and Copaco Cloud Support confirmed that it is possible to migrate your old IP configuration, this section does not apply to you.

Schedule migration date

You are now almost completed with the preparations for migration. Please open a support case with the Copaco Cloud Support team by sending an e-mail to to schedule a date when the migration is going to take place. We request that you include all relevant customer and subscription(old and new) details in the ticket.

Copaco provides migration assistance free of charge. We can execute migrations during office hours, in evenings, or in weekends pending our availability and the date you agreed upon with the customer for maintenance activities. We expect that there will also be technical staff available with our partners during the migration timeframe to answer questions or issues that get detected during migration.

We recommend that you provide our support team with local admin/root credentials on every virtual machine that can be used for troubleshooting and verification of the configuration before and after migration. If additional testing or configuration changes need to be taken from Copaco’s team, please provide a step-by-step instruction of the requested validations.


Actions for Copaco Cloud support

The Copaco Cloud Support team will take care of the actual migration of the Virtual Machine configuration and linked hard drive data. During the agreed-upon timeframe we will take the following actions:

  1. Review if the provided credentials can be used to access the Operating system.

  2. Check for the installation status of the VMware Tools.

  3. Shut down the virtual machines.

  4. Backup Hyper-V virtual machine configuration including the linked virtual hard disk files.

  5. Restore the VM configuration to Copaco VMware Cloud and convert and relink the Virtual hard disk files.

  6. Start virtual machines.

  7. Reconfigure network adapters with source IP configuration. (If local admin credentials are provided)

  8. Run provided test scenario’s to check if VM’s are available and the operating system can successfully boot. (If local admin credentials are provided)

Once migration is completed we will contact the partner to let them known migration has been completed and we request you to continue with the partner post-migration actions. We will leave the Hyper-V environment intact in a stopped state to provide a quick rollback scenario in case of major issues.

Actions for Partner post-migration

Once you have received the notification from Copaco Cloud Support about the migration completion, you can log in to the VMware Cloud Direct control panel to access the Virtual Datacenter infrastructure. You will see the new vApps and VM’s running in the environment. We recommend that you review the following items.


After migration, you should test if all servers and applications are starting as expected and all services hosted on the environment are accessible again. In case of immediate problems that need assistance from Copaco Cloud Support, please reply to the migration case as soon as possible. We are here to assist you. In case of emergency, we can roll back the migration and restart the Hyper-V environment.

Update DNS names

Please Note: In case you requested to keep existing Public IP addresses and Copaco Cloud Support confirmed that it is possible to migrate your old IP configuration, this section does not apply to you.

Your VMware Edge gateway has been assigned a new Public IP address unless explicitly agreed upon before migration. If your virtual environment is exposed to the internet you will need to update your DNS records and point them to the new IP of the Edge gateway.

If you have temporarily lowered the TTL on your domains for fast change detection, you can now restore to the original TTL value.

(Optionally) Update route to new VPN tunnel

If your customer uses site-2-site VPN tunnels this is the time to update the customer's router/VPN device onsite to re-route traffic through the new VPN tunnel.

Check for updates on VMware Tools

If your virtual machines are recently migrated, there will probably be new versions of VMware integrations tools available. We recommend that you install the new version of drivers as soon as they become available in your VMware Cloud Director portal. For more details please see KB:

Cancel the old Hyper-V subscription

Once the customer is happy with the migrated environment and everything has been running successfully for a few days we can clean up the old infrastructure and subscriptions.

You need to place a cancelation order for the old Copaco Hyper-V Cloud or Windows Azure Pack subscription to avoid duplicate subscription costs. You can also request the Copaco Cloud support team to clean up the old environment on your behalf. Please note that after cancelation a rollback to Hyper-V is no longer possible. KB available on:

If you migrated from a Windows Azure Pack subscription, you might also have a separate subscription for SPLA licensing. Please also submit a cancelation request for this separate subscription and order new SPLA licensing using the Copaco VMware Cloud subscription.