Why deactivated-owner records are pure leak
When a rep leaves the company, HubSpot deactivates their user account but does not auto-reassign their records. By default, every deal, contact, and company they owned stays attached to the deactivated user. From a UI perspective, the records still have an owner. From a "is anybody actually working this" perspective, they don't.
The damage compounds:
- Deals don't progress. No one is enrolled in the cadence, no one gets the close-date alerts, no one books the next meeting.
- Inbound leads route nowhere. If your assignment workflow points at the departed rep's territory, new leads are still going to them.
- Forecasts include phantom pipeline. The weighted number includes deals nobody is touching, inflating the apparent commit.
The practical recovery cost is real: every deactivated-rep record you find is a record that needs reassignment, re-enrollment in cadences, and a "let's catch up on this account" call from whoever takes it over.
What Owner status is archived actually filters
The rule is simple — find records where:
- Deal owner / Contact owner / Company owner points at a user whose status is archived.
- The record is still active — not closed, not unenrolled, not soft-deleted.
Apply the filter across all three object types: deals, contacts, companies. Reps own records of all kinds.
Why the count rebuilds after every offboarding cycle
The offboarding prompt is a one-shot. After it runs, you have to manually re-audit periodically because three things keep creating new "archived owner" records:
Stale assignment workflows. Round-robin or territory-based workflows that still include the deactivated user as a candidate. They keep pointing new leads at the archived user until you remember to remove them from the workflow.
Integration field defaults. A Zapier zap or third-party tool that has the archived user's HubSpot ID hard-coded as the default owner. New records flow in with the dead owner.
Re-imports. A spreadsheet upload where the Owner column references a deactivated user — HubSpot will set the owner anyway.
The view is easy to build. Keeping the count at zero is ongoing work — a quarterly audit at minimum, sometimes a monthly one for fast-moving teams. Each new departure creates a fresh wave of records that need reassignment, plus a new round of workflow / integration audits to stop the bleed.
The manual HubSpot recipe
Three views (one per object type), one offboarding workflow, ongoing audits to keep the workflows clean.
- Open Sales → Deals → Create viewNavigate to Sales → Deals. Click 'Create view' in the top right.
- Add filter: Owner status is archivedFilter by Deal properties →
Owner status→ 'is archived'. HubSpot has this special filter built in for exactly this case. - Add filter: Deal stage is not closed won/lostAND group →
Deal stage→ 'is not any of' → 'Closed Won', 'Closed Lost'. Closed deals don't need reassignment. - Save as 'Deals — Archived owner'Pin to your sales-ops dashboard.
- Repeat for Contacts and CompaniesSame filter (
Owner status is archived) on the Contacts and Companies indexes. Three views total — reps own records of all kinds. - Build the offboarding workflowWorkflows → Create. Trigger: when a user is deactivated. Action: reassign all their records to a fallback owner (sales-ops mailbox, manager, round-robin pool). HubSpot's built-in offboarding prompt is a one-shot — this catches records that get re-assigned by stale workflows AFTER deactivation.
What Bloated does instead
Archived-owner records, with the workflow / integration root cause traced.
Bloated cross-checks deals, contacts, companies in one view AND traces which workflow or integration is still assigning new records to deactivated users. So a record with archived owner Sarah Chen flags AS WELL AS the round-robin workflow that's still sending leads to her — fix once, problem stops.
hubspot_owner_id (status: archived) · HubSpot owner