HubSpot and Salesforce cleanup for an education company that catches term-aware usage drops at partner schools and districts

What The Term-Aware Retention Cleanup delivers

A 200+ person education and training company sells a learning platform and instructor-led programs to school districts, colleges and corporate training departments, and also enrolls individual learners whose parents often pay. Salesforce is the system of record for institutional contracts. HubSpot runs marketing, enrollment nurture and parent communications. Usage drops for weeks before anyone notices, and the reason is structural: learner activity naturally collapses during winter break, spring break and summer, so every simple alert that was ever built fired constantly and got ignored. Meanwhile parents, students and institutional admins sit in the same contact object with overlapping lifecycle stages, duplicates from every enrollment cycle, and student-level fields that should never have synced into a marketing tool. This build delivers a severity-ranked audit of the HubSpot portal and the Salesforce sync, a cleanup of settings, permissions, integrations, workflows, pipelines and properties, a hard FERPA boundary that keeps student-level records out of both CRMs, and a usage feed that compares each institution's activity to its own term calendar so a genuine drop stands out from a scheduled break. RevOps owns the system; ongoing admin from a HubSpot solutions partner keeps it working through every term change, new integration and enrollment surge.

Custom build

Salesforce stays the system of record for institutional contracts and ownership because that is where the account teams work and where renewals are forecast, so At Risk tasks land there. HubSpot is the right place to fix audience separation, consent, subscription types and parent communications, and its Salesforce connector, data quality tools and Breeze features make dedupe, property governance and a later briefing agent practical without a new platform. The usage pipeline is a custom build in n8n because term-aware baselines and FERPA aggregation are too specific for an off-the-shelf connector, and keeping the logic in one auditable workflow makes compliance review straightforward.

Signs it is time

• Account managers learn a district or college stopped using the platform only when the renewal conversation starts, often weeks or months after activity fell off
• Usage alerts exist but fire every break and holiday, so the team has stopped reading them
• Parents, students and institutional admins share one contact record type, causing wrong emails (renewal notices to students, nurture emails to district procurement)
• Student names, grades or enrollment details have leaked into HubSpot or Salesforce through form fields, LMS syncs or imports, and nobody can say what is there
• Each enrollment cycle creates a fresh wave of duplicate contacts and the Salesforce sync error queue keeps growing

Systems and data

• HubSpot portal (contacts, companies, workflows, lifecycle stages, forms, lists, user permissions, connected apps)
• Salesforce (institution accounts, contracts, renewal opportunities, account ownership) and the HubSpot to Salesforce sync settings and error log
• LMS and product activity data (for example LearnWorlds for the direct-to-learner catalog plus the core platform's event data), aggregated to institution or cohort level before it reaches any CRM
• Term and academic calendar data per institution (start dates, breaks, exam windows, end dates), captured at contract signing or onboarding
• Support desk tickets and educator pulse surveys (for example Zonka Feedback) for qualitative risk signals
• Billing and enrollment systems for seat counts, cohort sizes and renewal dates

Where your team weighs in

• The compliance or privacy owner signs off on the FERPA field list and the deletion log before any student-level data is purged, because the deletion is irreversible and may need to be documented for institutional contracts
• RevOps and customer success leadership decide the At Risk threshold per segment (a K-12 district, a community college and a corporate academy have very different healthy usage), rather than letting one default apply to all
• Account owners decide what to do with each At Risk flag (call the district coordinator, schedule teacher retraining, or mark it a known pause such as a testing window), and that outcome is logged so thresholds can be tuned
• Marketing and RevOps jointly approve audience separation rules for parents of minors, including which messages a parent may receive and when consent must be re-collected

How we keep it right

• No student-level education records (grades, attendance, course progress tied to a named student, student IDs) may enter HubSpot or Salesforce. Usage arrives only as institution or cohort aggregates, with small cohorts suppressed so an individual cannot be inferred
• Every usage alert is checked against the institution's term calendar before it fires. An account with no calendar loaded shows Calendar Missing instead of a health score, so nobody acts on a false drop
• Contacts flagged as minors are excluded from all marketing lists, enrichment and sequencing, enforced by a list-membership check before any workflow sends
• Merges, deletions and sync mapping changes run in a sandbox or on a sample first, with a record count and rollback export saved before production changes
• Admin and super admin rights are reviewed each month, and any connected app without a named owner and a documented data scope is disconnected

How you know it works

• Median days between an institution's real usage decline and an At Risk flag reaching the account owner
• Share of At Risk flags that owners confirm as genuine (alert precision), tracked by term so break-season noise is visible
• Gross renewal rate and logo retention for institutional accounts, compared term over term
• Duplicate rate and open Salesforce sync errors, measured at the start and end of each enrollment cycle
• Number of fields or records containing student-level data found in the monthly scan (target zero)

From pilot to live

1. First slice: audit, FERPA boundary and one segmentComplete the severity-ranked audit, purge student-level data, fix critical permissions and sync errors, then load term calendars and turn on the usage feed for one segment (for example higher education accounts renewing in the next two terms). Owners work the flags manually and record outcomes.
2. Expand: audiences, dedupe and all segmentsRoll out the separated audience types and lifecycle stages, finish institution dedupe with parent-child structures, extend the usage feed to K-12 districts and corporate training accounts with their own thresholds, and rebuild retention reporting in Databox.
3. Run: ongoing admin and an AI layer on topMove to monthly admin with term-calendar loading before each term. Once the data is trusted, add a custom AI agent or HubSpot Breeze agent that writes a weekly brief for each At Risk institution (usage trend against the term, open support tickets, recent survey comments, contract dates) and drafts a suggested outreach for the owner to review, never sending on its own.