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

Salesforce as a Student Information System

After CAMS: the student record on Salesforce.

Unity Environmental University replaced CAMS in 2024 and runs prospect to alumni on Salesforce today. A CAMS migration is a completed project with a live, written-up reference.

In production

This migration has already been done.

Unity Environmental University replaced CAMS in 2024. Its student record — registration, academic records, student finance and compliance reporting — runs on Salesforce Education Cloud today, with real students registering in real terms on the system this page describes.

Where things stand

The situation around CAMS.

CAMS has changed hands: divested from Unit4 in 2021, it now belongs to Thesis, whose stated direction is its new Elements platform. Institutions on CAMS are, in effect, being asked to migrate somewhere either way.

What runs natively

Everything CAMS 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 institutions tell us changed once the record was on a platform.

A platform with a published cadence
Three releases a year, dated in advance, taken as they arrive. What is coming and when is a matter of public record rather than something to infer.
Reporting against the live record
Built and changed by the people who need the answer, with permissions applied from the record itself — no separate report writer, no export, no waiting on a specialist.
Connecting the next system is configuration
Documented APIs on every object and real-time events when something changes, with established routes to the learning management system, single sign-on, payment gateways and the Clearinghouse.
Room for how you actually operate
Rolling starts, non-term calendars, blended credit and payment plans that fit the student. The operating model is configuration rather than the shape the product was built around.

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 CAMS.

What does Thesis’s move to Elements mean for CAMS?

CAMS was divested from Unit4 in 2021 and now belongs to Thesis, whose stated direction is its newer Elements platform, and Gartner lists CAMS as legacy. Institutions on CAMS are being asked to migrate somewhere either way, which makes this a selection decision rather than a question of whether to move.

Has anyone actually moved off CAMS onto Salesforce?

Unity Environmental University replaced CAMS in 2024 and runs prospect through to alumni on Salesforce Education Cloud today, with the project written up as a case study. It is a completed migration with a named institution behind it rather than a described capability.

We are a small college. Is this over-engineered for us?

Configuration is what prevents that. You configure the record, the calendar and the processes you actually run, and nothing else appears. The result is usually a smaller estate than before, because the integrations between separate systems stop existing.

What happens to the reports we built directly against the CAMS database?

They are rebuilt as native reports on the platform, against live data rather than a database read behind the application. Nothing depends on knowing the physical schema, which means reports survive platform updates instead of breaking on them.

Start here

Bring us your CAMS 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.