Salesforce to ServiceNow Migration in Higher Education: Why R1 Institutions Are Rethinking Their Education Cloud Investment

TLDRIf your institution has been running ServiceNow for ITSM or CSM and Salesforce for advancement, admissions, or student success, you may not have stepped back recently to ask whether the platforms still match the institution you have become. A lot has changed since most R1 institutions adopted Salesforce Education Cloud. Pricing has changed. AI capability has changed. ServiceNow's CRM capability has changed materially. Tenon brings native marketing automation to the ServiceNow platform. Databricks brings the data backbone. The Salesforce to ServiceNow migration in higher education is the strategic platform evaluation that R1 CIOs should run before the next multi-year Salesforce renewal locks in another contract cycle on terms set when the institution was a different version of itself. This piece walks through the case for evaluation, the destination platform, and the four-phase migration sequence.

If your institution adopted Salesforce Education Cloud somewhere between 2018 and 2023, and your ServiceNow instance has been running ITSM or CSM in parallel ever since, you have probably not stepped back recently to ask whether the platforms still match the institution you have become.

A lot has changed since the original Salesforce decision. The platform has evolved. The pricing has evolved. Agentforce arrived and reshaped the AI conversation. ServiceNow's CRM capability expanded materially through 2025 and 2026. Tenon brought native marketing automation to the ServiceNow platform. Databricks established itself as the data and AI backbone of choice for higher education. None of these changes were on the table when the institution made its original Salesforce commitment. None of them automatically obligate the institution to migrate. But all of them are reasons to evaluate the platform posture deliberately before the next multi-year renewal locks in another contract cycle.

The institutions that have been running ServiceNow for ITSM or CSM for years have an under-appreciated asset. The platform investment is already in place. The operational expertise is already in place. The institutional governance posture is already in place. What most CIOs have not yet asked is whether the same platform that has been delivering for IT could absorb the CRM, advancement, and student success workloads that currently run on Salesforce, and what the institution would gain from that consolidation.

Bettera is the only ServiceNow consulting partner exclusively focused on higher education, and the Salesforce to ServiceNow migration evaluation is the Year 2 strategic engagement we lead for R1 institutions.

The destination is a four-product consolidated stack: ServiceNow as the CRM platform, Tenon as the marketing automation layer native to ServiceNow, AI Control Tower as the AI governance layer, and Databricks as the data backbone. This piece walks through the case for evaluation, what the destination platform actually delivers, the four-phase migration sequence, and the political playbook for bringing Advancement and the Cabinet along on the conversation.

Why now is the right time for higher education institutions to evaluate the Salesforce to ServiceNow migration question

Three structural reasons R1 institutions running Salesforce should evaluate the migration question now, before the next renewal cycle.

First: the platforms today are not the platforms you originally compared. Many institutions made their Salesforce Education Cloud commitments in the 2018-2023 window. At that time, ServiceNow was primarily an IT service management platform with limited CRM capability. Salesforce was the clear CRM choice. The decision was rational. Through 2025 and 2026, ServiceNow's CRM capability expanded materially, the Tenon partnership brought native marketing automation to the platform, AI Control Tower added a governance layer that did not exist when the original platform decision was made, and ServiceNow's commercial model bundled AI capabilities across every tier. None of this was on the institutional comparison sheet in 2020. All of it is on it now.

Second: the renewal cycle is a strategic decision point, not a procurement formality. Institutions hitting 3-5 year Salesforce renewals through 2026-2028 face a choice that most CIOs and CFOs do not frame as a choice. The default path is to renew on the existing terms with the AI sidecar bundled in. The deliberate path is to evaluate whether the platform still matches where the institution is going. Renewal is the natural inflection point because it is the moment when the institution is not yet locked into another contract cycle. Once the renewal is signed, the next evaluation window is 3-5 years away.

