When a family accepts a place, their enrolment details move from HubSpot into Sentral, so your registrar reviews a draft instead of typing it in.
A custom-built integration designed around your business logic, not a plug-and-play connector.
HubSpot holds the enquiry, the tour, the application and the family’s details. Sentral is where enrolled students live. Without a connection, every enrolment is keyed a second time, with the errors that brings.
Sentral cannot search records by email address, so matching families by hand is slow. Duplicate parents and households are common.
If every new enrolment means re-typing a form, your admissions data is only as good as the last person who keyed it.
The integration writes from HubSpot to Sentral through the Sentral Enterprise REST API. It runs when an enrolment reaches the agreed stage in HubSpot.
Each record carries its HubSpot ID in Sentral. Repeated events are ignored, and existing parents are looked up before anything is written.
Accepted enrolments create a student enrolment draft in Sentral. Your registrar reviews the draft and approves it, so no student record is created without a check.
Student details, previous school, entry year and year level move across with the enrolment.
Parent and guardian contacts move across with their flags, such as primary contact, emergency contact and who receives reports.
Household and address details move with the enrolment, so the family is set up once.
If your school uses HubSpot for admissions and Sentral for enrolled students, this integration connects them. It needs Sentral Enterprise, as the REST API is only available on that edition.
Sentral stays the operational record for enrolled students. HubSpot stays the record for enquiries and admissions.