CASE STUDY • hubspot • integration & custom build
Learn how an online education business connected Thinkific and HubSpot using Make as middleware—building a scalable custom enrollment object, five targeted data routing scenarios, and a comprehensive end-to-end quality pass against a 20-point testing checklist.
PROJECT SNAPSHOT
CLIENT TYPE
Online course business with an established HubSpot CRM
INDUSTRY
Online education & coaching
ENGAGEMENT
Defined-spec execution build
TIMELINE
2 Weeks, now ongoing maintenance
HubSpot
Thinkific
Make
CRM Architecture
Custom Objects
API/Webhook Integration
Middleware Architecture
Stripe Payments
No Migrations
- THE problem
The company ran its online learning academy on Thinkific and managed its core customer relationships inside HubSpot, but the two applications were completely siloed. When a student enrolled in a class, hit a milestone, stalled halfway through a lesson, or applied a coupon code, none of that behavior reached the CRM. This left the marketing and sales teams blind to active student progression.
What made this specific engagement unique was the client's level of preparation. They didn't need assistance mapping out their business goals; they had already produced a highly detailed, 28-page technical implementation blueprint. Every custom HubSpot property, data variable, webhook payload, and middleware routing logic was completely mapped out on paper. They were looking for an advanced systems operator to build their design exactly to spec.
The core engineering restriction was deep custom-object experience. Student enrollment variables could not be dropped into flat, loose contact fields that get overwritten during future classes; the architecture required a standalone custom object table natively associated with individual profiles. The build demanded clean REST API configurations, precise webhook conditioning, and error-proof routing.
The Solution: The technical system was configured and launched exactly to the client's documentation. By building a native enrollment custom object inside HubSpot and managing Thinkific payload variables through five dedicated Make scenarios, the new pipeline automates user data delivery, flags student lesson retention issues, and maps user behavior under a single source of truth.
- THE SYSTEM
- the build
Cramming recurring student data into standard contact fields ruins a CRM's long-term database integrity. Because a single user can enroll in multiple courses over their lifecycle, flat fields would let newer signups overwrite previous completion data.
We engineered a standalone HubSpot custom object with its own property schema, so the system scales sideways as new courses are added to the catalog.
Dumping diverse webhooks into a single catch-all scenario creates a fragile pipeline that crashes under mixed payloads. The middleware was divided across five isolated Make scenarios.
Each one parses a single event type \u2014 progress, enrollment, payment \u2014 so a bug in one pathway never takes down the rest.
Syncing clean data into a CRM is only half the battle; the platform has to act the second a new record lands. We deployed six targeted object-based workflows natively inside HubSpot.
They watch the live state of a learner to fire welcome sequences, launch retention tasks the moment someone stalls, and alert sales on high-intent behavior.
Flooding a database with custom properties without structure turns profiles into unreadable noise. We isolated the backend fields into clearly labeled HubSpot property groups.
Relationship metrics sit apart from core organizational data, so any employee opening a file sees a clean, logical breakdown instead of a wall of fields.
- THE LIFECYCLE
- the SHIFT
FOR THE OWNER
Enrollment, progress, and completion all flow into HubSpot as structured records — so the CRM finally reflects where each contact actually is in their learning.
FOR THE TEAM
Welcome sequences, stall detection, and sales alerts trigger off the enrollment object, not a manual guess — so the right follow-up happens the moment it should.
FOR THE LEARNER
Members kept their access, subscribers kept their billing, and buyers get instant delivery. The migration happened underneath them without anyone noticing.
READY TO WORK?

Helping online professionals build the backend systems that reflect the quality of the work they actually do.
On this side of the internet we fully celebrate all colors, genders, and lifestyles and fully back minority and LGBTQ led businesses.
And honey, if you can’t roll with that consider this one less tab in your browser to keep open.