Third: the institutional AI consolidation argument changes the platform calculus. Our piece on higher education AI vendor consolidation walks through why five to ten AI sidecars across the institutional stack create compounding governance, integration, and contract burden. Salesforce + Agentforce is one of those sidecars. The institutions taking AI governance seriously are asking whether Salesforce should be the platform that survives consolidation, or whether the ServiceNow CRM + Tenon + AI Control Tower stack is the more defensible long-term posture.

The institutions that evaluate the question deliberately produce a better answer than the institutions that default to renewal. The evaluation itself is not a commitment to migrate. The evaluation is a commitment to make the next platform decision with the full picture of what is now possible.

A brief history of Salesforce in higher education

The migration evaluation lands more credibly with audiences who have been through Salesforce implementations and respect the platform. Salesforce has delivered real value at many R1 institutions over the past decade. The evaluation argument does not deny that history.

Salesforce's higher education trajectory has three phases.

The Salesforce.org era (pre-2021). Salesforce.org was the nonprofit arm. The Higher Education Data Architecture (HEDA) was the underlying data model. Institutions adopting Salesforce in this era did so primarily for advancement and admissions, with strong nonprofit-pricing terms and a partnership-oriented sales motion.

The Education Cloud era (2021-2024). Salesforce consolidated Salesforce.org into the main commercial organization and rebranded HEDA as the Education Cloud product family. The pricing model shifted toward commercial enterprise terms. The product capability expanded into student success and lifecycle management. Many R1 institutions made their largest Salesforce commitments in this window.

The Agentforce era (2024-present). Salesforce introduced Agentforce at Dreamforce 2024 as its primary agentic AI platform, replacing the older Einstein predictive layer. Agentforce expanded materially through 2025 and 2026 and is now the AI sidecar for every Salesforce workload, including the Education Cloud workloads.

The institutions that committed to Salesforce across these three phases built deep workflow integration. Advancement teams built donor journeys on Marketing Cloud. Admissions teams customized recruitment workflows. Student success teams operationalized retention.

The platform delivered.

What comes next is not a critique of the platform's history. It is an evaluation of the platform's fit for the next decade of institutional work.

The four pressure points that make this the right time to evaluate

Four structural pressures that turn this from a routine renewal into a deliberate evaluation.

Pricing pressure. Salesforce per-user license costs at scale, combined with Agentforce consumption pricing, are reaching levels that have institutional CFOs asking serious questions about cost per user and total annual platform spend. The trajectory of the cost is the conversation. The CFO does not need a specific dollar threshold to start asking the question. The trajectory itself is enough.

AI governance fragmentation. Agentforce is one of the AI sidecars described in our piece on higher education AI vendor consolidation. Salesforce's AI governance posture is separate from every other AI sidecar the institution runs. The General Counsel's FERPA-and-AI conversation described in our piece on FERPA and AI compliance happens once per vendor. Five AI sidecars means five separate FERPA-and-AI conversations. Salesforce is one of those five.

Data fragmentation between Salesforce and the rest of the institutional stack. Salesforce sits adjacent to the SIS, the ERP, the LMS, and the institutional workflow systems. The data path is integration-dependent and brittle. Each new institutional workflow that requires Salesforce data adds another integration point, another set of failure modes, and another conversation with the integration team. Institutions with ServiceNow already deployed for ITSM or CSM have a platform that can subsume the workflow layer without the data path fragility.

Renewal cycle convergence. Institutions that procured Salesforce in 2018-2023 are hitting 3-5 year renewals through 2026-2028. The renewal is the natural inflection point. The institutions that signed renewals in 2022-2023 had less pressure to question the platform. The institutions facing renewal in 2026-2028 are asking harder questions because the alternative platforms have evolved meaningfully in the intervening years.

These four pressures compound. The institution feeling one of them is having a conversation. The institution feeling all four is making a deliberate evaluation.

What ServiceNow as institutional CRM actually looks like

The destination platform. This is where the evaluation argument becomes concrete.

