01
Student lifecycle (inquiry → alumni)
EDA-based configuration covering inquiry, application, enrollment, course connections, and alumni. Every stage tracked against retention and outcomes, not just stage progression.
Enterprise Platforms × Education & EdTech
Salesforce for Education.
Salesforce Education Cloud, Education Data Architecture (EDA), and Experience Cloud implementations for K-12 districts, higher ed institutions, and EdTech operators, student lifecycle done right with FERPA-aligned configurations and the SIS-integration boundary as primary scope.
- Privacy
- FERPA · COPPA
- Identity
- SAML SSO · Clever / ClassLink
- SIS interop
- OneRoster · SIS APIs
- Records
- Audit log + retention
The problem
Education Salesforce orgs treat the student lifecycle as a sales pipeline.
Higher ed and K-12 buyers come to Salesforce with a clear ask: track the student lifecycle from inquiry through application, enrollment, retention, alumni, and the parent / household / community relationships around it. The pattern that fails them is partner work that crams the lifecycle into Sales Cloud's lead → opportunity → account model and then bolts custom objects on top.
EDA (Education Data Architecture) is the right starting point: it ships with Affiliations, Course Connection, and Household models that fit the domain. We configure EDA as the foundation, integrate the SIS (OneRoster, district SIS APIs), wire the Experience Cloud portals students and parents actually use, and stand up the FERPA-aligned audit boundary.
Where it ships
5 workloads, scoped to education & edtech.
Concrete applications where enterprise platforms unlocks measurable value inside education & edtech delivery constraints.
- 02
−9 hr/wk
registrar manual reconciliation
SIS integration (OneRoster, district SIS)
OneRoster for K-12; institutional SIS APIs (Banner, Workday Student, Colleague) for higher ed. Student, course, term, and grade records as the integration spine. Idempotent, conflict-resolved, audit-grade.
- 03
Recruitment + admissions
Enrollment-cycle CRM tuned for the long admissions cycle: campus visits, application checkpoints, FA / FAFSA tracking, and yield modeling. Marketing Cloud for nurture campaigns with FERPA-bounded segmentation.
- 04
Student-success advising
Service Cloud + custom Lightning for advisor caseloads, intervention tracking, and at-risk flags. Integrated with LMS (Canvas, Brightspace, Schoology) for the engagement signals advisors need.
- 05
Family + parent portals
Experience Cloud portals for parents (K-12) and students / parents (higher ed). Document upload, milestone visibility, communication threads. Bounded by FERPA consent and minor-protection rules.
How we engage
4 phases, named in the SOW.
Each phase has a deliverable, an owner, and an acceptance criterion calibrated to education & edtech delivery.
- 01
Lifecycle + identity discovery
Two-week discovery: student lifecycle map, SIS interface surface, identity model, FERPA / COPPA boundary, parent / household relationships. Output is honest fit recommendation including 'EDA fits this' vs. 'use a different platform here'.
- 02
EDA-first configuration
EDA as the data-model foundation; standard Lightning where the use case fits; custom objects only where EDA can't be extended. Affiliations and Course Connections wired before custom work.
- 03
SIS + LMS integration
OneRoster (K-12) or institutional SIS APIs (higher ed) with idempotent transformation pipelines. LMS integration through standard connectors (Canvas, Brightspace) or LTI for the long tail. Latency, ordering, and re-sync semantics designed before configuration.
- 04
FERPA-aligned audit + go-live
FERPA evidence package, parent-consent flows for minors, audit-log retention configured per institution policy. Adoption discipline through faculty / advisor training, in-app guidance, and the registrar-led cutover plan.
Capabilities
What’s in scope.
- Education Cloud + EDA configuration for K-12 and higher ed
- OneRoster + SIS integration (Banner, Workday Student, Colleague, district SIS)
- LMS integration: Canvas, Brightspace, Schoology, custom LTI
- Marketing Cloud + Pardot for admissions and lifecycle nurture
- Experience Cloud portals for students, parents, faculty, advisors
- FERPA / COPPA-aligned configurations and evidence packages
- Migration from TargetX, Slate, or legacy student-CRM platforms
Stack
Tools we use in production.
- Salesforce clouds
- Education CloudEDAMarketing CloudPardotExperience Cloud
- SIS connectors
- OneRosterBannerWorkday StudentColleaguePowerSchool
- LMS connectors
- CanvasBrightspaceSchoologyLTI 1.3
- Identity
- SAML SSOCleverClassLinkEntra ID
- ALM & Operations
- Salesforce DXGitHub ActionsCopado
Compliance overlay
Frameworks we engineer to.
Every education & edtech engagement carries the evidence collection that procurement and audit teams expect on day one.
- 01
FERPA
Education record classification at the field level; consent capture for disclosure; audit-log retention per institution policy. Evidence package shipped with go-live.
- 02
COPPA (K-12)
Minor-protection rules in EDA; parent-consent flows for under-13 records; restricted marketing fields and consent-bounded segmentation.
- 03
OneRoster (K-12)
OneRoster v1.1 / v1.2 for student / class / enrollment / grade records. Conflict-resolution rules documented and tested. Roster refresh cadence aligned to district calendars.
Selected work
Quantified outcomes, not adjectives.
Where this fits
Open the parent practice or industry hub.
Common questions
Asked before the first call.
- 01
EDA or Education Cloud, what's the difference?
EDA is the open-source data architecture (free, community-supported). Education Cloud is the licensed product that builds on top. For most K-12 and higher-ed engagements we start with EDA: it's mature, well-supported, and avoids licensing complexity. Move to Education Cloud when the institution needs the licensed analytics, advising, or recruitment apps that ship with it.
- 02
Can you integrate with Banner / Workday Student / Colleague?
Yes: all three are common SIS integrations. Banner uses ETHOS APIs; Workday Student uses RaaS / Cloud Connect; Colleague uses the Web API or ETOS. We build idempotent transformation pipelines with explicit conflict resolution and error routing. No nightly batch jobs that silently lose records.
- 03
What about FERPA?
FERPA-defensible Salesforce orgs are about the configuration and evidence package, not the platform. We configure record classifications, consent capture, audit-log retention, and disclosure-tracking flows, then ship the evidence package an institutional auditor accepts. Salesforce's underlying infrastructure is FERPA-eligible; the implementation has to follow.
- 04
How long does a typical engagement take?
Higher ed (single institution): EDA + Banner integration + recruitment-cycle CRM in 6–10 months. K-12 district: OneRoster + parent portals + advising in 4–7 months. Multi-campus systems with consolidated EDA: 9–14 months phased. Programs that try to compress further usually descope SIS integration. We don't recommend that.
- 05
What does this cost?
Discovery + assessment: 2 weeks, $30K–$70K. EDA + Sales / Service Cloud implementation: 5–8 months, $300K–$800K. SIS integration (Banner / Workday Student / Colleague): +2–4 months, $150K–$400K. Marketing Cloud / Pardot: +2–4 months, $120K–$300K. Managed services post-launch: $15K–$60K monthly retainer.
- 06
Can you do EdTech product builds (LMS, SIS, assessment)?
Yes: those go through our Custom Software practice (FORGE), with Salesforce as a likely customer-facing layer but not the whole stack. The engagement starts with what should sit on Salesforce vs. custom and what should integrate to existing SISs / LMSs.
Talk to us
Bring us a hard Enterprise Platforms problem. We’ll bring a senior Education & EdTech engineer.
A senior engineer plus the ATLAS department lead joins the first call, both with prior education & edtech delivery experience.