Prerequisites and Compatibility

Operational Requirements

You can install EDA in Enterprise and Unlimited Edition Lightning Platform orgs. The profiles and layouts that come with Enterprise Edition or higher are required. For development and testing, you can use a Developer Edition org.

EDA K-12 Architecture Kit is primarily a data architecture providing objects configured for education. Access to the standard Account and Contact objects is required. Access to the standard Case object is required if you use the preconfigured behavior management features. 

License requirements depend on your business requirements. If you have questions about license types, see User Licenses in Salesforce Help and consult with your Account Executive.

• Implementations commonly rely on Service Cloud licenses (typically to manage student enrollment, counseling, or case management) or Sales Cloud licenses (typically to draft quotes and invoices for students). 

• If your requirements include setting up an online portal for applicants to apply, check on application status, and add supporting documents, consider augmenting with Marketing Cloud and communities licenses. 

• With a Lightning Platform license, users can access EDA K-12 Architecture Kit in that they can access the Account object, the Contact object, and the package's custom objects. However, this limited access can be insufficient for CRM workflows commonly used alongside EDA K-12 Architecture Kit, such as those using the Case, Lead, Opportunity, or Campaign objects.

• If you're using a Salesforce for Education product built on top of EDA, such as Advisor Link or Gift Entry Manager, keep in mind that each product has its own operational requirements.

• My Domain must be enabled in your org before you install EDA K-12 Architecture Kit. To find out if My Domain is enabled, from Setup, search for and select My Domain. To learn more, including how to enable My Domain, see My Domain in Salesforce Help.

NPSP and EDA Compatibility

EDA and Nonprofit Success Pack (NPSP) are not intended to be installed in the same org. If you install them together, Salesforce.org cannot provide support for your org.

There are multiple reasons why the two products can't coexist, such as:

• We don't test this scenario, so any release could potentially introduce changes with unintended and unpredictable results.
• Table-Driven Trigger Management (TDTM) in EDA and NPSP conflict in their handling of Accounts, Addresses, Affiliations, Relationships, and Contacts.
• Both NPSP and EDA have Household Account models, but they behave differently. Including both of these products in the same org can lead to unpredictable trigger behavior.

Existing Salesforce Orgs and EDA

If you're considering installing EDA in an existing org, analyze custom objects you've created and map them to EDA objects to determine whether it's a good fit. If processes in your existing org are very different from your intended use of EDA and you expect little to no overlap between your current org's data and the data in EDA, consider implementing EDA in its own org with an integration to your existing org.

EDA and Person Accounts

EDA doesn't support Person Accounts. However, you can install it in an org with Person Accounts enabled.

If Person Accounts aren’t already enabled, don't enable them because you can't turn off the feature after it's enabled. To completely remove Person Accounts, you need to apply for a new Salesforce org and request a license transfer. Then migrate existing data from your current org to the new one. Ask your Account Executive for help with this process.

If you must leave Person Accounts enabled:

• Make sure that you do not use the Person Account record type to manage your student records. Instead, use the Administrative or Household Account record type.

• If you plan to do lead conversion, make sure that the Person Account record type isn't set as the default record type for the profile of the user who is converting the lead.