How does it work?
The Ellucian integration is bi-directional, meaning data is synced in two directions:
- Element451 → Ethos
- Ethos → Element451
Element451 uses a contact-centric data model, so all integration processing occurs at the contact level rather than the application or opportunity level. When a sync is triggered, the entire contact record is processed.
This includes:
- Biographic and demographic information
- Contact details
- Previous schools
- Family members and emergency contacts
- Applications
Data Sync Behavior
In most cases, data sent during a sync will update the corresponding record in the destination system. However, certain data types include safeguards to prevent unintended overwrites.
Previous Schools
- Records where the previous school matches the partner institution are excluded from sync to prevent conflicts with transcript data.
- In Colleague, some previous school fields may exist outside of Ethos. If those fields are populated manually, a sync can overwrite them.
- To prevent this, Element451 only creates previous school records in Colleague and does not update existing ones.
- In Banner, previous school records can be created and updated.
Applications
- Applications that are started but not submitted, or missing a major/program, cannot be accepted by Ethos and will not be sent.
- If an application cannot sync, an error will appear in the integration logs for that specific application.