The Object Model: How SGA Data Maps to HubSpot

Last updated: July 6, 2026

Summary

The integration syncs data one direction, from SGA into HubSpot. SGA remains your system of record; HubSpot is where you segment, email, and automate. To use HubSpot well, it helps to know how each thing in SGA shows up here — because a single SGA member becomes more than one HubSpot object, and the detail you'll segment on (program, branch, dates) lives on specific objects. This article is the map.

How SGA entities map to HubSpot

In SGA	In HubSpot	What it represents
A member (person)	A Contact and an SGA Member record	The person — as both a marketable contact and a complete member record
A program/class/membership registration	A Deal with one or more Line Items	Something the person signed up for
The catalog of offerings	Products	The master list of programs, memberships, and fees

Contacts — the people you market to

Every member eligible to be marketed to syncs as a HubSpot Contact. Contacts are the marketing surface: they hold identity, contact information, membership status, and household indicators, and they're what you enroll in lists and workflows.

Young children are intentionally not created as contacts (see Households, Minors, and Who Receives Program Emails for the exact threshold and the reasoning). They still exist in HubSpot — as SGA Member records — so no one is lost, but they aren't emailed directly.

SGA Member records — the complete member picture

Alongside contacts, the integration maintains a dedicated SGA Member object. This holds a record for every member, including those too young to be contacts, plus richer membership detail (active-membership specifics, household relationships) than the contact carries.

Why two objects? The contact is the streamlined, marketable version of a person. The SGA Member object is the faithful, complete mirror of the member and their relationships. Keeping them separate lets marketing stay clean while the full member context — and the family structure — remains available for reference and association.

Deals — a person's registrations

Each registration a member makes becomes a Deal. A deal represents the registration event and is associated to the person who registered. Membership renewals, program sign-ups, and similar all arrive as deals, distinguished by their line items and stage.

Line Items — what was actually registered for

The specifics of a registration — program/class name, branch, product type, activity code, status, price — live on the Line Items attached to the deal, not on the deal header. This matters: when you build program-based lists, you're filtering on line-item detail. See How to Build a Program-Based List.

Products — the catalog

Every offering is a Product. Products carry the program name, type, branch, session begin/end dates, time, and pricing. Line items reference the product that was registered for, which is how a registration connects to its real dates and catalog detail.

How the objects connect

At a glance, the associations look like this:

        Contact ──────────── Deal ──────────── Line Item ──────── Product
           │                  │
           │                  │
      SGA Member ─────────────┘
           │
   (household / primary relationships)

Contact ↔ Deal — links a person to their registrations
Deal ↔ Line Item — links a registration to what was registered for
Line Item ↔ Product — links the registration to the catalog entry (and its dates)
Contact / Deal ↔ SGA Member — ties the marketable contact and the registration back to the complete member record
Household / primary relationships — connect family members to one another (central to routing a child's program emails to the right adult — see Households, Minors, and Who Receives Program Emails)

In HubSpot, you'll see these on each record's Associations panel, and you'll traverse them in the Lists and Workflows tools using cross-object filters (for example, contacts who have an associated deal or line item matching a program).

Note on HubSpot tiers: Cross-object list logic and custom-object access depend on your HubSpot subscription tier. If an associated-object filter isn't available in your portal, check your Marketing/Enterprise entitlements or ask your implementation partner.

Where to find what (quick reference)

You want to segment on…	Look on…
Program / class name	Line Item (and Product)
Branch / location	Line Item, Product, or Contact
Member vs. non-member	Contact (active-membership property)
Actual class start date	Product (begin date)
Household / who's the primary adult	SGA Member relationships