OVERVIEW
This article explains the VMware to Nutanix (V2N) Migration Project, including why SFU is moving from VMware to Nutanix, what’s changing for VM owners, and what to expect during the migration period.
Introduction to the VMware to Nutanix (V2N) Migration project
The VMware to Nutanix Migration project will update how SFU runs its cloud systems. SFU is changing from VMware to a new platform called Nutanix because VMware has become much more expensive and SFU’s contract ends in 2026.
This project will upgrade equipment in SFU’s data centers, deploy Nutanix, move all virtual machines to Nutanix by November 30, 2026 and decommission all VMware clusters by December 31, 2026.
Upcoming Changes
For most users, SFU Cloud will work the same way as before, with only small changes to how it looks.
Here’s what is staying the same:
| Area |
What this means for you |
| Core VM functionality |
You can still request, run, and manage VMs in SFU Cloud |
| Portal capabilities |
Common tasks and workflows remain similar |
| Non‑production backups |
Not backed up by default on either platform |
| Powered‑off VMs |
Not backed up on either platform |
| Production VMs |
Automatically backed up (full backups), retention will be approximately 4 months. |
| Snapshots |
Snapshots are allowed and auto deleted after 48 hours. |
| Network & IP Addresses |
VMs will retain the same IP addresses after migration. |
What is the difference between VMware and Nutanix?
| Area |
Current State (VMware) |
Future State (Nutanix) |
| SFU Cloud Portal |
A familiar web-based SFU Cloud Portal, VMware interface for creating and managing VMs. |
New Nutanix-based cloud portal with a different look and modern interface, but very similar functionality for VM management |
| SFU Single Sign-On (CAS): Login & Security |
Login via SFU computing ID (AD credentials). Standard AD authentication. |
Login via SFU Single Sign-On (CAS) with MFA support. |
| Operating System Support |
Must run supported OS versions. |
Must run supported OS versions. |
FAQs
General
What is the VMware to Nutanix (V2N) Migration Project?
The VMware to Nutanix (V2N) Migration project is to update how SFU runs its cloud systems. SFU is moving all VMware-based VMs to Nutanix, upgrading our cloud infrastructure for improved cost and performance.
Why are we migrating from VMware to Nutanix?
SFU is changing from VMware to a new platform called Nutanix because VMware has become much more expensive and SFU’s contract ends in 2026. This project will upgrade equipment in SFU’s data centers, move all virtual machines to the new platform, and decommission all VMware clusters by the end of the year.
What is the timeline for migration?
The migration timeline is from July 1 to November 30, 2026.
Access and Data Retention
Will we lose access to VMs that are not migrated?
Yes, VMs left on VMware after December 2026 will be inaccessible.
Will VMs left on vmware beyond December 2026 be permanently deleted or archived after migration?
Backup retention is 4 months for Powered On Production VMs. We can restore data (files) from those backups 4 months after the last backup. There is no backup or retention for non-production VMs
Are powered-off VMs backed up?
No, only running, production VMs are backed up; powered-off VMs are not included in backups. If needed in future, they must migrate to Nutanix.
can I restore VMs or data after migration?
You can restore data from VMware backups for 4 months after migration; full VM restores are generally not possible.
Migration Planning and Requirements
Is there a way to test my VM in Nutanix before the full migration?
You can deploy a new VM in Nutanix for testing.
What if I have a need to create new VMs during the migration period?
New VMs will be created on VMware until Nutanix is live; after mid-2026, new VM requests will be fulfilled on Nutanix.
How should Active Directory (AD) and MS SQL servers be migrated?
While Move can migrate Active Directory VMs, it is often recommended to create a new Domain Controller VM on the Nutanix side and migrate flexible single master operations (FSMO) roles to avoid potential sync issues.
For very large, high-transactional SQL servers, Nutanix recommends using standard SQL Server backup/restore methods or SQL Always On Availability Groups to migrate data, rather than a full VM migration. Failure to follow best practice might cause performance degradation.
Should I migrate VMs that are currently powered off but might be needed in the future?
Request a backup for these VMs, so it can be restored later, if needed.
If some virtual machines are migrated to Nutanix while other dependent VMs remain on VMware, will they continue to communicate with each other?
Yes they will continue to communicate with each other after migration. Dependent applications will be grouped and migrated together within the same maintenance window to minimize disruption.
Can VMs keep the same IP address after migration?
Yes, IP addresses will be preserved when migrating to Nutanix.
Support and Training
How will migration impact my daily operations?
We are aiming for minimal impact. Any outages will be managed through regular change management processes
Who can I contact for more information or support?
Submit a TDX ticket to the project team. Support is available throughout the migration.
Will there be training or documentation for using Nutanix?
Yes, user-friendly documentation and a training demo will be provided, including updated guides and FAQs.
NEED ADDITIONAL SUPPORT
Details Coming Soon!