Matching your HubSpot pipeline to Summit's project statuses
Who can use it. Owners, in Settings → Integrations. It only appears once your HubSpot account is connected and deals have started syncing.
What it's for
Summit tracks every job through six statuses — lead, quoting, approved, in progress, complete, archived. HubSpot tracks the same job through *your* pipeline stages, which you named yourself.
Until now Summit assumed you were using HubSpot's out-of-the-box pipeline ("Appointment Scheduled", "Qualified To Buy", "Closed Won", and so on). If you'd built your own stages — and most builders have — Summit couldn't tell them apart: every deal arrived as a lead and stayed there, moving a deal in HubSpot did nothing on Summit's side, and when Summit tried to push a job's progress back to HubSpot the update was rejected because the stage it was aiming for didn't exist in your portal.
This screen fixes that. You tell Summit which of your stages means what, once, and both sides stay in step.
How to use it
- Go to Settings → Integrations and scroll to HubSpot Stage Mapping.
- The top list shows every stage Summit has seen on your deals, with a count of how
many deals are sitting on each. Pick the Summit status each one means. - Leave a stage on — not mapped — if it shouldn't change a job's status. A deal moving onto an unmapped stage leaves the job exactly where it was; a brand new deal found on one starts as a lead. - Several stages can share a status. If you have both "Enquiry" and "Qualifying", mapping both to lead is perfectly normal.
- Below that, choose the stage Summit writes back when *it* moves a job:
- approved — used when a Buildxact estimate is accepted. - complete — used when a job is marked complete in Summit. These are the only two moves Summit makes on your behalf, so they're the only two you need to set.
- Press Save stage mapping. It applies org-wide, straight away — the next sync
and the next webhook both use it.
Good to know
- You don't have to do anything. If you never open this screen, Summit keeps
behaving exactly as it did before, using HubSpot's default stage names.
- The stage list comes from your own deals, not from a fixed list — so it names
your real pipeline. A stage you've mapped stays on the list even after the last deal leaves it, so you can always change your mind.
- Changing the mapping doesn't re-sort existing jobs. It changes what happens
from now on. Jobs move to their new status the next time their deal changes stage, or on the next full sync.
- It's per business. Your mapping never affects another organisation's deals.
Related
- Region & tax settings
- Importing a tenant's HubSpot pipeline and automations