The destination is not just ServiceNow. The institutional CRM workload on ServiceNow depends on three additional layers: Tenon for marketing automation, AI Control Tower for AI governance, and Databricks for the data backbone. This four-product stack is what makes the Salesforce to ServiceNow migration argument credible for higher education.

ServiceNow as the CRM platform

Through Knowledge 2026, ServiceNow's CRM capability expanded materially. The Customer Service Management product family now covers institutional workflows that were previously Salesforce-native. Case management, interaction management, knowledge management, journey orchestration, and analytics all run on the platform that many R1 institutions already own and operate for ITSM or CSM. The expansion is not theoretical. Bettera has built advancement, student, and research agents that operate on this platform today.

Tenon as the marketing automation layer

Tenon is built natively on the ServiceNow platform. Not integrated with it. The distinction is operationally meaningful. Tenon's marketing automation capabilities (trigger-based journeys, drip campaigns, email and SMS, behavioral segmentation, A/B testing, customizable performance dashboards, GDPR compliance) run inside the same security boundary as the rest of the ServiceNow workload, with zero data sync latency and a unified governance posture.

For advancement teams whose biggest objection to migration is "but Marketing Cloud is how we run our giving campaigns and donor journeys," Tenon is the answer. Tenon delivers what Marketing Cloud delivers, native to the destination platform, with a tighter data path and unified governance. When the institution's AI governance posture extends to marketing workflows (FERPA-relevant student communications, donor segmentation that touches educational records, accommodation-aware communications), Tenon inherits that posture natively because it runs on the same platform. The deeper introduction to Tenon's role in the institutional architecture is in our Beyond the Help Desk white paper.

Now Assist and AI Control Tower as the AI layer

The strategic posture described in our piece on Now Assist in higher education AI governance and the platform deployment described in our piece on the ServiceNow AI Control Tower for higher education applies natively to all the migrated workloads. The governance posture follows the platform. The four FERPA edge cases get worked through once, not five times.

The worked example

The Bettera-built Alumni Agent demonstrates what the consolidated stack actually delivers for the most politically sensitive Salesforce workload (advancement and alumni).

Bettera Agent in Action

Sarah is an alumna requesting her digital transcript. Watch what becomes possible when alumni workflow runs on ServiceNow with Tenon-powered communications and an AI Control Tower governance layer, instead of on Salesforce + Marketing Cloud + Agentforce.

What the demo proves about the evaluation thesis: the operational alumni workflow that Salesforce + Marketing Cloud delivers today is reproducible on the ServiceNow + Tenon stack. The institution does not lose advancement capability in migration. The institution gains a unified governance posture, a native data path, and a consolidated AI agent surface.

Databricks as the data migration and intelligence backbone

The platform partner most CIOs do not yet realize is essential to the migration.

A Salesforce to ServiceNow migration is fundamentally a data migration problem before it is a workflow migration problem. The workflows are recoverable. The data is the asset that took the institution years to accumulate, and the data is what the migration must preserve with full fidelity.

Why the migration is a data problem first. Salesforce holds years of donor records, applicant data, student interactions, alumni engagement history, and the institutional context that surrounds each of these records. Moving the workflows without moving the data faithfully is what produces migration failure. The institutions that botch CRM migrations almost always botch the data layer first.

What Databricks brings that ServiceNow alone does not. Databricks is a unified data and AI platform that specializes in data engineering, data quality, and the institutional data lake architecture that supports both ServiceNow and any other institutional analytics or AI workload. In a Salesforce to ServiceNow migration, Databricks serves four roles:

• The data extraction and transformation layer between Salesforce and ServiceNow

• The historical fidelity layer that preserves the full Salesforce record history at migration

• The unified institutional data lake that supports both the migrated ServiceNow workloads and the institution's broader analytics and AI workloads

• The data quality and governance layer that catches the data problems that would otherwise surface mid-migration

  
  

