One of the first questions every team asks is: when a Stripe customer syncs, where does it land in HubSpot? The answer depends on what’s actually on the customer.
Routed by the names on the customer #
We classify each Stripe customer and create the matching HubSpot record(s):
| Stripe customer has… | Becomes in HubSpot |
|---|---|
| a business name | a Company |
| an individual name | a Contact |
| both | a Company and a Contact, associated |
| neither | a Company (fallback) |
This means B2B accounts roll up under a single Company, while individual buyers become Contacts — without you maintaining any rules.
Why you won’t get duplicates #
Before creating anything, we look for an existing record: first by the Stripe id we stamp on it, then by a natural key like company domain or contact email. If we find a match, we adopt it. Re-running a sync is always safe.
What gets written #
Beyond the join key, you control exactly which fields sync via field mapping rules — so the Company or Contact carries the Stripe data your team actually uses.
Want the full object model? See what syncs to what.