Before You Choose a New ERP, Decide What Success Looks Like.

Watch Video

Written by Doctums Staff

Ask an IT leader in higher education whether their institution will move its ERP to SaaS, and the honest answer is increasingly “when,” not “if.” Most of the institutions we work with are somewhere between early planning and active transition. That part is rarely in question anymore.

‍

What is still in question is how they’ll get there, and whether the institution will actually run better on the other side. That outcome is mostly decided before a single system is selected.

Why the move is coming either way

The pressure on institutions isn’t coming from one direction. Maintaining a server room is expensive, and getting funding approved on a reasonable replacement cycle gets harder every budget season. Keeping student and employee data on local servers carries real risk, and most institutions can’t hire the security expertise to manage it alone. Meanwhile, more and more higher ed software is no longer sold for local installation at all.

‍

“Very few institutions will be able to avoid moving to SaaS. Even the ones still in planning will eventually have to make the leap, whether they decide to change systems or their current system changes how it’s licensed and supported.”

— Connie Atchley, Senior Consultant, Doctums

‍

The scale of the work has changed too.

‍

“Gone are the days when an IT team managed ten servers. Today they’re keeping hundreds of physical and virtual machines patched and secure, and finding qualified people to do that keeps getting harder.”

— Sulema Cabrera, Senior Consultant, Doctums

‍

That talent gap isn’t new, and it isn’t only about headcount. We wrote about what institutions actually lose when experienced IT staff move on.

‍

What modernization actually means

When an institution tells us it wants to modernize, it usually means one of two things: moving to SaaS and needing a trusted advisor along the way, or getting more out of the student information system it already has. Either way, the conversation starts in the same place.

‍

“Modernization isn’t simply about moving from an on-premises system to the cloud. It’s about stepping back, understanding where an institution is today, and figuring out how technology, processes, and people can work together to get where it wants to go. Our goal is to help institutions make decisions that set them up for the long term, not just get them through a migration.”

— Heather Harrison, Director of Advisory Services, Doctums

‍

Why the system is rarely the problem

EDUCAUSE research on ERP implementations in higher education makes a point institutions often learn too late: go-live shouldn’t be the measure of success. Customizations and the design of future business processes are among the biggest hurdles, and each institution has to define what success means for itself. In our experience, the software is rarely what holds a project back.

‍

The reason is usually what institutions bring with them. Years of workarounds, custom modifications, and processes that exist because “that’s how we’ve always done it” don’t disappear in a new system. Cloud ERP leaves less room for deep customization, which forces institutions to reconcile workflows that never matched across departments in the first place, as ERP Today has reported. If those differences aren’t addressed early, they surface mid-project, when they’re most expensive to fix.

‍

We’ve seen the same pattern in how community colleges are handling outcomes-based funding: a decade of workarounds stays invisible until something forces the data to hold up.

‍

What to assess before you select

None of this requires waiting until a contract is signed. The most valuable work happens before selection, and it starts with an honest look at the current state.

‍

How work actually gets done today. 

That means existing workflows, data quality, integrations, and institutional requirements, not how the system is supposed to work in theory.

‍

What should change and what should carry forward.

“If legacy processes get replicated without anyone asking why they exist, institutions end up carrying the same inefficiencies and complexity into the new ERP. The honest conversation about what should change versus what should carry forward is the one that gets skipped most.”

— Heather Harrison, Director of Advisory Services, Doctums

‍

Where the friction is.

“Before anything else, we ask what’s working and what isn’t. Where are functional areas feeling the pain? What parts of the system aren’t being used today that could make people’s work easier? And can this modernization be tied directly to the institution’s strategic goals?”

— Sulema Cabrera, Senior Consultant, Doctums

‍

The reports you can’t live without. 

Every institution has reports it depends on for compliance, leadership, and day-to-day decisions. Building an inventory of must-have reports, and deciding whether the current reporting platform stays or goes, prevents some of the most disruptive surprises after go-live.

‍

Institutions that do this work first don’t just choose better. They choose with a clear definition of what success looks like, which is the only way to know later whether they got there.

‍

Where an independent advisor helps

As an independent higher education consulting firm, Doctums brings decades of experience with ERP and SIS platforms, and no system to sell. 

‍

“Before selection, we help institutions build the criteria they’ll use to evaluate vendors, and we can facilitate the decision as a neutral party. Because we’ve worked with these systems and these institutions for so long, we can bring insight into the conversation that wouldn’t otherwise be in the room.”

— Connie Atchley, Senior Consultant, Doctums

‍

From there, we support institutions through implementation and well after go-live.

‍

Go-live is not the finish line

Modernization will look different for every institution, but the ones that get the most from it share one thing: they defined success before they defined the system. In our next piece, we’ll look at what happens once the system is chosen, and why the real timeline is set by the institution, not the technology.

‍

If your institution is starting to plan its move, or you’re not sure where to begin, that’s exactly the conversation we’re glad to have.

‍

Talk to our team.

‍

Written by Doctums Staff

‍