Your Vendor’s Roadmap Is Not Your ERP Strategy

Why Higher Education Institutions Need an ERP and SIS Strategy Now, Even While the Market Is Still Re-Sorting

Blog 1 of 5  |  2,096 words  |  Approximately 10 minutes

This is the first article in our five-part series, ERP Strategy in a Re-Sorting Market.

Throughout this series, we will examine how colleges and universities can move forward while the higher education ERP and Student Information System market continues to evolve. We will explore the emerging technology and vendor paths, identify the modernization work institutions can begin now, explain how major decisions should be sequenced, and show how institutions can preserve flexibility as products and delivery models mature.

In this first article, we begin with the most important principle:

Vendor pressure and vendor moves are not institutional strategies.

That distinction matters now more than ever.

Higher education institutions are being told that the market is moving quickly, their current environments are becoming unsustainable, and the time to follow their incumbent vendor’s prescribed path is running out.

The urgency may sound convincing. Some of it may even be legitimate.

But a vendor roadmap describes where the vendor wants its customers to go. An institutional strategy defines where the institution needs to go, why it should go there, what problems it is trying to solve, and when each decision should be made.

Those are not necessarily the same destination, the same sequence, or the same timetable.

The Higher Education ERP and SIS Market Is Re-Sorting

For decades, the higher education ERP and SIS market was relatively stable. A small number of vendors dominated the market, institutional transitions were infrequent, and most colleges and universities assumed they would remain with their existing platforms for many years.

That stability is breaking down.

Cloud delivery models are changing. Traditional vendors are moving customers toward SaaS environments. Workday is becoming a more credible option for a broader segment of higher education. Oracle continues to develop its higher education capabilities. Institutions are considering composable architectures, specialized applications, public-cloud modernization, and domain-by-domain replacement strategies. EDUCAUSE’s 2025 Top 10 IT Issues report identified digital transformation and institutional agility as leading priorities, reflecting the urgency institutions feel about their enterprise technology futures.

At the same time, artificial intelligence, cybersecurity requirements, staffing shortages, data expectations, and financial pressures are changing what institutions need from their enterprise systems.

The market is not simply moving from one established model to another. It is re-sorting.

That creates uncertainty, but it also creates opportunity.

Institutions have more potential paths than they did a few years ago. They may also have more negotiating leverage. But taking advantage of those choices requires an institutional strategy that is independent of any single vendor’s commercial objectives.

Why Develop a Strategy Before the Market Settles? Digital Transformation Cannot Wait

Some institutions are tempted to wait.

They reason that the products are still evolving, vendor roadmaps remain uncertain, and there is no reason to begin planning until a clear market winner emerges.

That approach sounds cautious, but it carries significant risk.

Institutions are already making decisions about infrastructure, hosting, contracts, staffing, integrations, data, security, and operating models. Those decisions will shape what is possible five or ten years from now.

Doing nothing is still a decision.

A poorly considered contract extension may limit future leverage. A rushed SaaS commitment may eliminate alternatives. A lift-and-shift cloud migration may reproduce decades of technical debt in a more expensive environment. Continued neglect of integrations and data governance may make any future transition slower, riskier, and more costly.

The purpose of an ERP strategy is not to predict which vendor will eventually dominate the market.

The purpose is to ensure that the decisions made today support institutional priorities, reduce risk, and preserve future choices.

A good strategy allows an institution to move now without pretending that every long-term question can or should be answered now.

The Incumbent Vendor’s Strategy Is Understandably Vendor-Centered

Institutions should listen carefully to their incumbent vendors.

They should understand product roadmaps, support timelines, cloud plans, pricing changes, technical requirements, and future investment priorities. These are important inputs into institutional planning.

But they are still vendor inputs.

Every vendor has legitimate business objectives. Vendors want to move customers toward the products and delivery models that best support their own economics, development priorities, revenue predictability, and long-term market position.

There is nothing surprising about that.

The mistake occurs when an institution begins treating those vendor objectives as though they were institutional imperatives.

