- Institution
- University of New England, UNE Online (College of Professional Studies)
- Programs
- Graduate public health and health professions
- Replaced
- Salesforce EDA with a managed-package storefront
- Built on
- Education Cloud and Commerce on Core
- System of record
- Banner, through supported Banner APIs
UNE Online, the College of Professional Studies at the University of New England, had a Salesforce EDA org with a managed-package storefront that was generating most of its support tickets, so we rebuilt the enrollment experience on standard Education Cloud and a Commerce on Core storefront, with Banner staying the system of record.
Who UNE Online Is
The University of New England is a private university in Maine, and UNE Online is its College of Professional Studies, which runs online graduate programs in public health and the health professions for working adults who enroll year-round.
UNE Online already ran Salesforce, built on the Education Data Architecture (EDA) with a managed package handling the application and the storefront. The university talked about the project publicly at the Education Trailblazers Summit in June 2026, which is why we can name it here.
What They Had
By the university's own account, most of the support tickets the college handled came from the storefront not working, and the team was spending its time keeping it running.
"It's bad for the college and worse for me."
UNE Online, Education Trailblazers Summit, June 2026, describing the old platform.
Two constraints shaped the project. Banner is the system of record and stays that way, so anything the storefront did had to land in Banner through supported Banner APIs. The legacy org also carried other contracts with hard end dates, so the storefront had a fixed calendar while the broader migration continued behind it.
What We Built
We started with the data model and then the screens. Legacy EDA objects were mapped to standard Education Cloud objects, and the storefront was built on Commerce on Core in the same org, so a purchase and an enrollment are the same event.
| Layer | What UNE Online Runs Now | Notes |
|---|---|---|
| Learner record | Education Cloud Person Accounts, Learning Programs, and Course Offerings | Standard objects, so the college's administrators can maintain it |
| Storefront | Commerce on Core on an LWR Experience Cloud site | Program catalog, product variations, cart, and checkout with two-factor sign-in |
| Checkout rules | Custom checkout for deposits and program-specific requirements | Built as storefront components, and the order itself stays standard |
| Post-purchase automation | Flow creates enrollment records and rolls products forward by term | No Apex in the enrollment path |
| System of record | Banner, through supported Banner APIs | Never direct database writes |
| Delivery | Discovery, design review, UAT scripts and office hours, training, and documentation | Design sign-off took one day once the plan was on the table |
"We got sign-off in 1 day."
UNE Online, Education Trailblazers Summit, June 2026.
The Design Decisions That Mattered
- Education and Commerce Cloud, together. The storefront reads from the same Course Offering and pricing records the college maintains for everything else, so there is one catalog to keep current.
- Standard objects wherever one existed. Legacy custom objects were retired in favor of the Education Cloud learning model, which is how we approach every project and is why the college's own staff can run the system after we leave.
- The SIS stays the SIS. Salesforce holds the relationship, the application, and the purchase, and Banner holds the official enrollment, with the handoff on supported APIs only.
- Automation in Flow. Enrollment creation, product rollover, and notifications run in Flow so administrators can see and adjust them.
Challenges Encountered
The hardest part was sequencing. The other contracts on the legacy org set a cutover calendar the project had to respect, so the storefront opened while later phases continued in parallel, and the first weeks included manual steps the team retired one at a time as each automated handoff was confirmed.
We plan for that on every storefront now: a short list of interim manual steps, each with an owner and a retirement date.
What Changed for the College
Programs opened in phases so the team could watch each one, and the enrollment experience now runs on current Salesforce products that get three releases a year instead of a managed package layered on EDA.
Questions We Hear
Was this a migration or a rebuild?
Both. The data moved from EDA objects to Education Cloud objects, and the storefront and enrollment automation were rebuilt on Commerce on Core and Flow, since the old storefront was the problem.
Did UNE Online keep Banner?
Yes. Banner remains the system of record for enrollment, and Salesforce integrates with it through supported Banner APIs.
How long did the storefront take?
About six months from kickoff, longer than our three-month Commerce Accelerator because the scope included the migration from EDA, custom checkout rules for deposits, and a cutover calendar set by other contracts.
Can we talk to UNE Online?
Ask us. We arrange reference calls with clients whose projects look like yours, and UNE Online has told its own story publicly at the Education Trailblazers Summit.
What would you do differently?
Publish the interim manual steps on day one. Every launch has a few, and naming them with an owner and a retirement date up front keeps them from becoming a surprise.

