When a campus Salesforce project has stalled between admissions, student success and advancement, we find what still works, stabilize it and complete the rollout.
An education rescue usually begins with an institution that bought one platform for the whole student lifecycle and ended up with three disconnected builds. Admissions may be live, advising half-configured and advancement still waiting, each designed by a different team with different ideas of what a student record is. We review the org against how your offices actually work, secure whatever the current recruitment cycle depends on, and then agree a sequence for the rest. Decisions are made with the registrar, enrollment and IT in the room, since each owns part of the data.
Higher education projects stall for reasons that are unusual outside campus life. Governance is shared across schools, colleges and administrative offices, so a design decision can wait a full committee cycle. The academic calendar leaves narrow windows for change: nobody touches recruitment tools during application deadlines, and advisors cannot absorb new processes in the first weeks of a term. The student information system remains the record of enrollment, grades and holds, yet many failed builds tried to replicate it. Privacy obligations under FERPA also shape who may see advising notes, which is where early builds often exposed too much or locked advisors out entirely.
Some failed campus orgs contain separate records for the same person as prospect, applicant, student and alumnus, created by different offices. We map how each department identifies people, choose a single contact-centered structure, often aligned with Education Cloud, and merge carefully so application history, advising notes and giving records stay attached to the right individual across every stage. Merge rules are reviewed with the registrar first.
Recruitment teams need inquiry capture, event registration, application status and communication tracking working before the next cycle opens. We test every form, lead source and status update end to end, repair assignment rules for counselors and territories, and confirm that application data from the portal or SIS updates Salesforce without creating duplicate applicants or overwriting counselor notes. Counselors confirm results before the cycle opens.
Student success tools often launched with case types nobody used and alerts that fired too often or never. We work with advising leads to trim alert criteria, restructure appointment and note records, and apply sharing rules that give each advisor the students they support. Faculty referrals are simplified so instructors actually submit them when a student is struggling. Advisors then trust the queue again.
Alumni relations and fundraising are frequently the last phase and the first to be cut when a project runs over. We assess what gift, constituent and engagement data already sits in Salesforce, decide how it relates to the student record, and plan the remaining work so development officers see a graduate's full history with the institution. Gift processing stays with the advancement team throughout.
Every education rescue starts by mapping the academic calendar against the recovery plan, marking application deadlines, term starts and commencement as periods when nothing risky ships. Next come a governance meeting with the offices that share the org and a review of the build, data and SIS integration. Urgent fixes for recruitment go first. Structural changes are tested with sample records for several student types, including transfer, graduate and returning students. Central IT signs off on security and integration changes, and each office approves the pieces affecting its staff before release.
Enrollment, program and hold data flow into Salesforce on a schedule we verify, and we remove integrations that tried to write academic records back.
Application submissions and status changes create or update the right applicant record, with matching rules that stop duplicates when students apply more than once.
Course activity signals feed early-alert criteria, limited to the indicators advisors agreed are meaningful rather than every available data point.
Changing recruitment tools during application season puts enrollment at risk. Lock the funnel during peak periods, fix only what is broken, and hold redesign work until counselors can test changes properly and learn them before the next cycle. Communicate the freeze clearly.
FERPA and institutional policy limit who sees academic and personal notes. Review record types, sharing rules and field security with the registrar and counsel, so advisors see what they need without exposing sensitive details to every user on campus. Test with real advisor profiles.
Stalled campus projects often lack one decision owner. Establish a small governance group representing each office, with a clear route for requests and priorities, so the rescued org does not fragment into separate builds again within a year. Publish its decisions openly.
Yes, although the work is mostly about agreement rather than configuration. We map each office's records and processes, propose a shared person model, and show each team what changes for them. Merging then happens in stages, starting with the office under the least calendar pressure, so recruitment is never at risk while the model is unified across departments.
Sometimes. If your build is heavily customized around an older data model, moving to Education Cloud objects can reduce future maintenance, but it adds scope to a project that already struggled. We compare the effort of repairing the current model with moving to the newer one, and recommend whichever gets offices working reliably with less risk.
Start by asking which alerts led to an action last term. Most failed early-alert setups trigger on too many signals, so advisors ignore the queue. We reduce criteria to those advisors trust, route alerts to the assigned advisor rather than a shared pool, and review outcomes with advising leadership after the first term. Adjustments continue each term after that.
Quite involved. IT usually owns the SIS integration, single sign-on and security review, and it often inherited the failed project from a departmental sponsor. We work alongside IT from the assessment onward, share every design decision, and hand over documentation so the campus team can support the platform after the rescue ends. IT also joins release planning meetings.
One onshore team with 150 Salesforce certifications, a Salesforce Consulting Partner since 2017.
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.