Skip to content
ancilAn INSIDEA company
HubSpot check library

HubSpot dormant contacts untouched for 180+ days

A dormant contact is one whose record has not changed in 180 days or more. When 30% or more of a database is dormant, email engagement drops and reports count people who left long ago. Segment the dormant group, run one short re-engagement attempt, and then suppress or retire the people who do not respond.

ContactsCONTACT-003Updated 2026-10-28

Why it matters

Mailbox providers watch how recipients engage. Sending to large groups of people who never open teaches them your mail is unwanted, which can push messages to spam for engaged contacts too.

If your subscription uses marketing contacts, dormant records that stay set as marketing contacts can count toward your tier. They also inflate list sizes and funnel reports, so conversion rates look worse than they are.

A dormant share this large is usually a process signal: old imports, event lists, or bought data that were never qualified or cleaned out.

How to find it in HubSpot

  1. Open CRM > Contacts and switch to the table view.
  2. Add a filter on Last modified date and choose more than 180 days ago.
  3. Compare that count with the total number of contacts, to see what share of the database is dormant.
  4. Add the Create date, Original source and Marketing contact status columns, so you can see where the dormant records came from.
  5. Save the view as "Dormant contacts 180+ days" so the team running re-engagement can reuse it.

How to fix it safely

  1. Split the dormant group by source. Customers, partners and contacts on open deals need a different conversation from old imports or event lists.
  2. Run one short re-engagement attempt, such as two or three emails over a few weeks, to the contacts who are still opted in.
  3. Give non-responders about 30 days. Then set them as non-marketing contacts or suppress them from sends, if your subscription supports it.
  4. Decide on deletion separately. Archiving or deleting contacts removes history, so agree a retention rule with the person responsible for data and privacy first.

Before you change anything: Last modified date changes whenever any property updates, including updates from workflows and integrations, so treat the count as a floor. Deletion and retention can carry privacy obligations. A responsible person should decide them, and this page is not legal advice.

How Ancil checks this

Rule
CONTACT-003
What it looks for
Counts contacts whose last modified date is 180 or more days old. Contacts with no last modified date are not counted. The finding appears only when dormant contacts are 30% or more of the contacts measured. Ancil uses HubSpot’s portal-wide count when it is available and consistent with the records read, and the contacts read otherwise.
Severity
Info from 30% to 49% dormant. Warning at 50% or more.
Evidence shown
The dormant count, the population it was measured against, whether the count is exact or from the records read, and contact IDs for up to 200 affected records.
Governed fix
Supported. Ancil drafts a re-engagement checklist for a portal owner to review: build the dormant segment, run a short win-back sequence, then suppress or archive non-responders after 30 days. It does not suppress, archive, or change the marketing status of any contact. Your team makes those changes.

Frequently asked questions

Why does Ancil use last modified date instead of last activity date?

Last modified date is a default property that HubSpot keeps on contact records, while activity dates depend on which tools your team uses. It is a conservative measure: a contact updated by a sync or a workflow is not counted as dormant, even if no person has engaged.

Should I delete dormant contacts?

Not as a first step. Re-engage them, then suppress them or set them as non-marketing. Delete only under a retention rule your team has agreed, because deletion removes history that reporting and attribution may need.

Run this check and 149 more.

Ancil connects to HubSpot read-only in about 60 seconds. Nothing changes in your portal without your approval.