Ellucian Recruit–HubSpot integration

The brief

Southern Nazarene University (SNU) needed to support the long chain of interactions behind higher-education recruitment. A prospective student may enter through a marketing campaign, move into an admissions workflow, update information over time, and require follow-up from teams working in different systems.

This project connected Ellucian Recruit and HubSpot for SNU so those systems could participate in one coordinated process instead of behaving like isolated databases.

What made it complicated

The two platforms serve different purposes and express their data differently. A field that appears simple in one system may have a different format, lifecycle, or owner in the other. Records can arrive incomplete, change after the initial sync, or conflict with information already present.

That makes the integration contract more important than the transport. The work had to account for mapping, validation, update behavior, error handling, and the operational question of what should happen when a record could not move cleanly.

The approach

I helped shape the integration around explicit mappings and predictable boundaries. Instead of treating every field as interchangeable, the workflow separated required data from optional context and kept platform-specific behavior at the edges.

The implementation emphasized:

• clear ownership for the values exchanged between systems;
• validation before a record crossed a platform boundary;
• repeatable handling for updates and incomplete submissions;
• useful failure information for the people responsible for the workflow; and
• an integration structure that could evolve as admissions and marketing needs changed.

The result was a custom bridge built around SNU’s process rather than the assumptions of a generic connector.

Why it mattered

Recruitment teams need confidence that the information in front of them represents the current prospective-student journey. Marketing teams need enough context to communicate appropriately without becoming the system of record for admissions.

By coordinating Ellucian Recruit and HubSpot through a deliberate data contract, the integration reduced the gap between those responsibilities while preserving the role of each platform.

The takeaway

The durable part of an integration is not the API call. It is the agreement about ownership, validation, recovery, and change. This project demonstrates how I approach cross-platform work where operational trust matters as much as successful data transfer.