How Leads Become HubSpot Contacts
Reframed from Gab's April 2026 "Automated Lead Generation Sequence." Unlike most other training courses, this one isn't really a MOM-to-APSync migration story — this part of the flow already runs entirely in HubSpot. What's below is how it works today, plus two real open issues worth knowing about before you trust it blindly.
What you did before
Before HubSpot owned lead capture, a website form submission or ad click had no automatic record — there was no single system tracking where a prospective customer came from before Sales ever spoke to them. Getting that history meant asking the customer directly or piecing it together from email threads.
What happens now (all automatic, no action needed from you)
- A prospective customer clicks a Google Ad, finds the site through search, or fills out a website form (the account login form, checkout, the eNews signup, or a Free Preview form) — HubSpot's tracking code is already watching the session before any of this happens.
- HubSpot creates a Contact Record automatically, populating Email, First/Last Name, IP Country/State, a HubSpot ID, and a Lifecycle Stage (starts at "Lead").
- HubSpot tags the contact with an Original Source property — Paid Search (with the keyword/campaign), Organic Search, Direct Traffic, Referrals, AI Referrals, or Offline Sources — so you can see what actually brought them in before you ever talk to them.
- HubSpot looks at the contact's email domain and either associates them with an existing Company record or creates a new one automatically.
- Based on the form, ad, or lead score, HubSpot sends a notification to the Contact Owner (assigned by a state-based workflow) — this is the handoff point where Sales picks up: review the HubSpot record for history before calling, sequencing, or starting a quote/invoice. See Taking a Customer Order for what happens next.
Two real open issues, not yet resolved
- State field sometimes doesn't populate. A number of contacts end up with no State value even though the underlying order data has one — the exact mapping gap hasn't been found yet. A workflow was built to backfill State from a state abbreviation, but it doesn't appear to be working. If you notice a contact missing State, don't assume it's a one-off — it's a known, tracked gap.
- HubSpot ID vs. the legacy customer number isn't fully mapped for everyone yet. Existing customers have a MOM
CUSTOMER #; HubSpot also assigns its own Contact ID. How reliably those two line up for every contact hasn't been fully confirmed.
If you're not sure
Use Submit an Issue and include the contact's email and which field looked wrong — the same guidance as Start Here for Marketing.