Higher education leaders may hear messages such as:

• Everyone is moving to SaaS.
• Your current model will not be sustainable.
• You need to get on the roadmap.
• Moving now will reduce your risk.
• Remaining where you are will become more expensive.
• Delaying may cause you to lose your place in the transition queue.
• The integrated suite is the only realistic long-term model.

Each statement should be examined carefully.

Some may prove accurate. Some may be exaggerated. Some may reflect a vendor’s preferred commercial outcome more than the institution’s actual operational needs.

The appropriate response is not automatic resistance. It is disciplined evaluation.

The institution should ask:

• What specific problem does this proposed move solve for us?
• Is the proposed destination fully mature and operational?
• Has it been proven at institutions comparable to ours?
• What functionality, access, or control would change?
• Which integrations would need to be rebuilt?
• What would the full transition cost be?
• What would the long-term total cost of ownership be?
• What options would this decision eliminate?
• Is the vendor’s timetable based on a genuine technical requirement or a commercial preference?
• Can our objectives be achieved through a smaller and more reversible step?

Vendor urgency should trigger analysis, not compliance.

An ERP Strategy Is Not a Product Selection or Vendor Selection

Another common mistake is assuming that an ERP strategy process must immediately result in the selection of a new product.

It should not.

Product selection may eventually be part of the process, but it should not be the starting point.

Before evaluating products, an institution should understand what it is trying to accomplish.

That requires answering more fundamental questions:

• Which institutional capabilities need to improve?
• Where are students, faculty, and employees experiencing unnecessary friction?
• Which business processes are overly complex or poorly documented?
• Which operational risks are no longer acceptable?
• Where does technical debt create cost or vulnerability?
• Which integrations are brittle, undocumented, or dependent on individual employees?
• How accessible, governed, and portable is institutional data?
• What level of vendor dependence is acceptable?
• What implementation and operational capacity does the institution realistically possess?
• Which decisions are urgent?
• Which decisions would benefit from additional product maturity or market evidence?

Only after these questions are answered should an institution begin comparing destinations.

Otherwise, the institution risks selecting a product first and then reshaping its strategy to justify the purchase.

Strategy Should Define Principles Before Products

Institutional priorities come first

Technology choices should be connected to measurable institutional objectives, not merely to vendor lifecycle events.

Delivered capability matters more than roadmap promises

Institutions should evaluate what is operational and proven, while treating future commitments as possibilities rather than certainties.

Data must remain an institutional asset

Institutions should retain practical access to their data and understand how it can be extracted, integrated, governed, and moved.

Integration must be treated as a strategic capability

No modern institution operates entirely within one application suite. Integration architecture, API management, identity, and data movement will remain essential regardless of the selected platform.

Major decisions should be reversible when practical

Institutions should avoid unnecessary lock-in and understand the cost and mechanics of changing direction.

Total cost must include the transition period

The cost of a new platform includes implementation, integration redesign, process change, temporary duplication, staffing, consulting, training, and the period in which old and new environments operate simultaneously.

Institutional readiness matters as much as product readiness

Even an excellent product can become a failed implementation if governance, staffing, processes, data, or executive sponsorship are not ready.

These principles create a decision framework that can be applied consistently as the market evolves.

How to Get Started: Building Your ERP Assessment

An ERP strategy does not need to begin with a massive, multiyear consulting exercise.

It can begin with a focused and disciplined assessment.

1. Establish the Right Governance Group

ERP and SIS strategy cannot be owned by information technology alone.

The process should include representation from:

• Executive leadership
• Academic affairs
• Student services
• Finance
• Human resources
• Payroll
• Institutional research
• Information security
• Enterprise technology
• Procurement and legal
• Faculty and operational stakeholders where appropriate

The group should have clear authority, defined decision rights, and executive sponsorship.

Its first responsibility is not to select a vendor. It is to establish what the institution needs from its enterprise environment.

2. Create an Honest Current-State Assessment

Document the environment as it actually exists, not as organizational charts and system diagrams suggest that it exists.

