IT Infrastructure Migration Project

IT Infrastructure Migration Project. Blue banner with image of computer network.

IT Services will be completing a university-wide infrastructure initiative to migrate all university system platforms. This project will begin in February 2026 and continue into the summer, with all migrations completed by August 2026.

Many of the applications and services used across campus operate on the infrastructure included in this migration. These systems will require brief, planned downtime, which will be scheduled in advance. As a result:

  • Planned system outages will be scheduled in consultation with impacted areas to minimize disruption.  
  • Each affected application will require one scheduled outage; applications with associated databases may require two or more.
  • The average outage is expected to last between one and two hours, depending on the size and complexity of the virtual machine this could be longer.
  • Migrations will occur behind the scenes, with little to no action required from you.

This project is a key step in modernizing our technological environment. Migrating the system platforms will allow the institution to reduce licensing costs and make better use of our existing technological investments. Our goal is to ensure a smooth transition with minimal impact on operations, while strengthening the reliability and sustainability of the University’s technology environment.

We appreciate your cooperation and partnership as we complete this critical infrastructure improvement. 

Frequently Asked Questions

The IT Infrastructure Migration Project is a university‑wide initiative led by IT Services to modernize and strengthen the institution’s technology environment. As part of this initiative, all University virtual machines (VMs) will be migrated from VMware to Oracle Linux Virtualization Manager (OLVM).

This migration involves:

  • Establishing the new OLVM platform and preparing the servers that will host the migrated virtual machines.
  • Copying, converting, and validating each virtual machine to ensure compatibility with the new environment.
  • Recreating the necessary network configurations and storage connections required for each system.
  • Verifying that all applications and services continue to function as expected once migrated.

The goal of this project is to transition university systems to a more sustainable, cost-effective, and reliable infrastructure with minimal disruption to operations.

A helpful way to understand the migration is to think of it like moving from one apartment building to another. First, we need to make sure the new building is fully ready. Then we move each individual “apartment” (VM), reconnect all the “utilities” (network, storage, access), and verify everything works the same way it did before. 

The migration will begin in February 2026 and continue through the summer, with all migrations completed by August 2026.

Migrating to updated system platforms will help the university:

  • Reduce licensing and operating costs
  • Make better use of existing technology investments
  • Strengthen the long‑term stability of our IT environment

Yes. Many applications and services require brief, planned outages while they are migrated to the new infrastructure. 

Most outages will last 1–2 hours. However, systems running on larger or more complex virtual machines may require slightly longer downtime. 

Each application will require at least one planned outage. Applications with associated databases may require two or more planned outages. 

  

Outages will be planned in consultation with impacted departments to reduce disruption and avoid peak operational periods whenever possible. 

In most cases, no action is required. The migration work happens behind the scenes. You will simply need to avoid using affected systems during the scheduled outage windows. 

Affected users or departments will be notified well in advance with details on timing, impact, and what to expect. 

Each application has a dedicated system analyst who will coordinate the migration for the application and related servers.  

 

Tentative Migration Outage Schedule:

Application, Service, or System Name Tentative Maintenance Date & Time
AIMS  TBD
Brightspace TBD   
Central Policies Index TBD
Collections TBD
Connect One  TBD
Create Form TBD
Crystal Reports TBD
CuMA TBD
Dabble TBD
DEAP TBD
Destiny  TBD
Domino / Legacy ARAC Forms Workflow TBD
Ecostruxure  TBD
Equipment Booking TBD
Event Worx TBD
FLEX License Manager TBD
Genetec TBD
GitLab TBD
Go Print TBD
Grade Flow TBD
Honeywell Energy Management System TBD
IBM Cognos Planning Analytics TBD
Infosilem TBD
Intuem TBD
Key Control TBD
Konnect Sys TBD
Law OLAS Reader TBD
Law Library EZ Proxy TBD
Leddy Library EZ Proxy  TBD
Leddy Library Website TBD
Lift Net TBD
Lutron TBD
Miles TBD
MySuccess TBD
Nursing CPE TBD
Odyssey PCS TBD
PaperCut TBD
Pivot Pro Request TBD
Ready Trak TBD
Required Training TBD
SAS TBD
Scholars Portal  TBD
Titanium TBD
UCAPT TBD
University Website (Drupal)  TBD
UWin Account Services TBD
UWinsite Student  TBD
Workshops TBD
ZMS Gate Control  TBD
ZEAG TBD