How an institution running Ellucian Banner or Colleague can bring applicants, admission decisions, enrollment, programs and graduates into HubSpot through Ellucian's Ethos Integration, so recruitment, retention and alumni teams work from one record per student, with the registrar deciding what student data HubSpot may hold.
Banner and Colleague are Ellucian's student information systems. They hold the official record of who applied, who was admitted, who enrolled and who graduated. HubSpot is where recruitment, student engagement and advancement teams plan and send their communications.
Public documentation. The client's own admin issues credentials, with no vendor approval needed.
Open API. Ethos APIs follow Ellucian's published data model. The institution's Ellucian administrator creates the Ethos Integration application and its API key.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
Ethos Integration gives Banner and Colleague one standard API layer, so both systems feed HubSpot the same way.
Campaign Creators assessment
Ellucian's Ethos Integration is a cloud service that sits in front of Banner and Colleague. It exposes the Ethos Data Model, a shared higher-education data model, through a proxy API for reads and writes, and it places change notifications in a subscriber queue for each integration application. CC builds a sync module that reads those notifications, fetches the changed person, application or program record, and writes it to HubSpot. One build pattern works for either system. Two things set the pace: the institution's Ellucian administrators create the Ethos Integration application and choose which resources it may read, and the registrar and compliance office decide, under FERPA, which student data HubSpot may hold.
Ratings are CC judgments from Ellucian's public SDK documentation and product materials. Resource names, versions and the institution's Ethos configuration are confirmed with its Ellucian administrators during discovery.
Ethos Data Model resources such as persons, admission-applications and student-academic-programs look the same whichever system sits underneath, so the HubSpot mapping is built once.
Once a student enrolls, FERPA governs their education records. HubSpot should hold only what each team acts on, such as status, program and term, never transcripts, grades or financial aid detail.
The institution's Ellucian administrators set up the Ethos Integration application and its resource subscriptions, and the registrar signs off which fields reach HubSpot before any build starts.
Seven parts of the Ellucian stack matter to HubSpot. Four carry the integration, two enrich it, and one is a scope decision the registrar makes.
The cloud service every call goes through. An API key from an Ethos Integration application is exchanged for an access token, and the proxy API reads and writes Ethos Data Model resources.
When a subscribed record changes in Banner or Colleague, Ethos Integration places a notification in the application's queue. The sync module consumes it and updates HubSpot.
The person record behind every prospect, applicant, student and graduate, with names, emails, phones and addresses.
Applications by program and term, application status and admission decisions. These drive the recruitment funnel in HubSpot.
The program catalog and the term calendar. They become HubSpot options for program of interest and entry term, and can fill HubSpot's Courses object.
Whether a student is active in a program, and the credential they earned. These move a contact from student to alumni in HubSpot.
Grades, holds, financial aid and account balances stay in Banner or Colleague. The registrar decides which, if any, student status signals HubSpot may hold.
Banner or Colleague publishes changes through Ethos Integration. A CC-built integration layer consumes the notifications, fetches the full record, applies the registrar's field rules and writes to HubSpot. A small number of HubSpot actions can write back through the same proxy API when the institution allows it.
Admission decisions, enrollment and credentials are official in Banner or Colleague. HubSpot reads them and never edits them.
Prospect inquiries, email engagement, event attendance and communication preferences live in HubSpot, and flow to Ellucian only if the institution asks.
The sync module carries only the fields on the signed list. Anything else is dropped before it leaves the integration layer.
Each phase ends on a gate the client signs off before the next begins. Admissions goes live first, then enrollment and alumni.
Confirm whether the institution runs Banner or Colleague, which Ethos resources are available, and which teams use HubSpot. Meet the registrar and compliance office to agree what student data HubSpot may hold.
The institution's Ellucian administrator creates an Ethos Integration application for HubSpot, issues its API key and subscribes it to the agreed resources. CC confirms the regional endpoint.
Agree how a person matches between systems (Ethos person ID, then email), how lifecycle stages map to application status and enrollment, and who owns each field.
Create the properties, the admissions pipeline, the Courses object setup for programs, association labels and the Ellucian property group in a HubSpot sandbox.
Build the queue reader, record fetcher, identity resolver, FERPA field filter and HubSpot writer, with idempotent writes and an error replay queue.
Load current applicants and active students for an agreed set of terms through the proxy API, then load the program catalog.
Build nurture, yield and deposit-reminder workflows with sends paused, run two weeks in parallel, then switch on.
Resource names follow the Ethos Data Model. Exact properties and resource versions are confirmed against the institution's Ethos Integration tenant in the access phase.
| Ellucian field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Persons · contacts | ||||
| persons.id | ell_person_id | Contact | ELL → HS | Primary match key. Unique. |
| persons names (first, last, preferred) | firstname, lastname, ell_preferred_name | Contact | ELL → HS | Fill blanks only; HubSpot edits stay in HubSpot. |
| persons emails (by type) | email, ell_institution_email | Contact | ELL → HS | Personal email for recruitment; institution email once enrolled. |
| persons phones | phone, mobilephone | Contact | ELL → HS | Normalize to E.164. |
| addresses (mailing) | address, city, state, zip, country | Contact | ELL → HS | Mailing address only. |
| Inquiry from HubSpot form | persons (new) | Person | HS → ELL | Only if the institution allows writes; match before create. Confirm in discovery. |
| Admissions · applications | ||||
| admission-applications.id | ell_application_id | Deal | ELL → HS | One deal per application in an admissions pipeline. |
| Application program | ell_program_of_interest | Deal, Contact | ELL → HS | Values from academic-programs. |
| Application academic period | ell_entry_term | Deal, Contact | ELL → HS | Values from academic-periods. |
| Application status | dealstage | Deal | ELL → HS | Started, submitted, complete, decision. Confirm status codes in discovery. |
| Admission decision | ell_admission_decision | Deal | ELL → HS | Admit, deny, waitlist. Confirm resource in discovery. |
| Admission decision date | ell_decision_date | Deal | ELL → HS | |
| Application type (first-year, transfer, graduate) | ell_applicant_type | Contact | ELL → HS | Drives nurture tracks. |
| Enrollment & deposits | ||||
| Enrollment deposit received | ell_deposit_paid | Deal | ELL → HS | Yes or no plus date. Confirm source resource in discovery. |
| student-academic-programs status | ell_enrollment_status | Contact | ELL → HS | Active, inactive, completed. |
| student-academic-programs program | ell_current_program | Contact | ELL → HS | Program the student is enrolled in. |
| Lifecycle stage | lifecyclestage | Contact | ELL → HS | Prospect, applicant, admitted, enrolled, alumni. Computed in the integration layer. |
| Programs, credentials & alumni | ||||
| academic-programs (id, title, level) | Course record (hs_course_name) | Courses object | ELL → HS | Program catalog for forms, lists and reports. |
| academic-periods (code, start, end) | ell_entry_term options | Contact, Deal | ELL → HS | Refreshed on a schedule. |
| academic-credentials earned | ell_credential_earned | Contact | ELL → HS | Degree or certificate title. |
| Credential date | ell_graduation_date | Contact | ELL → HS | Moves the contact to alumni lists. |
| Advancement constituent status | ell_constituent_type | Contact | ELL → HS | Only where the institution runs Ellucian advancement. Confirm in discovery. |
Access runs through the institution's own Ethos Integration tenant. Values Ellucian does not publish are marked for confirmation.
| Topic | Ellucian | HubSpot |
|---|---|---|
| Access model | An Ethos Integration application created by the institution's Ellucian administrator. The application's resource list limits what the sync module can read or write. | Self-serve in the client portal. Custom objects need an Enterprise subscription; the Courses object is activated by a Super Admin. |
| Authentication | The application's API key is exchanged for a short-lived access token (a JWT), which the sync module refreshes before it expires. Confirm token lifetime in discovery. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Interfaces | Ethos Integration proxy API for Ethos Data Model resources (/api/{resource}), change notification consume, and the errors service. Banner- or Colleague-specific APIs only where the Data Model has no resource. Confirm in discovery. | REST APIs: CRM objects, associations, pipelines, Courses object. |
| Change notifications | Pulled from the application's subscriber queue. Up to 1,000 messages per call with a 1 MB response limit; a last processed ID lets the module re-read messages it did not finish. | Writes are immediate; batch endpoints handle volume. |
| Endpoints & regions | Cloud endpoint at integrate.elluciancloud.com, with regional endpoints for institutions outside the US. Confirm the region in discovery. | Single global API. |
| Rate limits | Not published. Confirm with Ellucian. | Per-10-second burst and daily limits by subscription tier. |
| Sensitive data | Education records are governed by FERPA. The registrar's field list is enforced in the integration layer. | Sensitive data properties available on Enterprise; field-level permissions by team. |
Severity reflects impact on the SOW, not technical difficulty alone.
Once a student enrolls, their education records are protected. The registrar decides what HubSpot holds, and the SOW lists every field. Anything not on the list is dropped by the sync module.
The API key, resource subscriptions and region come from the institution's Ellucian administrators. Make Ethos access a client-owned dependency in the SOW, with a date.
Application status and decision codes are configured locally in Banner or Colleague. The lifecycle map translates each code, and new codes raise an alert instead of failing silently.
A graduate may apply again, or a staff member may enroll. The Ethos person ID keeps one HubSpot contact, and lifecycle rules decide which stage wins.
Many institutions do not let outside systems create SIS records. If HubSpot inquiries should reach Ellucian, matching runs before any create, and admissions staff review possible duplicates.
Ellucian's detailed resource documentation sits with the institution's Ellucian access. Budget a short discovery spike to confirm resource versions and properties.
Applications, decisions and deposits arrive as they change, so HubSpot reports show the same numbers the admissions office reports, by program and term.
Prospects and applicants get communications for the program and entry term they chose, from the same catalog the SIS uses.
Admitted students who have not paid a deposit get reminders and counselor tasks, and stop the moment the deposit posts.
When a credential is earned, the contact moves to alumni lists automatically, ready for advancement and graduate program outreach.
Where the registrar approves it, an enrollment status change triggers student success outreach, using status only, not records.
Inquiry, application, enrollment and graduation sit on one contact, so leaders see conversion from first touch to alumni.
Each stage is owned by one system. HubSpot runs the conversation, Banner or Colleague keeps the official record, and the sync module keeps them in step.
All custom properties use the ell_ prefix in an Ellucian property group. Lifecycle stage is calculated in the integration layer so every report agrees.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| ell_person_id | Ellucian Person ID | Contact | Single-line text | persons.id; unique |
| ell_preferred_name | Preferred Name | Contact | Single-line text | persons names (preferred) |
| ell_institution_email | Institution Email | Contact | Single-line text | persons emails, institution type |
| ell_program_of_interest | Program of Interest | Contact | Dropdown | academic-programs; inquiry or application |
| ell_entry_term | Entry Term | Contact | Dropdown | academic-periods |
| ell_applicant_type | Applicant Type | Contact | Dropdown | Application type |
| ell_application_id | Ellucian Application ID | Deal | Single-line text | admission-applications.id; unique |
| ell_admission_decision | Admission Decision | Deal | Dropdown | Latest decision on the application |
| ell_deposit_paid | Enrollment Deposit Paid | Deal | Single checkbox | Deposit posted in the SIS |
| ell_enrollment_status | Enrollment Status | Contact | Dropdown | student-academic-programs status |
| ell_credential_earned | Credential Earned | Contact | Single-line text | academic-credentials |
| ell_graduation_date | Graduation Date | Contact | Date picker | Credential date |
Choose the Ellucian data for this engagement and the direction each field syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.
Based on public documentation. Resource names, versions, status codes and regional endpoints are confirmed against the institution's Ethos Integration tenant in the access phase.
Yes. Ellucian's Ethos Integration gives Banner and Colleague one standard API layer: an Ethos Integration application's API key is exchanged for an access token, and the proxy API reads and writes Ethos Data Model resources. Campaign Creators builds a custom sync module on these APIs once the institution's Ellucian administrators grant access.
Persons, admissions applications and decisions, enrollment status and academic programs sync from Ellucian to HubSpot contacts, an admissions pipeline and the Courses object, driven by Ethos change notifications. HubSpot can send new person or inquiry records back to Ellucian only where the institution allows writes.
The student information system owns the official record: admission decisions, enrollment and credentials are worked in Banner or Colleague, and HubSpot never edits them. HubSpot owns the conversation, holding prospect inquiries, email engagement and communication preferences, plus only the student status fields the registrar approves under FERPA.
Seven phases, each closed by a client sign-off: discovery and data governance with the registrar, Ethos Integration access through an API key and resource subscriptions from the institution's Ellucian administrator, identity and lifecycle rules, the HubSpot data model, the build, backfill by term, and a two-week parallel run before workflows switch on.
Timeline and cost depend on the Ethos resources the institution subscribes to, the field list the registrar approves and the terms being backfilled. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.