The ITSM Modernization Path in Higher Education

ITSM modernization is not one project at most R1 institutions. It is three. The first is moving onto ServiceNow from a legacy ticketing system. The second is maturing within IT, which means consolidating service desks, unifying knowledge, completing the CMDB, and producing the metrics that IT leadership actually needs. The third is what happens after IT works. The move from ITSM-only to ITSM-plus, where Customer Service Management or HR Service Delivery joins the platform and ServiceNow stops being an IT tool and starts being an institutional workflow platform. The CIOs who get the most from ServiceNow recognize which moment they are in and what the next one looks like. This pillar is for all three.

Why higher ed ITSM modernization is not corporate ITSM modernization

ITSM modernization in higher education looks superficially like ITSM modernization anywhere. Replace the legacy queue. Stand up a service catalog. Define SLAs. Build a CMDB. Train the staff. The ITIL frameworks that anchor every corporate IT modernization apply here too.

But five structural conditions, the same ones we documented in our Pillar 1 piece on orchestration, apply at the ITSM scale and change what modernization actually means.

Federated IT comes first. At a typical R1, central IT shares the institution with college IT teams, library IT, ResLife, athletics IT, the medical campus, and a research computing group that may report to the Provost rather than the CIO. Each runs its own help desk, its own KB, its own ticket queue. Modernizing the central IT desk does not modernize the institution.

Faculty governance comes second. Major IT changes touch faculty workflows. The ITSM platform decision usually does not require senate approval, but the workflow changes that follow often do. The CIO who modernizes the help desk without the political work has a working tool that staff and faculty refuse to use.

The third condition is the multi-decade integration debt with Banner, PeopleSoft, Workday, and the homegrown systems that surround them. Every ITSM workflow that touches identity, course enrollment, employee status, or financial data depends on integrations that were built across two decades by people who, in many cases, have retired. Modernizing means inheriting that complexity, not avoiding it.

Cycle-time constraints come fourth. The registrar's deadlines, the payroll runs, the federal compliance windows. IT services have to be available across all of them. ITSM modernization cannot take the institution offline.

Identity attachment is fifth. The current ticketing system and the team that runs it have been there a long time. The Director of IT Service Management, the senior help desk staff, the platform owners — these are the people whose professional reputations are tied to the current system. Modernization that does not bring them along produces resistance that no platform change can overcome.

These five conditions compound. They are why corporate ITSM modernization timelines do not transfer to higher education, and why the modernization conversation in this sector benefits from being broken into the three distinct moments below.

Moment 1: First implementation

For institutions still running Cherwell, BMC Remedy, Ivanti, ServiceDesk Plus, or a homegrown queue.

The first ITSM modernization moment is the move onto ServiceNow itself. At R1 institutions, this typically follows a familiar shape. A legacy contract is up for renewal, a vendor end-of-life is announced, or a new CIO arrives and inherits a tool the IT leadership team has wanted to replace for years. The institution runs a procurement, evaluates the major ServiceNow alternatives, and lands on ServiceNow because the platform's roadmap, the ServiceNow higher ed customer base, and the workflow extensibility outweigh the alternatives.

What the first implementation actually looks like in higher education comes down to four decisions.

The first is which service desk goes first. Almost always central IT, because that is the team that owns the platform decision. The federated desks (college IT, library IT, ResLife) typically do not migrate in this phase. They watch.

The second is configuration versus customization. The institutions that succeed in the first implementation configure to the platform's standard model and resist customization in the early months. The institutions that struggle bring decades of legacy workflow into the new platform on day one and end up with a ServiceNow instance that mirrors the system they replaced.

The third is the integration scope. Active Directory and the IdP at minimum. Email and calendar usually. Banner or PeopleSoft for limited workflow context (employee status, course enrollment) where the ITSM workflow needs it. The full integration roadmap belongs to Moment 2.

The fourth is the metric the CIO commits to. First-call resolution rate, mean time to resolve, customer satisfaction, ticket volume by category. Pick two. Defend them. The metric the CIO commits to in Moment 1 is the one that justifies Moment 2.

A realistic Moment 1 timeline runs 6 to 12 months from contract to go-live. The institutions that run it well treat the first implementation as the proof, not the destination. They land cleanly, produce baseline data, and earn the right to come back for the next phase.

Moment 2: Maturing within IT

For institutions running ServiceNow ITSM today and not yet getting full leverage from it.

Most R1 institutions live here. The platform is in production. The help desk uses it. Tickets get logged, routed, and resolved. But the institution is using maybe 40 percent of what ServiceNow ITSM can deliver, and the leadership team can feel the gap without always being able to name it.

Three sub-patterns define what maturing within IT actually means.

Sub-pattern 1: Multi-service-desk consolidation. The college IT desk runs in parallel to the central IT desk. The library IT desk runs separately. ResLife runs its own queue. The medical campus has its own ITSM instance. Faculty and staff who cross departments file the same kinds of tickets in three different systems. Each desk makes sense in isolation and makes no sense in aggregate. The consolidation work is operationally hard and politically harder, but it is the move that turns ServiceNow from "central IT's tool" into "the institution's IT platform." Our forthcoming cluster on multi-service-desk consolidation walks through the pattern in production.