The four-product partnership. Bettera + ServiceNow + Tenon + Databricks is the delivery model. ServiceNow is the destination platform. Tenon is the marketing automation layer. Databricks is the data backbone. Bettera is the higher-ed-exclusive implementation partner who orchestrates the multi-year program. The deeper case for this partnership architecture is in our Beyond the Help Desk white paper.

The four-phase Salesforce to ServiceNow migration sequence

The operational framework that turns the strategic evaluation into a defensible multi-year program.

Phase 1: Data inventory and dependency mapping. Catalog what lives in Salesforce. Map the workflow dependencies. Identify what depends on Marketing Cloud specifically (the workloads Tenon will absorb), what depends on Agentforce specifically (the workloads Now Assist and AI Control Tower will absorb), what depends on Education Cloud-native objects (the workloads ServiceNow's CRM will absorb), and what depends on Salesforce-only integrations the institution cannot easily replicate. This phase produces the migration risk profile, the sequencing plan, and the data quality baseline. It also produces the answer to the prior evaluation question: whether to migrate at all.

Phase 2: Parallel deployment. Deploy ServiceNow + Tenon + Databricks alongside Salesforce. Build the consolidated stack to functional readiness. Migrate the highest-confidence Phase 1 workload first, typically an internal-facing advancement or alumni workflow where the political risk is lowest. The parallel deployment phase validates the destination platform and produces the operational evidence the Cabinet needs to commit to the broader migration.

Phase 3: Controlled workflow transition. Each Salesforce workflow migrates on a defined cadence, validated against the Salesforce baseline. Advancement workflows. Admissions workflows. Student success workflows. The Marketing Cloud journeys transition to Tenon. The Agentforce AI work transitions to Now Assist under AI Control Tower governance. Each workflow gets a controlled cutover with a defined success criterion before the institution moves to the next workflow. The four FERPA edge cases get a second walkthrough with counsel during this phase because data is moving between systems.

Phase 4: Salesforce sunset on renewal cycle. The displaced Salesforce contract sunsets on its natural renewal cycle. No early-termination fees. The institution chooses not to renew. The Salesforce-specific integrations that did not migrate are handled either through the orchestration patterns described in our piece on orchestration-not-consolidation or through deliberate retention of specific Salesforce capabilities the institution still values.

The full sequencing depends on the institution's contract calendar, workflow priorities, data governance maturity, and political readiness. Bettera works with R1 CIOs to build the institution-specific sequencing as part of the Phase 1 evaluation work.

When migration is the right call (and when it is not)

Migration is the right call when:

(1) The institution is already running ServiceNow at scale. The platform investment is in place. Migration is consolidation, not net-new platform commitment.

(2) The Salesforce renewal is on a defined horizon. The contract calendar gives the institution enough lead time to run the Phase 1 inventory and Phase 2 parallel deployment before the renewal decision must be made.

(3) The institution has the data governance maturity to operate Databricks. Migration is fundamentally a data migration problem, and Databricks is essential to the data layer. Institutions without data governance maturity can build it during Phase 1, but you should know that is part of the work.

(4) The AI consolidation argument applies. The institution sees value in reducing five AI governance frameworks to one. The CIO is making the consolidation case described in our piece on AI vendor consolidation credibly to the Cabinet.

Migration is not the right call when:

The institution has deep Salesforce-specific workflow customization that does not map cleanly to the ServiceNow + Tenon stack yet, and the cost of rebuilding those customizations exceeds the consolidation benefit. Example: institutions with extensive Salesforce Lightning component development, complex Salesforce Industries cloud implementations, or specific advancement modules with no current ServiceNow + Tenon equivalent.

The Marketing Cloud objection is no longer a "not the right call" condition because Tenon addresses it. The Agentforce objection is not a "not the right call" condition because Now Assist + AI Control Tower addresses it. The remaining "not the right call" conditions are genuinely narrow, and the institution can identify them in the Phase 1 inventory.

How the CIO leads this conversation internally: the political playbook

The migration evaluation involves multiple stakeholders. The CIO who runs this conversation well brings each of them along on the specific argument that matters to their role.

The CFO conversation. The financial argument. Per-user licensing economics, AI consumption pricing trajectory, total platform spend across the five-year horizon, and the four-product consolidated stack cost comparison. The CFO does not need the technical migration plan. The CFO needs to see that the migration produces a defensible total-cost-of-ownership case across the five-year window. Bettera builds this case as part of the Phase 1 inventory work.

The VP of Advancement conversation. The single biggest political conversation in the evaluation. Advancement is typically the largest Salesforce stakeholder and Marketing Cloud is typically the workflow they care about most. The answer is Tenon. Tenon delivers what Marketing Cloud delivers, native to the destination platform, with a tighter data path and unified governance. The advancement conversation is not "you have to give up your campaigns." It is "your campaigns run on a better-integrated platform with a clearer FERPA posture and better cross-domain context."

The Chief Data Officer or Director of Institutional Research conversation. The data governance argument. The migration produces a unified institutional data lake on Databricks that serves not just the migrated ServiceNow workloads but the institution's broader analytics, predictive modeling, and AI workloads. The Chief Data Officer comes out of the migration with a stronger data architecture, not a weaker one.

The Cabinet conversation. The strategic AI consolidation argument from our piece on AI vendor consolidation. The five-AI-sidecars-to-one move. The unified governance posture. The reduced General Counsel workload. The four-product stack instead of the five-to-ten-vendor sprawl.

The CIO who runs all four conversations well does not become the institution's gatekeeper saying no to Salesforce. She becomes the institution's enabling partner orchestrating a multi-year strategic platform migration that strengthens each stakeholder's position rather than threatening it. This is the same CIO-as-enabling-partner positioning described in our AI vendor consolidation piece, applied here at the largest possible strategic scale.

Frequently asked questions

What is Salesforce to ServiceNow migration in higher education?

Salesforce to ServiceNow migration in higher education is the strategic decision by an R1 institution to move its CRM, advancement, admissions, and student success workloads from Salesforce Education Cloud onto the ServiceNow platform. The migration is typically structured as a multi-year program with four phases (data inventory, parallel deployment, controlled workflow transition, Salesforce sunset on renewal) and depends on three additional platform components: Tenon for marketing automation native to ServiceNow, AI Control Tower for AI governance, and Databricks for the data backbone.

Why are R1 institutions evaluating migration from Salesforce Education Cloud to ServiceNow?

Four pressures converge in the 2026-2028 window: pricing trajectory at scale combined with Agentforce consumption pricing, AI governance fragmentation as Agentforce becomes one of five to ten AI sidecars across the institutional stack, data fragmentation between Salesforce and the rest of the institutional systems, and renewal cycle convergence as 2018-2023 Salesforce contracts hit their natural inflection points. The evaluation itself is not a commitment to migrate. It is a commitment to make the next platform decision deliberately.

What replaces Salesforce Marketing Cloud in a ServiceNow migration?

Tenon. Tenon is built natively on the ServiceNow platform and delivers trigger-based journeys, drip campaigns, email and SMS, behavioral segmentation, A/B testing, customizable performance dashboards, and GDPR compliance. The key operational difference from Marketing Cloud is that Tenon runs inside the same security boundary as the rest of the ServiceNow workload, with zero data sync latency and a unified governance posture. The deeper introduction to Tenon's role in the institutional architecture is in our Beyond the Help Desk white paper.

How is Tenon different from Salesforce Marketing Cloud?

The architectural difference is native versus integrated. Marketing Cloud sits adjacent to the institution's CRM and connects to it through integration. Tenon runs inside the ServiceNow platform itself. When CRM data changes in ServiceNow, Tenon sees it in real time. When a prospective student, current student, or alumna engages with a Tenon campaign, that interaction flows directly into their ServiceNow profile without an integration layer in between. The capability set is comparable on most major dimensions. The architectural difference matters for AI governance, FERPA posture, and operational simplicity.

What is Agentforce, and how does it compare to Now Assist?

Agentforce is Salesforce's agentic AI platform, introduced at Dreamforce 2024 and expanded materially through 2025 and 2026. It replaced the older Einstein predictive layer as Salesforce's primary AI capability. Now Assist is ServiceNow's equivalent agentic AI platform, bundled across every ServiceNow tier per the April 9, 2026 commercial model announcement. The two platforms are comparable in agentic capability. The relevant difference for the migration evaluation is governance: Agentforce is one of five to ten AI sidecars the institution governs separately, while Now Assist sits inside the AI Control Tower governance layer described in our piece on the ServiceNow AI Control Tower for higher education.

How long does a Salesforce to ServiceNow migration take at an R1 institution?

The honest answer is that it depends on the institution's Salesforce contract calendar, the scope of the displaced workloads, the data governance maturity, and the political readiness of the stakeholder group. The four-phase sequence is structured so that Phase 4 (Salesforce sunset) aligns to the natural renewal cycle of the displaced contract, which is what determines the overall program length. Phase 1 inventory and dependency mapping is the leading work that produces the institution-specific sequencing plan. Institutions that try to compress the program produce the data migration failures the four-phase sequence is designed to prevent.

What role does Databricks play in a Salesforce to ServiceNow migration?

Databricks is the data backbone. A Salesforce to ServiceNow migration is fundamentally a data migration problem before it is a workflow migration problem. Databricks serves four roles: the data extraction and transformation layer between Salesforce and ServiceNow, the historical fidelity layer that preserves the full Salesforce record history at migration, the unified institutional data lake that supports both the migrated ServiceNow workloads and the institution's broader analytics and AI workloads, and the data quality and governance layer that catches the data problems that would otherwise surface mid-migration. The four-product delivery model (Bettera + ServiceNow + Tenon + Databricks) is built around Databricks as the data layer.

Where this leaves the institution

The Salesforce to ServiceNow migration in higher education is the strategic platform evaluation that R1 CIOs should run deliberately before the next multi-year Salesforce renewal locks in another contract cycle on terms set when the institution was a different version of itself.

The platforms have changed materially.

The pricing has changed.

The AI capability has changed.

ServiceNow + Tenon + AI Control Tower + Databricks is now a credible consolidated alternative to the Salesforce + Marketing Cloud + Agentforce stack. The evaluation itself is not a commitment to migrate. The evaluation is a commitment to make the next decision with the full picture of what is now possible.

If your institution is approaching a Salesforce renewal and would benefit from an evaluation framework rather than a vendor pitch, that is the working session we facilitate at Bettera. Contact us and we will walk through your institution's migration readiness using the four-phase sequence.

Bettera is the only ServiceNow consulting partner exclusively focused on higher education, and Salesforce to ServiceNow migration is the Year 2 strategic engagement we lead for R1 institutions in 2026. The four-product partnership (Bettera + ServiceNow + Tenon + Databricks) and the deeper architectural argument for the consolidated stack are covered in our Beyond the Help Desk white paper.

Public Sources Cited

• ServiceNow Newsroom, "ServiceNow moves beyond the sidecar AI era," April 9, 2026

• ServiceNow Newsroom, "ServiceNow expands AI Control Tower," Knowledge 2026, May 2026

READ NEXT

• Higher Education AI Vendor Consolidation: One Platform vs Five Point Solutions (the AI consolidation argument that frames the migration evaluation)

• Now Assist in Higher Education: A Practical AI Governance Framework (the AI strategic posture)

• ServiceNow AI Control Tower for Higher Education (the AI governance layer)

• FERPA and AI Compliance in Higher Education (the legal posture that applies once during consolidation versus five times during sprawl)

• Orchestration, Not Consolidation (the systems-of-record argument that reconciles with the AI agent surface consolidation argument)

• AI Readiness in Higher Education (the document workflow foundation that the migrated workloads depend on)