Tondro Salesforce Spark · Dubai · 13 October 2026More information →
Salesforce Consulting Partner
Austin, TexasMálaga, SpainAmsterdam, Netherlands

Salesforce as a Student Information System

After Ellucian Colleague: the student record on Salesforce.

Colleague institutions ask the same question Banner institutions do: what happens to our system in a portfolio of four? Every record function Colleague runs today — registration, grading, transcripts, degree audit — runs natively in our Salesforce deployments.

Where things stand

The situation around Ellucian Colleague.

Since Ellucian acquired Anthology’s SIS business in December 2025, Colleague is one of four student systems the same owner maintains side by side. No public roadmap states which receives long-term investment.

What runs natively

Everything Ellucian Colleague holds today, native.

The record of truth moves whole. In our deployments these run natively on Salesforce — configured on the platform, not built beside it.

Registration
Prerequisite enforcement, section capacity and waitlists.
Grading
Grade entry, grade rolls and grade-change workflow.
GPA and academic standing
Computed in the platform, not imported into it.
Official transcripts
Produced natively; delivered through your existing service.
Course catalog and class scheduling
Terms, sessions, sections, rooms and times.
Degree audit
Degree progress and what-if analysis.
Transfer credit
Articulation rules, not just stored evaluations.
Student financials
Fee assessment, accounts receivable, payments and refunds.

Financial aid stays in the system your aid office trusts — live integrations with PowerFAIDS, Regent and Campus Ivy tie aid status into the same student record. Reporting and compliance run natively, by jurisdiction.

What changes day to day

The work after the migration, not just the migration.

A replacement is judged on the years after go-live. Four things Colleague institutions tell us changed once the record was on a platform.

A database you can hire for
The record sits on a mainstream platform with the largest skills market in enterprise software. Finding someone who can work on it is a job posting, not a search for one of a shrinking number of specialists.
Screens that read in English
No memorized codes between a new starter and the record. The people who join your office this year can be useful in weeks, and the knowledge does not walk out when someone retires.
Integrations are not a vendor list
Every object is addressable through documented APIs, so connecting a system nobody anticipated is configuration — not a wait for someone to decide it is worth building a connector for.
The office of record stops saying no
When a policy change is configuration made in days, the answer to a new progression rule or a calendar exception is a date rather than a refusal. That changes what colleagues bring you.

Ten months, typically — for institutions under 10,000 students.

Institution size drives the timeline, and larger or more structurally complex institutions take longer — we will tell you where you fall in the first conversation. For context, the industry norm for an SIS replacement is measured in years.

Common questions

Moving off Ellucian Colleague.

What happens to our UniData data?

It migrates into a relational data model on the platform, with the multi-valued structures unpacked into records and relationships that report cleanly. This is real work and it is scoped in the first phase, where the mapping decisions are made with your team rather than discovered during testing.

Will our staff have to relearn everything?

They learn one interface instead of a set of screen codes. In practice the transition is easier for the people who know the work and harder for the people who knew the system — because expertise in your calendar, your policies and your exceptions is exactly what carries across, and expertise in navigating the old software is what stops being necessary.

Is Salesforce viable for a small college?

Yes, and the institutions we work with are mostly under 10,000 students. The platform scales down as well as up because the operating model is configuration rather than a fixed product: a college running one campus and a handful of programs configures what it needs and nothing else.

Who supports it after go-live, and how is that priced?

Either your own team or ours. Several clients staff their own Salesforce administration; others use our managed services, which is a standing team rather than a per-incident sale. What you are not doing is paying a maintenance contract for the privilege of waiting on a release cycle.

Start here

Bring us your Ellucian reality.

Your contract dates, your academic calendar, your integrations, whatever your registrar worries about most. A discovery call is a working conversation with people who have moved institutions onto Salesforce — we will tell you candidly whether this is a fit.