
TL;DR
- A unified customer profile in EdTech is one record per learner that follows them from first inquiry to alum. It joins identity, stage and data from the SIS, LMS and CRM, links the parents and sponsors in the decision and carries the conversation history from every channel.
- Student data silos outlast CRM projects because every system was bought by a different team for a different job. The SIS, LMS, CRM and aid system each hold one true slice.
- Fields are the easy part. The profile also needs what the learner asked, objected to and was promised, and which channel they actually answer.
- Leave each slice in the system that owns it. Unify identity and context in a layer on top, then let that layer act within minutes.
- The payoff shows up in speed to first reply, fewer admits lost over the summer, parents who feel informed and earlier retention signals.
Most parents are in the college search. Most of them say colleges are not giving them what they need.
A unified customer profile in EdTech is one record per learner that joins identity, lifecycle stage, data from the SIS, LMS and CRM, and the conversation history from every channel. It links the parents and sponsors involved, so any counselor, advisor or AI agent can see what the learner needs next without asking them again.
The EAB 2026 Parent Survey, published in July 2026 from more than 2,500 parents, found that 74% are highly involved in their student's search. And 69% say colleges do not give them the information they need.
The parent is in the conversation. The parent is almost never in the record.
This guide covers who the customer really is in education, why student data silos survive every CRM project, what a profile needs beyond fields, how to unify it without a migration and where it pays off first.
What is a unified customer profile in EdTech, and who is the customer?
A unified customer profile in EdTech is a single, current view of one learner that every team and system reads from. The hard part is the word customer, because in education it means several people at several stages.
One learner, five roles over time
The same person shows up as a prospect, an applicant, an admit, an enrolled student and later an alum or a returning learner. Each role usually lives in a different system, under a different ID, often with a different email address.
A profile that resets at each stage throws away the most useful history, which is why orchestrating the full student lifecycle starts with one record. The counselor who helped with an application essay knows things the first-year advisor will need in October.
The people around the learner
Parents, guardians, employers paying tuition and scholarship sponsors all shape the decision. They ask their own questions, on their own channels, and they often decide when money is involved.
That is why a unified profile links people. Each person keeps their own contact points and consent, and the link records how they relate to the learner.
In education the customer is a small group of people moving through five stages, and the profile has to follow all of them.
Why do student data silos survive every CRM project?
Student data silos survive because each system was bought by a different team to do a different job well. A new CRM fixes recruitment's view and leaves the registrar, the LMS and financial aid exactly where they were.
The numbers get large quickly. A Deloitte UK case study (undated) reports that the University of Hull was running 27 different systems and data sources across the institution before it unified them.
Our breakdown of the EdTech data silo maps where that sprawl comes from. Students feel it directly. In the first Salesforce.org Connected Student Report, a February 2020 survey of more than 1,000 students and staff, 63% of students said they had to sign into two or more platforms to get answers.
Three habits keep the silos in place.
- Every system is right about its own slice. The SIS is right about grades and the aid system is right about awards. Nobody wants to give up the record they trust.
- IDs change at each stage. An inquiry gets a CRM ID, an applicant gets an application number and a student gets a student number. Matching them later is guesswork.
- Conversations happen outside all of them. WhatsApp threads, chat transcripts and phone calls sit in inboxes and personal phones, so the richest data never lands in any system at all.
We have covered the general version of this in our piece on breaking data silos. In education the cost lands on a 17-year-old and their parent, who end up repeating themselves to four offices.
Silos last because each one is correct about something, so the fix is a shared layer on top of them.
What does a student profile need beyond fields?
A student profile needs conversation context on top of its fields. Fields tell you who the learner is. Context tells you what they want, what is blocking them and what you already promised.
Most student 360 projects stop at fields like name, program, stage, GPA and aid status. Those matter. They also cannot tell a counselor that the student asked twice about part-time options, or that her father wants a call after 7pm.
| What fields capture | What conversation context adds |
|---|---|
| Program of interest | The two programs she is still comparing, and why |
| Application status | The document she said she would upload on Friday |
| Aid package sent | The objection her parent raised about the loan component |
| Email and phone on file | The channel she actually replies on, and how fast |
| Enrolled, term one | The worry about commuting she mentioned in July |
Context also decays if nobody acts on it. A question asked on WhatsApp in June is useless in August if it sits in one counselor's phone.
This is the gap our post on how conversation data builds a single customer view describes for every industry. Education has more of it, because the learner, the parent and the sponsor all talk to you separately.
A profile that knows the GPA and forgets the promise you made is still a silo.
How do you unify customer profiles across channels and lifecycle stages?
You unify customer profiles across channels and lifecycle stages by agreeing on identity rules first and moving data second. The order matters, because most failed projects start with a data pipe and no rule for who is who.
- Pick the identifiers that prove a match. Usually a verified email, a verified phone number and any student or application ID. Decide which pairs merge automatically and which go to review.
- Store each contact point separately. International students often carry a home number, a local number and a WhatsApp account that matches neither. Each one gets its own channel type and consent status, linked to one learner.
- Link people, do not merge them. Parents and sponsors become their own profiles with a relationship to the learner. Siblings who share a parent's email are the classic false merge, so test for them first.
- Carry one person ID across stage changes. When an inquiry becomes an applicant and then a student, the new system IDs attach to the same person. Nothing gets re-created.
- Write every conversation to the same timeline. Chat, WhatsApp, email, SMS and calls land on the learner's profile with a summary of what was asked, decided and still open.
- Keep a merge log. Every merge records its source and evidence, so a wrong one can be reversed without losing history.
Our post on omni-channel continuity in student recruitment goes deeper on the channel side of step five.
Identity rules come before integrations, and parents get linked as their own profiles.
Which system should own which slice of the student profile?
Each system should keep owning the slice it is already right about. The unified profile reads from them and adds the context none of them hold.
| System | Owns | What the profile takes from it |
|---|---|---|
| Student information system (SIS) | Enrollment, courses, grades, holds | Stage, program, open holds |
| Learning management system (LMS) | Course activity and submissions | Engagement signals, missed work |
| Admissions or student CRM | Pipeline, staff tasks, campaigns | Source, owner, application status |
| Financial aid and billing | Awards, balances, deadlines | Open aid steps and due dates |
| Conversation layer | Every message and call, on every channel | Questions, objections, promises, channel preference |
Nothing in that table needs a migration. The registrar keeps the SIS, admissions keeps the CRM and nobody waits two years for a replatforming project.
The conversation layer is the row most institutions are missing. It is also the one that changes most often, sometimes several times a day for an active applicant.
Leave records where they live and add the layer that holds what was said.
Should a unified student profile live in a warehouse or an activation layer?
A unified student profile that only feeds reports belongs in a warehouse. A profile that has to change what happens to a learner this afternoon needs an activation layer that reads it and acts in minutes.
Both are useful. A higher ed data warehouse answers questions like "which programs lost the most admits last summer". It runs on nightly loads and serves analysts.
Recruitment does not run on nightly loads. In the RNL 2023 graduate recruitment research, two-thirds of graduate students expected a reply within 24 hours, and more than 60% said they would likely or definitely enroll with the program that responded first. RNL's 2024 Online Student Recruitment Report, a survey of 1,500 prospective and enrolled online students, adds that 45% of online undergraduates read a slow reply as a sign they are not a priority.
An activation layer closes that gap. It reads the profile when a message arrives, replies with the context already loaded and writes the result straight back. The activation gap is where most single-view projects stall, in education and everywhere else.
Warehouses explain last term. Activation layers change this week.
Where does a unified student profile pay off first?
A unified student profile pays off first at the handoffs, where one team passes a learner to another and context usually gets lost.
Speed to first reply
When the profile is current, the first reply to a new inquiry can go out in seconds and already know the program, the source and any earlier contact. That matters given the RNL finding above. Our post on speed to lead in admissions covers the mechanics.
Summer melt
Summer melt is the gap between a student committing and actually showing up. Researchers Ben Castleman and Lindsay Page, in the 2013 Harvard Strategic Data Project Summer Melt Handbook, put it at 10% to 40% of college-intending students, and found that counseling and text outreach lifted enrollment.
The problem has not gone away. The School District of Philadelphia reported in May 2026 that 42.5% of college-planning seniors in its 2024-25 exit survey melted, up from 40.5% a year earlier. A profile that knows which aid step, form or housing question is still open tells you exactly who to message in July.
Parents who feel informed
Back to the EAB numbers. When parents are linked to the learner with their own consent and channel, they get answers to their own questions. Families stop finding out about deadlines from their kids at the last minute.
Earlier retention signals
Once a learner enrolls, the same profile picks up LMS activity and new conversations. A student who stops logging in and asks about withdrawal dates shows up before the midterm grades do. We covered those patterns in student retention analytics.
Every handoff that loses context today is a place the profile earns its keep.
How Zigment keeps the student profile in the conversation
Zigment is a Conversational Revenue Orchestration Platform for education and EdTech growth teams. It runs student and parent conversations on WhatsApp, web chat, email, SMS and voice, and sits on top of the CRM and SIS you already run.
The Conversation Graph is the engine underneath. It keeps one timeline per learner across every channel and stage, links the parents and sponsors in the decision, and records what each person asked, objected to and was promised. AI agents read that timeline before they reply and write back what changed, within boundaries your team configures once.
One EdTech platform running its enrollment conversations on Zigment handles more than 100,000 conversations a month and saw a 3x lift in conversion (Zigment-reported, from Zigment's customer deck, undated). Its WhatsApp and web chat sessions carry over from one visit to the next, so no learner starts from zero.
The record that remembers the conversation
Every institution already has a record for each student. The question is whether that record knows what the student said last Tuesday, and what their mother asked on WhatsApp on Sunday night.
If it does not, which of your teams is answering those questions from memory right now?
See how one learner timeline carries context across every channel in how the Conversation Graph works.