Ethos Integration Overview

Last updated: October 5, 2026

Ethos is a data integration platform from Ellucian, the company behind the Banner and Colleague student information systems (SIS). In Housing.Cloud, Ethos acts as a bridge between your housing management system and your institution’s SIS, keeping data accurate, consistent, and up to date across both systems.

This bridge works by synchronizing data in both directions and using indexing, a process of matching IDs, so Housing.Cloud records connect to the correct SIS records for students, beds, terms, and other entities.

While Housing.Cloud handles the technical setup, housing administrators benefit from understanding how Ethos works, how data flows, and how to identify or resolve sync issues with their IT or integration teams.

For a technical introduction to Ellucian’s platform, visit Ellucian’s Ethos overview.

 

Data Flow: Ingress and Egress

Housing.Cloud’s Ethos integration supports both one-way and two-way data synchronization. These sync behaviors are categorized into two directions: ingress, for data flowing into Housing.Cloud, and egress, for data being exported from Housing.Cloud to your SIS.

 

Ingress (Data Coming Into Housing.Cloud)

Profiles (student and staff records) are the most visible data type imported into Housing.Cloud via Ethos. These profile imports ensure the housing system reflects accurate identity, contact, and enrollment details from your SIS. Profile data is only ingressed. Housing.Cloud does not export (egress) profile records back to your SIS.

Ingress also powers indexing, which is the process of linking Housing.Cloud records to their SIS equivalents by storing their Ethos IDs. Examples of ingressed data used for indexing include beds, buildings, term codes, financial detail codes, and meal plans. While this data may not be directly referenced by admins day-to-day, it is essential for ensuring outbound records like transactions, residencies, and meal plans are properly connected to the SIS.

 

Egress (Data Sent From Housing.Cloud to Your SIS)

Most Housing.Cloud data flows outbound to your SIS through Ethos. These egress records include:

  • Residencies (Housing Assignments): Sent when students are assigned, transferred, or removed from on-campus housing.
  • Meal Plans: Exported when a student selects or changes a meal plan.
  • Transactions: Includes housing and dining-related charges or refunds.

Each outbound record is packaged into a structured payload containing all required references such as IDs for the student, bed, building, term, and financial codes. Without correct indexing, these egress processes will fail.

 

Indexing and External IDs

To export records accurately, Housing.Cloud must know exactly how the SIS refers to each object. This process is known as indexing. Indexing connects internal Housing.Cloud records to their SIS equivalents by storing the Ethos ID for each entity. These Ethos IDs are commonly known as External IDs in the Housing.Cloud platform.

Example: When a housing assignment is sent to the SIS, Housing.Cloud can include up to 15 or more External IDs in the payload, one for each connected item: the student, the term, the building, the bed, the charge code, the meal plan, and more. These External IDs ensure that the record will be correctly recognized and processed by the SIS for proper data storage.

Indexing must be completed before any outbound records can sync. Housing.Cloud provides setup tools and workflows to help institutions store External IDs for key entities, including:

  • Profiles
  • Housing Cycles
  • Inventory (buildings, rooms, beds)
  • Meal Plans
  • Charge Codes (AR or Detail Codes)

External ID fields are displayed across the platform on records that sync with Ethos. If an External ID is missing or incorrect, the record may fail to export or trigger a sync error. Technical documentation on the indexing process can be found here.

 

Managing the Integration in Housing.Cloud

To help institutions monitor their Ethos integration, Housing.Cloud includes built-in features that make sync health and troubleshooting more accessible. These tools allow admins to:

  • View the sync status of records and their External IDs
  • Identify records that haven’t synced or may be failing
  • Perform manual sync checks to update data in real-time
     

Ethos and Transactions

The Clean Up Failures feature is a particularly useful tool in this process. It enables Housing.Cloud to recheck Ethos for transactions that may have been created in the SIS but didn’t return a confirmation. In some cases, Ethos times out or responds incompletely, which can leave Housing.Cloud in an uncertain state. This cleanup process detects those cases and fills in the correct Ethos ID if the SIS accepted the record.

Learn more about managing ethos transactions here.