agentleFS
TomGranotTomGranot/hubspot-admin-skills/skills/cleanup-lead-owners/SKILL.md

cleanup-lead-owners

Skill75 starsChanged 20 days agoMITView on GitHub

Remove non-employee users from HubSpot and reassign their orphaned contacts, companies, and deals. Pairs with the assign-unowned-contacts skill for comprehensive ownership cleanup.

  • Reads credentials

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Remove departed employees from HubSpot and reassign their CRM records.

    line 13
  2. Distinctive:

    Use the batch update API to reassign contacts to the appropriate active owner

    line 60
  3. Very specific:

    Run /assign-unowned-contacts: after reassignment to catch any records that ended up without an owner.

    line 66
  4. Very specific:

    Search for contacts where hubspot_owner_id matches any deactivated owner ID — count should be zero.

    line 70
  5. Distinctive:

    Check that no workflows broke due to owner changes (some workflows may filter by specific owners).

    line 72
  6. Distinctive:

    Keep a log of original owner assignments before making changes.

    line 77
  7. Distinctive:

    Run this whenever an employee leaves the company — do not wait for quarterly cleanup.

    line 82

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cleanup Lead Owners

Remove departed employees from HubSpot and reassign their CRM records. Orphaned records with no active owner fall through the cracks.

Prerequisites

  • A HubSpot service key (HUBSPOT_ACCESS_TOKEN in .env; an existing legacy private app token also works) with crm.objects.owners.read and contact/company/deal write scopes
  • Python 3.10+ with uv
  • A list of current employees (to compare against HubSpot users)
  • A default owner or round-robin assignment rule for orphaned records

Step-by-Step Instructions

Stage 1: Plan

Confirm with the user before starting:

  1. Who receives reassigned records — a single default owner, or territory/round-robin rules?
  2. Which flagged users should be deactivated vs merely stripped of records?

Stage 2: Before

Identify non-employee owners via the Owners API:

import os, requests
from dotenv import load_dotenv

load_dotenv()
TOKEN = os.environ["HUBSPOT_ACCESS_TOKEN"]
BASE = "https://api.hubapi.com"
HEADERS = {"Authorization": f"Bearer {TOKEN}", "Content-Type": "application/json"}

active = requests.get(f"{BASE}/crm/v3/owners", headers=HEADERS,
                      params={"limit": 100, "archived": "false"}).json()["results"]
deactivated = requests.get(f"{BASE}/crm/v3/owners", headers=HEADERS,
                           params={"limit": 100, "archived": "true"}).json()["results"]

Cross-reference with your current employee list. Flag:

  • Deactivated HubSpot users who still own records
  • Active HubSpot users who are no longer employees
  • Contractors or vendors who should not own records

For each flagged owner, count how many contacts, companies, and deals they own.

Stage 3: Execute

  1. Reassign records owned by non-employees:
    • Use the batch update API to reassign contacts to the appropriate active owner
    • Apply round-robin or territory-based rules if no specific owner is obvious
    • Reassign companies and deals associated with the same contacts
  2. Deactivate users who are no longer employees (requires Super Admin in HubSpot Settings > Users & Teams).
  3. Run /assign-unowned-contacts after reassignment to catch any records that ended up without an owner.

Stage 4: After

  1. Search for contacts where hubspot_owner_id matches any deactivated owner ID — count should be zero.
  2. Confirm all reassigned contacts have an active owner.
  3. Check that no workflows broke due to owner changes (some workflows may filter by specific owners).

Rollback

  • Owner reassignments can be reversed by batch-updating the hubspot_owner_id back to the original value.
  • Keep a log of original owner assignments before making changes.
  • Deactivated users can be reactivated in HubSpot Settings if needed.

Tips

  • Run this whenever an employee leaves the company — do not wait for quarterly cleanup.
  • Set up an offboarding checklist that includes HubSpot record reassignment.
  • Pairs with /assign-unowned-contacts for comprehensive ownership hygiene.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.