What you’ll learn in this post:
- Why K-12 schools migrate from EDA to Agentforce for Education.
- What the architecture actually changes (and what stays the same).
- The compatibility decisions you’ll face: Success Hub, Admissions Connect, Admin Accounts, and the K-12 Architecture Kit.
Why migrate to Agentforce for Education?
EDA has served schools well. It’s free, it’s community-supported, and for many K-12 schools it still gets the job done. So before anything else, it’s worth being direct about when migration makes sense and when it doesn’t.
If your Salesforce org primarily supports recruiting and admissions, and everything else is handled by a Student Information System, EDA may still be the right fit. The complexity Agentforce Education introduces may not be worth it for narrower use cases.
If, however, your school wants to expand how it uses Salesforce to use cases like managing student success, connecting family data, activating AI-based case routing, or building a fuller picture of each student across their lifecycle, Agentforce Education is where Salesforce is investing. And the gap between the two will only widen over time.
The Core Difference is Architecture
EDA is a managed package that has to be installed on top of the Salesforce core platform. Agentforce Education is the platform, as it’s built on the core Salesforce data model, so there is nothing to install, with the exception of the K-12 Architecture Kit, but more about that later.
The benefit of being on core isn’t just fewer packages to manage. It’s that Agentforce Education sits on the same layer of the Salesforce platform that Salesforce’s own product teams build against. Every new capability like AI, automation, and industry common features, lands in Agentforce Education the moment it ships, with no package update, no compatibility lag, and no namespace conflict standing between the institution and the platform. EDA will always be one step behind because the platform was never built around it.
EDA uses a Contact-based data model with Administrative Accounts to represent students – where the Account record exists mostly as a container. This often leads to a proliferation of Contact record types to represent applicants, students, alumni, and other constituent groups. Agentforce Education uses Person Accounts, similar to Health Cloud and Financial Services Cloud, which aligns with the core account model and allows direct relationships with other accounts such as departments, programs, and households.
The true advantage of the Person Account model isn’t just cleaner data. It’s that Person Accounts put Agentforce Education constituents on the same foundational data model that the rest of the Salesforce platform is built around. Every native tool, every AI capability, every cross-cloud integration starts from that assumption. EDA Contacts don’t. That gap will widen as Salesforce continues building on the Person Account model — and it’s one of the strongest arguments for migrating sooner rather than waiting.
Other Capability Differences to Consider
Salesforce built Agentforce Education with the future in mind, and with the goal of leveraging many of the common industry cloud features, ensuring compatibility with other tooling, such as Marketing Cloud, and aligning with the Salesforce release cycle. Below is a table of key capabilities between EDA and Agentforce Education.
| Capability | EDA | Agentforce Education |
|---|---|---|
| Person Account data model | No (Contact-based) | Yes |
| Education Data Foundation (native to core) | No (managed package) | Yes |
| OmniStudio for guided workflows | No | Yes |
| Business Rules Engine | No | Yes |
| Activity Timelines / Care Plans | No | Yes |
| Advanced Case Management | Limited | Yes |
| Data 360 for Education (unified data) | Limited compatibility | Yes – purpose-built |
| Agentforce AI | Limited | Yes – purpose-built |
| Marketing Cloud / Pardot (MCAE) | Compatible | Compatible |
| K-12 Architecture Kit (K-12 only) | Installable add-on | Installable add-on (same kit) |
| Salesforce release cycle alignment | Package-dependent | 3x/year, native updates |
One thing that does not change: K-12 schools using the K-12 Architecture Kit will continue to install it in Agentforce Education, just as they did with EDA. The Kit is the same package. The difference is that it now operates on top of a Person Account model rather than the older Administrative Account structure.
Student and household Contact records carry over via the Contact side of the Person Account. However, existing page layouts should be rebuilt rather than migrated. EDA page layouts frequently reference objects, fields, and functionality that don’t exist in Agentforce Education. Rebuilding them from scratch in the new environment is cleaner and avoids carrying that technical debt forward.
What about Data 360 and Agentforce?
Data 360 is technically available to standard Salesforce orgs, including those running EDA. But it was purpose-built for Agentforce Education. When Salesforce announced Data 360 for Education at Dreamforce 2024, the framing was explicit: Data 360 serves as the data foundation that makes Agentforce AI practical for schools – unifying student data from multiple systems so AI-based tools like automated case routing and student support agents actually have something to work with.
You can connect Data 360 to an EDA org. Whether the education-specific data unification and AI capabilities work at full depth on the EDA data model is less clear, and Salesforce has not documented this comprehensively. In practice, schools that want to use Agentforce meaningfully are migrating to Agentforce Education first. We recommend confirming this with your Salesforce account executive before making any decisions based on it.
On Marketing Cloud and Pardot: both work with Agentforce Education. You can use either depending on your existing licenses and use cases. This is not an either/or decision. Your migration roadmap should map out how leads and prospects convert to Person Accounts without creating unnecessary Opportunity records in the process.
What changes, and what you need to plan for
The move from EDA to Agentforce Education is not a lift-and-shift. The data models are different enough that several components your school may rely on today either don’t carry over or require deliberate replacement work. Here’s what to plan for.
| Component | Status in Ed Cloud | What to do |
|---|---|---|
| Student Success Hub | Not compatible | Case Management + OmniStudio FlexCards replace most workflows. Prebuilt Hub UI components need to be rebuilt declaratively. |
| Admissions Connect | Not compatible | Agentforce Education’s Recruiting & Admissions module replaces it. OmniScripts rebuild guided admissions workflows. Salesforce rates parity as near-complete. |
| EDA Administrative Accounts | Structural change required | The Person Account model replaces Administrative Accounts. No automated migration path exists. Manual data mapping and transformation required before migration. |
| K-12 Architecture Kit | Compatible (same kit) | The Kit installs the same way. It operates on Contact records (via the Person Account’s contact side), so student and household data structures carry over. Rebuild all page layouts from scratch – EDA layouts frequently reference deprecated objects and fields that do not exist in Agentforce Education. |
| Marketing Cloud / Pardot (MCAE) | Compatible | Both work with Agentforce Education. Use cases and existing licenses determine which to keep. Migration planning should confirm lead-to-Person Account conversion flows. |
A closer look at the trickier transitions
Success Hub
Student Success Hub provided a set of prebuilt UI components: FlexCards, advisor dashboards, success plan views, that gave advisors and student support staff a structured interface for managing student cases. In Agentforce Education, that prebuilt interface is gone. The functionality exists, but it needs to be rebuilt using OmniStudio components: FlexCards, OmniScripts, Integration Procedures, and DataRaptors.
This is not a small task, but it is a well-understood one. The upside is that OmniStudio gives schools more control over what those interfaces look like and how they connect to external data sources like a Student Information System. Schools that integrate with Ellucian Banner, PowerSchool or similar systems can pull real-time data into OmniStudio-built views without moving everything into Salesforce.
The data model differences also matter here. Success Hub tracked student cases using Advisee Case records: a record type on the standard Case object. Agentforce Education’s Case Management handles this natively, but how existing Advisee Case data maps to the new model requires explicit planning. Don’t assume the records carry over automatically.
Admissions Connect
Admissions Connect is not compatible with Agentforce Education. The replacement is Agentforce Education’s Recruiting and Admissions module, which Salesforce considers near-parity with Admissions Connect as of recent releases. The guided application workflows that Admissions Connect handled are rebuilt in OmniScripts.
If your school has done significant customization of Admissions Connect such as custom application steps, reviewer workflows, or decision logic, those need to be inventoried and mapped to their Agentforce Education equivalents before migration begins. This is one of the areas where schools most commonly underestimate scope.
Administrative Accounts
In EDA, every Contact gets an automatically created Administrative Account in a one-to-one relationship. This is how EDA manages individual student records. Agentforce Education replaces this with Person Accounts, which merge the Account and Contact into a single record.
There is no automated migration path for converting EDA Administrative Accounts to Person Accounts. The transformation requires manual data mapping. Data Processing Engine and Business Rules Engine can support parts of this logic, but the mapping strategy needs to be designed before migration begins, not during it. This is one of the first things we work through in Phase 1.
How we run the migration
We break EDA-to-Agentforce Education migrations into two structured phases. The sequencing is deliberate: some of the work that looks like migration prep is actually cleanup that needs to happen before a migration begins. Skipping it creates downstream problems.
| Phase | Workstream | Key activities |
|---|---|---|
| Phase 1 | Assessment and roadmap | Hubbl org scan, architecture review, data model audit, roadmap with sequenced milestones |
| Phase 1 | Data model cleanup | Reduce Contact record type dependency, persona indicator design, duplicate review |
| Phase 1 | Consent and preferences | CASL/consent framework, dynamic preference center build |
| Phase 1 | Compatibility decisions | Success Hub workflow mapping, Admissions Connect replacement scoping, Admin Account strategy, marketing platform decision |
| Phase 2 | Data mapping | EDA-to-Agentforce Education field and object mapping, custom logic documentation |
| Phase 2 | Transformation rules | Contact-to-Person Account conversion logic, consent carryover, integration update plan |
| Phase 2 | Build and sandbox testing | Validation against real scenarios: enrollment, case management, communication preferences |
| Phase 2 | Stakeholder validation | UAT with admissions, student services, communications teams; change management prep |
Phase 1: Assessment and roadmap
We start with a Hubbl scan of your existing Salesforce org. Hubbl reads metadata health, technical debt, security risks, and automation gaps in minutes. That gives us an objective picture of what’s actually in the org before anyone makes assumptions.
From that scan, we build a sequenced migration roadmap. The first milestone is almost always data model cleanup. In most EDA orgs, Contact record types are doing too much work like representing applicants, students, alumni, families, and staff in ways that start to conflict. We replace that with checkboxes and persona indicators before Person Accounts are introduced. Doing this first makes the data mapping significantly cleaner.
We also work through the compatibility decisions in Phase 1: mapping Success Hub workflows to their OmniStudio replacements, scoping the Admissions Connect rebuild, designing the Administrative Account transformation strategy, and confirming the marketing platform approach. Leaving these for Phase 2 is one of the most common ways migrations get delayed.
For schools with CASL or similar consent obligations, the preference center and consent framework go in at this stage. That work needs to be done before any data moves.
Phase 2: Migration execution
With the roadmap defined, we build a detailed field-and-object mapping between the EDA data model and Agentforce Education. Contacts, Administrative Accounts, affiliations, program associations, case records, and engagement data all need explicit mapping. Where Salesforce provides a standard migration path, we follow it. Where custom objects or institution-specific processes exist, we document the transformation logic.
The transformation rules cover how existing Contact records become Person Accounts, how persona indicators replace record types, how consent data carries forward, how historical case data maps to the new model, and how existing integrations like Banner, web forms, and AWS will identify person records after the change.
Migration runs through sandbox cycles with validation against real scenarios: student enrollment, case management, advisor workflows, communication preferences, and Marketing Cloud journey prep. Before any rollout, we validate the future-state model with stakeholders across admissions, student services, and communications. That’s when training needs and reporting impacts surface – while there’s still time to address them.
What you’re positioned to do after
A well-executed migration opens up capabilities that are difficult to build on the older EDA foundation.
- Data 360 can unify student data across your SIS, Salesforce, and other systems into a single, actionable profile.
- Agentforce AI can handle case routing, student support automation, and early-warning signals when the data model underneath it is clean and well-structured.
- Marketing Cloud journeys run more effectively when the person model is accurate and the consent framework is solid.
- Advanced Case Management works better when knowledge content is organized and the data relationships are clean.
- OmniStudio-built student portal components and staff interfaces can pull real-time data from your SIS without requiring a full data migration into Salesforce.
None of these are automatic. They require that the migration was designed with them in mind from the start. Schools that approach this as a data project alone, rather than a platform strategy, tend to find themselves back at the drawing board within a year or two.
Summary
The short version:
EDA is not being retired by Salesforce. But Agentforce Education is where the product investment is going. Data 360, Agentforce, advanced case management, and the native Salesforce release cycle is where the innovation engine is running. For K-12 schools that want to expand how they use Salesforce, migration is the right long-term move. The path requires careful planning around Success Hub replacement, Admissions Connect scope, Administrative Account transformation, and the K-12 Architecture Kit. Done in the right sequence, it produces a simpler architecture and a platform that’s ready for what Salesforce is building next.
Next steps
The right starting point for any EDA-to-Agentforce Education migration is an assessment of your current org. That gives you a clear picture of what you’re working with, where the cleanup work is, and what a realistic roadmap looks like.
Talk to our team about what your migration would involve. We’ll show you exactly what the roadmap looks like for your school.
About Plative
Plative is an award-winning consulting firm that helps companies bring the future state of their business to life through advisory, implementation, and ongoing innovation across the Salesforce and Oracle NetSuite platforms. Plative is a Salesforce Summit Partner and Top-10 Oracle NetSuite Alliance Partner in North America.