HubSpot Contact Disappeared? The 7 Causes and How to Get It Back

How to tell which cause you have

Match what you are seeing to the row that fits, then jump to that cause. When in doubt, start at cause 1 and work down.

1. Is a view filter hiding the contact?

Start with the simplest cause. Filters on your contacts index page narrow which records you see, and a saved view can carry old filters you forgot about. Open the All Contacts view, clear every filter, and search the contact's email in the search bar. If the contact appears, nothing was ever lost.

Saved views remember their filters, and it is easy to open a view that quietly excludes the contact you want: a lifecycle stage filter, an owner filter, or a create date range. The fastest check bypasses views entirely. Use the global search bar at the top of HubSpot and search the contact's email address, then their name.

2. Do you have permission to see the contact?

HubSpot view permissions can be set to All contacts, Their team's contacts, or Their contacts. Users limited to Their contacts only see records assigned to them on index pages, in lists, and in reports. If ownership changed, the contact simply stops appearing for that user. It looks deleted, but it is not.

Per HubSpot's user permissions guide, admins set CRM view access per user, and there is an optional Unassigned checkbox that also exposes unowned records. Without it, a contact with no owner can be invisible to a restricted user too.

The remedy: ask a Super Admin, or a colleague with All contacts access, to search for the record. If they can see it and you cannot, the contact was never lost. Its owner changed, or your access did. Adjust the ownership or the view permission and it reappears.

3. Was the contact deleted and sent to the recycle bin?

Deleted contacts are restorable for up to 90 days. Go to CRM > Contacts, click Actions in the upper right, then Restore records. Filter by date, select the contact, click Restore, and confirm. If you find the contact there, this is your cause, and HubSpot's own tool fixes it for free.

Three gotchas from HubSpot's restore documentation before you rely on this:

• * The restore tool can only display and restore up to 10,000 records at a time.
• * A contact cannot be restored if an active contact's email matches the deleted contact's email. The community-endorsed workaround, from a thread HubSpot staff participated in, is to change the conflicting email on the active record first, then restore.
• * If a workflow deleted the contacts, turn off or delete that workflow before restoring, to prevent a delete loop.

Also note HubSpot's warning that when you restore a contact, some of the data associated with them will still be lost. A restore is not always a complete round trip.

4. Was it a GDPR (permanent) delete?

Permanent or GDPR-related deletions never enter the recycle bin, so they cannot be restored. HubSpot also blocklists the deleted contact's email, so you cannot re-add it through the UI or an import. The contact can only return through contact-initiated actions, such as submitting a form on your website, or through an API request.

You can tell a permanent delete apart at deletion time: HubSpot's dialog warns the contact will be permanently deleted and you'll be unable to restore it. From the user's perspective the record is gone immediately, though HubSpot notes the backend purge may take up to 30 days.

Per HubSpot's GDPR delete documentation, if a well-meaning teammate used permanent delete for routine cleanup, that is unfortunately the whole story. Tightening delete permissions is the practical prevention.

5. Did an import or integration change the contact?

Review your import history and any connected integrations before assuming data loss. An import that updated existing records, or a sync tool with its own deduplication rules, can change the email or name you search by. Check recent imports, integration sync logs, and any data quality automation that ran recently.

• ✓ Check the import history for imports that ran around the time the contact vanished.
• ✓ Review sync logs in any connected integration or data sync tool, which keep their own change records.
• ✓ Look for dedupe or cleanup automation that may have altered identifying fields.

6. Did a teammate merge the contact into another record?

This is the cause nobody checks. When two contacts merge, they become one record, and the secondary contact's email address is added to the survivor as a secondary email. HubSpot states it is not possible to unmerge records. Search the missing contact's email; if a different contact opens, a merge is your likely cause.

Here is the exact diagnosis, using HubSpot's merge documentation:

1. Search the missing contact's email in global search. In a merge, the secondary contact's email is kept on the survivor as a secondary email, so the search should land on the record that absorbed it.
2. On that record, in the left panel, click Actions, then View all properties, and search Merged.
3. Check the Merged contact IDs property. It contains the Record ID values of all records previously merged into that record.
4. Hover on the property value and click Details to see who performed the merge and the timestamp when it occurred.
5. For merges made in HubSpot's Data Quality tool: go to Data Management > Data Quality > Manage Duplicates, click Actions, then Export merge history. It reaches back up to 90 days and includes property values prior to the merge, but it only covers merges performed in that tool, which handles contacts and companies and requires a Professional or Enterprise subscription.

Two more merge fingerprints: the missing contact dropped out of your static lists, because HubSpot removes the secondary record from all static segments, and property values changed on the survivor, because the primary record's values win wherever both records had one.

7. Did a form cookie overwrite the contact?

HubSpot's forms can match a submission to an existing contact by browser cookie instead of email. HubSpot documents that this may result in contacts being overwritten when the same form is submitted multiple times from one device. Two people sharing a computer can end up recorded as one contact.

The guard is a form setting. In the current form editor it is called Automatically create new contacts from unknown email addresses, under the form editor's Settings on the General tab. In the legacy editor it is Always create contact for new email address, on the Options tab. Per HubSpot's forms documentation, turning it on makes every submission with a unique email create a new contact, and HubSpot won't use an existing browser cookie to associate the submission with a previously tracked contact.

One precision that matters for diagnosis: HubSpot documents this behavior as contacts being overwritten, not as two existing records being merged. An overwrite usually leaves the Merged contact IDs property empty. Look instead at the contact's property history for values that flip between two different people, and at form submissions arriving from a single shared device. A long-standing answer on HubSpot's community thread about automatically merged contacts points to the same form setting.

If the free scan from cause 6 finds no merge history, you are likely in this overwrite case. Turn the auto-create setting on to stop the bleeding, then repair the affected contact by hand using its property history. To keep a safety net for next time, CRM Data Backup & Restore by Third Space takes automated backups of your HubSpot contacts, companies, and deals.

Frequently Asked Questions