Sub-pattern 2: Unified knowledge. The KB sprawl problem is rampant. Confluence runs in central IT. SharePoint is the official institutional KB but nobody uses it. Notion lives in one team. The legacy ServiceNow Knowledge15 articles were never migrated to the modern KB module. Faculty Google for the answer instead of opening a ticket because they cannot find the article that exists. Our forthcoming cluster on knowledge management covers the strategy and migration path.

Sub-pattern 3: Getting more out of ITSM Pro, or upgrading from Standard. Many institutions have ITSM Pro and use a fraction of what they paid for. Predictive intelligence, performance analytics, virtual agent, agent workspace, mobile agent — features that are licensed but not deployed. Other institutions are on Standard and starting to feel the ceiling. The Pro-versus-Standard decision is well-trodden in corporate IT but takes a different shape in higher education, where the audience volume, the seasonal patterns, and the federated structure all change the math. Our cluster on ITSM Pro versus Standard for higher ed handles this directly.

The CMDB question lives in Moment 2 too, but it earns its own treatment in Pillar 7 on ITOM and CMDB Health rather than getting compressed into a paragraph here.

What ties these three sub-patterns together is the same observation EDUCAUSE made in the 2026 Top 10. Technology professionals consistently report that their workloads exceed capacity, their teams are understaffed, and that, despite these realities, their institution still demands they maintain the same levels of service and continue to do more with less.

The institutions that mature within IT do so because the operational gap between what IT is asked to deliver and what IT has the capacity to deliver gets too wide to ignore. Maturing the ITSM practice is how that gap narrows.

Moment 3: Expanding beyond IT

For institutions where ITSM is delivering and the conversation is shifting to what is next.

This is the moment where ServiceNow stops being an IT tool and starts being an institutional workflow platform. It is also the moment that defines whether the institution gets the full economic and operational return on the ServiceNow investment, or whether ServiceNow becomes another vendor relationship the institution maintains without maximizing.

The signals that say it is time are five, in our experience.

The first is that ITSM is delivering and the help desk is no longer the highest-pain workflow. The CIO's leadership team has bandwidth that did not exist eighteen months ago. The platform's reputation inside the institution has shifted from "the new ticketing system" to "the way we do work."

The second is that a non-IT department has asked, on its own, whether ServiceNow could solve a workflow problem they have. Often it is HR after a particularly painful onboarding cycle. Sometimes it is the Provost's office after a sabbatical-tracking spreadsheet falls apart. Occasionally it is Facilities. The question never comes from the same place twice, and it is always the most reliable signal that Moment 3 is open.

The third is that the platform team has capacity that is not being used. The team that built the IT service catalog has the skills to build a faculty onboarding workflow. The team that maintains the integration to Banner can extend it for an HR use case. The capacity exists. The pipeline of work to use it does not yet.

The fourth is that cabinet-level conversations about institutional experience are happening. The Provost and the COO are talking about how it feels to be a faculty member at the institution. The CHRO is being asked about employee engagement scores. Student affairs is presenting on the student experience. These conversations point toward orchestration even when the cabinet members involved have never used the word.

The fifth is that the CIO has political credit to spend on a non-IT initiative. ITSM has worked. The CIO is trusted. The next platform decision is going to draw on that trust rather than build it from scratch.

If three of these five signals are true, the institution is at Moment 3. The decision is no longer whether to expand. It is which adjacent domain to expand into, and how to bring the senate along, which our cluster on faculty governance and platform decisions walks through directly.

The most common first expansion is Customer Service Management. CSM applies the same case management spine that ITSM uses, but to non-IT customer-facing workflows: student services, advising, financial aid, conduct cases, alumni engagement. The CSM-versus-ITSM-extension decision is its own conversation, which we cover in our forthcoming cluster on ITSM to CSM.

The other common first expansion is HR Service Delivery, which connects to the broader Employee Workflows roadmap we walked through in our post on scaling ServiceNow beyond ITSM.

Both paths land at the same place: ServiceNow as the institutional workflow platform, with ITSM as the launchpad rather than the ceiling.

The higher ed ITSM maturity model

A diagnostic for placing the institution on the path between Moments 1, 2, and 3.

Stage 1: Reactive. Tickets in shared inboxes or homegrown queues. No ITSM platform. Modernization has not started.

Stage 2: Implemented. ServiceNow ITSM is live but mostly mirrors the workflow of the system it replaced. SLAs are defined but inconsistently enforced. Reporting exists but is not trusted.

Stage 3: Operating. Real SLAs, real reporting, IT leadership trusts the data. The help desk is performing. The CMDB is partially populated. ITSM Pro features are licensed but not fully deployed.

Stage 4: Mature. Multiple service desks consolidated, KB unified, CMDB usable, ITSM Pro features actively used. Predictive intelligence and performance analytics are running. Virtual agent is deflecting tickets. The platform team is operating at the practice's published reference level.

