You can see that something is wrong in HubSpot: a record is missing, a workflow did not run, or two reports disagree. What you need next is a way to isolate the cause. We recommend starting with one affected record and one expected outcome, then checking the data, rules and access behind it before changing the wider account.
For common HubSpot issues, use a simple sequence: Trace, isolate, correct, verify. Trace the affected record, isolate the first point where the result differs from your expectation, correct that cause, and verify the outcome with a controlled test. Treat this as a diagnostic approach, not a promise that every issue has a quick fix.
A broader redesign may be necessary when the underlying process is inconsistent. We would establish that from the evidence first, rather than use a failed workflow as the starting assumption for a full rebuild.
Use this routing table to choose your first check. It is a troubleshooting starting point, not a diagnosis.
| What you see | First check | Evidence to keep |
|---|---|---|
| A field or record is missing | View, object and user access | Record ID and the affected user's view |
| A stage looks wrong | The stage property and its update source | Expected stage and property history |
| Duplicates or unexpected import updates | Matching identifiers and field mappings | Source file, import result and affected IDs |
| A workflow did not produce the result | Enrollment first, then action errors | Record, expected time and failed step |
| An integration or report disagrees | Sync rules or report definitions | The same record or measure in both systems |
First separate a missing value from a value that is not displayed. For your own record view, HubSpot lets you customize the properties in a sidebar card when user customization is enabled. Those changes apply to your view. The selectable properties belong to the object you are viewing. See HubSpot's record-property customization instructions.
If a colleague can see the record or tool and you cannot, compare access before recreating data. HubSpot distinguishes subscription features, assigned seats and permissions: the seat determines tool access within the subscription, while permissions control the actions a user can take. Check the seat requirements and ask your administrator to review the specific permission. Do not grant broad administrator access just to test a missing field.
When the underlying configuration is correct but users need a repeatable way to work with it, make that part of your HubSpot onboarding and training plan.
HubSpot's Lifecycle stage property categorizes contacts and companies in the marketing and sales process. Lead Status describes sub-stages within Sales Qualified Lead. Do not use those labels interchangeably when investigating a handoff. The official lifecycle-stage guide also explains where to see the source of a property update.
Compare the expected stage with that update source before changing an automation. HubSpot documents forward-only behavior for the default Lifecycle stage when updated through tools such as imports, forms, APIs and workflows. Setting an earlier stage through those tools requires clearing the existing value first. That is a consequential data change: review its purpose and downstream rules before doing it.
Write down who owns the handoff and what qualifies a record for the next stage. We recommend agreeing on that definition as part of revenue operations before automating it.
HubSpot's duplicate manager identifies potential contact and company matches for review. It requires an eligible Professional or Enterprise subscription and appropriate data-quality and record-edit permissions. Bulk duplicate management requires Data Hub Professional or Enterprise. The duplicate-management documentation gives the current access requirements.
Do not merge records on name similarity alone. Compare the properties, associated records and values you need to retain. HubSpot states that merged records cannot be reverted. Review a pair carefully before proceeding, and investigate how the duplicate was created so the same source does not recreate it.
For a multi-object import, HubSpot requires a unique identifier to update an existing record. Record ID takes precedence over other identifiers in the file. Check the chosen create/update mode, object mappings and identifiers before running the import. Follow the current multi-object import instructions, or their linked single-object procedure when that is your scope.
The import option that prevents overwriting is not a general data-repair setting. HubSpot documents that it protects a property's existing value, including a value that was previously set and later cleared. It can populate that property on new records and on existing records that have never had a value for it. Review that distinction before expecting it to fill every blank field.
Our recommendation is to test a small approved sample, inspect the import's errors and compare the resulting records with the source file. Keep missing information marked as unknown until you have an appropriate source. Do not guess values to make a completeness report look better.
Start by separating enrollment from execution. For the full workflows tool, HubSpot lists eligible Professional or Enterprise subscriptions and requires workflow access. Its enrollment troubleshooting guide covers trigger criteria, AND/OR logic, suppression and unenrollment rules, and re-enrollment settings. An eligible record is not necessarily eligible to enroll again.
If the record enrolled, inspect the failed action instead of widening the enrollment criteria. HubSpot documents distinct action failures, including missing associated records and attempts to create records with values that must be unique. Use the workflow error reference to interpret the actual error.
Before changing a live workflow, document the intended branch and expected action for your test record. Check the version and timing involved in the original failure. Re-enrolling a real contact may repeat actions, so do not use that as an unreviewed diagnostic shortcut.
For supported apps, HubSpot data sync can run in one direction or both directions. The result depends on the selected objects, matching rules, filters and field mappings. Use HubSpot's data-sync setup guide to compare the configuration with the specific record that is failing or excluded. Connecting an app is not proof that the required sync is configured.
Custom data-sync field mappings require Data Hub Starter, Professional or Enterprise. Field types and the connected app's API restrictions can also limit what maps in each direction. Check the field-mapping requirements before assuming every property can be synchronized both ways.
Decide which system should win a conflict before changing sync direction. Preserve the current settings and test a bounded change. Avoid repeatedly saving a sync just to see what happens: HubSpot documents that saving the sync restarts its initial sync.
Compare definitions before totals. Check the underlying records, date property, date range, owner and other filters. For example, a deal report filtered on Create date is not the same question as one filtered on Close date. HubSpot's report-filter troubleshooting guidance recommends checking the source records and simplifying the report to isolate the difference.
For HubSpot and Google Analytics, also compare tracking coverage, internal-traffic filters, cross-domain settings and measurement definitions. The tools can report different session totals. HubSpot's analytics comparison guide explains several reasons. A mismatch alone does not show which implementation is wrong.
Write the agreed definition beside each important measure in your analytics and reporting plan. That gives the next investigation a clear reference point.
Escalate when you cannot reproduce the issue safely, a change could affect many records, or the evidence points to a platform or integration problem you cannot resolve within your access. Prepare the account and record IDs, timestamps, expected versus actual behavior, relevant configuration and exact error message. Share sensitive information only through an appropriate secure support channel.
For a process problem, ask for a scoped recommendation: what should stay, what should change, how it will be tested and who will own it afterward. Start with the cause and the acceptance criteria. Discuss your HubSpot issue with Selworthy.
Choose one affected record and describe the expected outcome. Check the underlying data and the first rule or action that should have produced that outcome. Keep the evidence before making a change.
Confirm the feature's subscription requirement, the user's seat and the relevant permissions first. An upgrade decision should follow that check, not replace it. Use the seat documentation linked above for the applicable requirements.
No. Review the records and the values and associations you need to retain. A suggested match is a review candidate, and HubSpot's duplicate-management documentation warns that merges cannot be reverted.
Do not assume they will. Compare the measurement definitions and tracking configuration described above, then investigate an unexplained difference. Do not change a report solely to make its total match another tool.
Product guidance checked against the linked HubSpot documentation on August 30, 2026. Feature availability and interface labels can change; confirm the requirements for your account before making changes.