The assessment should identify:

• Major institutional pain points
• Current technology and operating costs
• Aging or unsupported components
• Security and resilience risks
• Critical customizations
• Manual workarounds
• Integration dependencies
• Data-quality problems
• Key-person dependencies
• Process inconsistencies
• Contractual constraints
• Staffing and skills gaps

This assessment creates a factual basis for strategy and helps prevent the loudest complaint or most persuasive vendor from controlling the conversation. For institutions running Ellucian Banner, our Banner consulting services can support this current-state evaluation.

3. Separate Immediate Needs From Long-Term Platform Questions

Not every problem requires a new ERP.

Some challenges can be addressed through process redesign, integration improvement, data governance, automation, infrastructure modernization, better reporting, or targeted applications.

The institution should divide its needs into categories:

• Problems that require immediate action
• Problems that can be solved within the current environment
• Problems that may require a platform change
• Problems that cannot yet be evaluated because the market or institution is not ready

This prevents every operational frustration from becoming an argument for wholesale replacement.

4. Define Strategic Guardrails

Before evaluating specific products, establish the standards any future solution must meet.

These might include:

• Data portability
• Open and well-documented APIs
• Strong security and identity capabilities
• Demonstrated scalability and resilience
• Clear total-cost transparency
• Implementation alternatives
• Reasonable exit provisions
• Support for institutional reporting and analytics
• Reduced dependence on customization
• A realistic path for integration
• Evidence from comparable institutions
• An acceptable long-term operating model

These guardrails help the institution evaluate vendor proposals on its own terms.

5. Build a Sequenced Roadmap

The roadmap should not force every decision into the same project.

It should distinguish among:

• Work that should begin immediately
• Decisions that can be made soon
• Questions that require investigation
• Decisions that should wait for stronger evidence
• Conditions that would trigger future action

For any decision that is intentionally deferred, the strategy should specify:

• Why the institution is waiting
• What information is missing
• What market developments will be monitored
• When the question will be reviewed again
• What work will continue in the meantime

Waiting with defined conditions is strategy.

Waiting without a plan is avoidance.

What the Strategy Should Produce

A useful ERP and SIS strategy should result in more than a generic recommendation to “move to the cloud” or “prepare for SaaS.”

It should produce:

• A clear statement of institutional objectives
• A current-state capability and risk assessment
• Guiding technology and architectural principles
• A data and integration strategy
• A modernization agenda
• A governance and decision-making model
• A sequenced roadmap
• Product-evaluation criteria
• Decision gates and review points
• A financial framework based on total cost of ownership
• A clear description of the options the institution intends to preserve

Most importantly, the strategy should give institutional leaders a framework for responding when vendors, products, prices, or market conditions change.

Do Not Confuse Urgency with Strategy

Higher education institutions should not ignore changes in the ERP and SIS market. Incumbent-vendor moves, product transitions, and support timelines may require action.

But action should follow institutional strategy, not replace it.

The question is not whether the market is changing. It clearly is.

The question is who will control the institution’s response.

Will the institution define its own objectives, decision criteria, timetable, and sequence?

Or will it inherit those decisions from the vendor that has the greatest financial interest in directing the outcome?

The strongest institutions will listen to their vendors, evaluate every credible path, and make deliberate progress. But they will not allow vendor pressure to become institutional strategy.

The market may still be re-sorting.

Your strategy should not be.

Coming Next

In the second article in this five-part series, we will examine the emerging ERP and SIS paths available to higher education institutions. For institutions evaluating their Workday options alongside Banner, our Workday services page provides additional context on our firm’s capabilities.

We will look beyond the false choice between remaining exactly where you are and automatically following the incumbent vendor into its preferred SaaS destination. We will explore public-cloud modernization, incumbent SaaS offerings, Workday, Oracle, composable architectures, and the possibility of making different decisions for finance, HR, payroll, and student systems.

The goal is not to declare a universal winner.

It is to understand the choices, their relative maturity, and the institutional conditions under which each path may make sense.