Stage 5: Expanding. ServiceNow is moving beyond IT. Cabinet-level conversations are happening. CSM, HRSD, or Workplace Service Delivery is in some stage of evaluation, pilot, or production. ITSM is no longer the only workload on the platform.

Stage 5 is where Beyond the Help Desk becomes the next read.

Most R1 institutions self-assess as Stage 3 (Operating) and are actually Stage 2 (Implemented) on the rigorous version of the model. The honest assessment is uncomfortable but useful: it is the version that produces a real Moment 2 program rather than the version that produces another self-congratulatory readout to the cabinet.

What ITSM modernization actually delivers

Concrete outcomes by moment. The CIO who can bring this list to a board meeting has the language for the modernization conversation that gets funded.

Moment 1 outcomes. Unified ticketing on a single platform. Real SLAs that the institution actually measures. The retired legacy contract. Baseline operational data that does not exist before the move.

Moment 2 outcomes. One front door for IT services, regardless of which IT team owns the underlying work. A real CMDB that supports incident, change, and problem management with confidence. Trusted metrics that IT leadership uses to make staffing and investment decisions. Faster mean time to resolve. Measurable customer satisfaction. Knowledge that staff and faculty can find. ITSM Pro features that are deployed rather than licensed-and-shelved.

Moment 3 outcomes. Student case management running on the same platform as the help desk. Cross-functional onboarding workflows that touch HR, IT, Facilities, Library, and Department in parallel. An institutional experience that feels like one university rather than fifteen disconnected offices. Real return on the platform investment.

Each moment produces measurable outcomes. None of them require waiting until the end to produce evidence. This is what makes the modernization conversation winnable in higher education, where five-year programs without intermediate proof points have largely lost the right to be funded.

A diagnostic: which moment are you in?

Three questions that map the reader to a moment and a next step.

The first. Do you have ServiceNow ITSM running today? If no, you are at Moment 1, and our cluster on ITSM Pro versus Standard is the procurement-stage read. If yes, continue.

The second. Is your ITSM operationally mature, meaning one consolidated service desk, a unified KB, a usable CMDB, and trusted metrics that your IT leadership team relies on for staffing and investment decisions? If no, you are at Moment 2. The posts on service desk consolidation and unified knowledge are the next reads.

The third. Is at least one non-IT cabinet member asking, on their own, whether ServiceNow could solve a workflow problem in their domain? If yes, you are at Moment 3. The cluster on ITSM to CSM and our Pillar 1 piece on orchestration are the next reads, and Beyond the Help Desk is the long-form version of the case.

The diagnostic is unsexy on purpose. It is what produces a credible internal answer to "where are we, and what is the next move."

Frequently asked questions

How long does first implementation actually take?

Six to twelve months from contract to go-live for the central IT service desk at a typical R1. Federated desks (college IT, library IT, ResLife) typically migrate later, in Moment 2's consolidation work.

We have ServiceNow ITSM but barely use it. Where do we start?

Run the Stage 2-versus-Stage 3 diagnostic above honestly. Most institutions that say "we barely use it" are at Stage 2 (Implemented), and the work is to get to Stage 3 (Operating) before tackling the consolidation and KB work that defines Stage 4. The cluster on ITSM Pro versus Standard helps if licensing is part of the question.

Do we need ITSM Pro to get to Moment 2?

No, but the path is harder without it. Many of the features that define a mature ITSM practice in higher education (predictive intelligence, performance analytics, agent workspace, virtual agent) are Pro-tier features. Standard institutions that mature within IT typically reach a ceiling that drives the upgrade conversation.

What does it cost to consolidate multiple service desks?

Less than the institution thinks, in most cases. The ServiceNow license usually covers it. The cost is in the change management work and the political work with the federated desk owners, not the platform.

How do we know we are ready for CSM?

Three of the five Moment 3 signals are true. The cluster on ITSM to CSM has the longer answer.

What happens to our existing KB systems if we migrate?

Migration patterns vary by source system. Confluence is the most common source and has well-understood export-and-import paths to ServiceNow Knowledge. SharePoint and Notion are harder. Knowledge15 (the legacy ServiceNow KB module) is straightforward to migrate to the modern KB. The forthcoming knowledge management cluster handles each pattern.

Where this leaves the institution

Higher ed ITSM modernization is rarely a single decision. It is a sequence of three, and the institutions that recognize the sequence run the modernization program meaningfully better than the institutions that treat each phase as a separate project.

The most transformative CIOs we have worked with do not stop at Moment 2. They use the operational success of mature ITSM as the evidence that earns the cross-institutional conversation. ITSM is necessary. ITSM is not sufficient.

For the broader case for ServiceNow as an institutional workflow platform, our Pillar 1 piece on orchestration is the foundation.

The full case is in our Beyond the Help Desk white paper.

If you want a working session on which moment you are in and what the next one looks like, that is what we do.

Bettera is the only ServiceNow consulting partner focused exclusively on higher education.