Migration from MAX and Dynamics embedded E2 Agent to NICE CXone
How do you migrate an end-of-life shadow IT platform to a new one, with little to no domain knowledge to start from?
TLDR;
I took over an end-of-life shadow IT platform with almost no documentation, learnt the domain fast, and moved Student Support and Student Administration teams onto NICE CXOne without disrupting service.
What I learned
- Users are the best source of domain knowledge. It is the people and teams using the platform every day that reveal critical workflows, dependencies and nuances that may not be documented or understood by technical owners.
- Never assume functionality will work as expected. Thorough UAT is essential for identifying integration gaps and validating real-world scenarios before cutover.
- The same platform can support very different ways of working. Even when teams use the same platforms, their processes can be different. Delivery, change management and hypercare need to account for those differences.
Outcomes
- Retired legacy shadow IT platforms: Migrated both colleges away from MAX ahead of its end-of-life deadline.
- Simplified the contact centre environment: Consolidated contact centre capabilities into a more consistent solution, reducing the overhead of maintaining separate platforms.
- Improved CRM integration: Enabled student interactions to be recorded through CXone's Dynamics integration, supporting more complete interaction data and future reporting insights.
- Maintained business continuity: Completed the migration without impacting university operations.
Context
Student Services teams at Torrens University Australia (TUA) and Media Design School (MDS) used two contact centre platforms to communicate with students via calls, SMS and chat: NICE MAX, a standalone contact centre, and E2 Agent, embedded within Dynamics CRM.
Problem
NICE announced that MAX would reach end of life before the end of 2026, creating a deadline to migrate. Both MAX and E2 Agent operated as shadow IT platforms, with limited documented knowledge of their configurations, integrations and usage. Maintaining two platforms that delivered similar functionality also created unnecessary operational overhead. The challenge was to migrate away from MAX while determining whether consolidating both platforms into CXone would provide a better long-term solution.
My role
As Product Owner for Student Experience and Support, I was responsible for understanding the existing platforms, defining the target state and coordinating delivery. I worked across internal technology teams, Student Services, NICE and its implementation partner to manage the migration, including requirements gathering, UAT, cutover and hypercare.
Discovery
Discovery revealed that the two colleges used the platforms differently, requiring tailored migration approaches. MDS primarily used MAX for inbound and outbound calls, while TUA relied on calls, SMS and chat. TUA also used MAX alongside E2 Agent to ensure student interactions were recorded in Dynamics CRM. In practice, staff initiated communications through MAX while keeping E2 Agent open to maintain the CRM integration. With limited documentation and platform knowledge, I worked with the teams who used the systems day to day to understand existing workflows, configurations and dependencies. This uncovered operational requirements that needed to be preserved throughout the migration.
Options and trade-offs
Migrating away from MAX was mandatory due to its end-of-life date. However, E2 Agent had no defined end-of-support date, leaving a decision about whether to migrate one or both platforms. Option 1: Migrate MAX only Pros: Smaller scope, lower delivery effort and cost, and a simpler migration using NICE's established implementation process. Cons: Continued reliance on two platforms, ongoing maintenance overhead, a fragmented Dynamics CRM integration, and limited access to the benefits of CXone embedded within Dynamics. Option 2: Migrate both MAX and E2 Agent Pros: Consolidated contact centre capabilities, a more seamless Dynamics CRM integration, reduced platform maintenance overhead, and access to CXone's embedded functionality. Cons: Greater scope and complexity, requiring additional coordination, testing and change management across both colleges.
Solution and delivery
I supported the decision to migrate both colleges to a consolidated CXone solution: the standalone CXone Agent for relevant workflows and CXone embedded within Dynamics CRM. I coordinated internal technology teams, NICE's implementation team and Student Services stakeholders to validate existing workflows, manage UAT and prepare for cutover. The migration approach accounted for the different ways TUA and MDS used the platforms, with tailored rollout and support arrangements to minimise disruption.