Implementing Education Cloud is a 6-12 month project involving data migration, system integration, user training, and process change. Plan it like a campus-wide ERP project, not a Salesforce sprint.
- Identify the in-scope lifecycle stages
Are you implementing for recruitment only? Student success? Advancement? End-to-end student lifecycle? Each stage has its own data model and team; phasing the implementation reduces risk and complexity.
- Choose EDA or Rebuilt Education Cloud
New institutions should default to Rebuilt Education Cloud. EDA users staying on the legacy path should plan a migration in the next 2-3 years. The choice drives data model, integration architecture, and training.
- Map source systems and integrations
Document every system that holds student data: SIS, LMS, financial aid, fundraising, library, parking, dining. For each, decide what flows to Salesforce, what flows back, and the frequency. Plan MuleSoft, custom integrations, or native connectors per system.
- Configure the platform
Build the org: enable Education Cloud features, install EDA (if using), set up Salesforce.org foundation packages. Configure profiles, permission sets, and Lightning Record Pages for each user persona.
- Migrate data
Bring in current students, applicants, alumni, courses, programs. Use Data Loader or third-party ETL. Data quality at migration is the difference between a useful system and a Salesforce-shaped landfill; validate carefully before going live.
- Train and launch
Roll out to one user community at a time: recruiters first, then student services, then advancement. Each group has different workflows and different definitions of success. Train, support, measure, and iterate.
Modern Education Cloud with dedicated objects. Default for new implementations.
Legacy managed package on standard objects. Still supported; migration path to Rebuilt is in progress.
Free package combining EDA with NPSP for institutions running both education and nonprofit programs.
Add-on for student recruitment communications and engagement campaigns.
- Implementations underestimate integration effort. SIS, LMS, and financial systems each have their own quirks; budget more time for integration than for Salesforce configuration.
- EDA-to-Rebuilt migration is a project, not an upgrade. Plan it deliberately; do not assume Salesforce will auto-convert your existing org.
- Student data is regulated. FERPA (US), GDPR (EU), and similar laws apply. Configure sharing and field-level security carefully and document the access model for audits.
- Higher-ed processes are slow to change. A 6-month Education Cloud project can become an 18-month project if institutional change management is not part of the plan.