You added validation rules, and the data still disagrees. The company record says one headcount, the contact’s form says another, and an integration rewrote both overnight. Validation rules look like the fix for HubSpot data quality. What actually holds is a rule for who may write each field.
This post is for founders and revenue leaders whose reports keep showing numbers nobody trusts, even after a cleanup. The fix starts with decisions, not settings.
Why validation rules do not fix HubSpot data quality
Validation rules do one job well: they make users meet a format before a value is saved. HubSpot’s guide to property validation rules says they apply when you edit records in the CRM or import data, and to forms built in the updated form editor. The same page lists where they are not enforced: workflows, chatflows and meeting scheduling page submissions, plus forms made in the legacy editor. Existing values are not reformatted after the fact.
So a rule guards one door. Most inconsistent data comes in through the others. Think of an integration that syncs the same field, an old form, a workflow that copies a value to every contact, or an import from a trade show list. Each writer is right by its own logic, and together they disagree.
The data quality tools have the same limit. HubSpot’s guide to the data quality overview notes that a record fixed there and later updated by hand in the wrong format will not be flagged again. Cleanup without a rule about writers comes back within weeks.
Who this matters for
- Heads of sales who segment territories or route leads by company size, industry or country: these are the fields most often written by several sources.
- Heads of marketing whose lists and scoring depend on the same fields that sales edits by hand.
- Founders who paid for a cleanup and want it to stick.
If your portal has one form, no integrations and two users, you can skip most of this. The problem grows with every new writer.
What to check in your portal
- List the fields that matter for routing and reporting. Start with the ones a report or a workflow filters on, not every property.
- Find every writer for each field. Open a record, click Actions in the left sidebar and select View property history. Use the property history to note which source made each change. Check a handful of records per field. Two or more sources on one field go on your list.
- Pick one source of truth per field and an owner. Write it down in one line per field. For example, sales sets industry on the company record, and the integration may fill it only when it is empty. The owner is a person, not a team.
- Change the writers to match. For a connected app, review its sync settings. HubSpot’s field mapping guide says mappings decide which data syncs, in which direction and how conflicts are handled. Turn off workflows that copy values against your rule, and retire the old forms.
- Then add or tighten validation rules in Settings > Properties, the property, then the Rules tab, for the entry points they cover.
- Only now clean the existing values, in the order from our CRM cleanup guide. Duplicates come early: our duplicate merge rules cover which record should win.
Where an agent helps
Steps 2 and 6 are the slow ones: reading history record by record and checking the result again a month later. This is the check the Auditor agent on the Alignify platform runs. It audits a deal, its company and contacts against data-quality rules and returns a scored list of fixes. Every agent starts in review mode, and proposed updates wait for an admin’s approval before anything changes in HubSpot. The platform is in private beta with early access.
The agent does not decide your source of truth. That one-line rule per field from step 3 is still yours.
Our take
Inconsistent data is a process problem, not a tool problem. The portal mirrors the fact that three teams and two systems each believe they own the same field. A new rule, a new tool or a new hub will not settle that argument.
The honest cost is small but real: some hours of an admin’s time to list fields and writers, and one meeting with sales and marketing leads to agree the owners. If nobody on your team can own that list after the meeting, do not start the cleanup yet. It will come back, and you will pay for it twice.
Private beta
Let an agent run this check in your HubSpot
Alignify agents read the deals, emails and meetings behind every record, show the evidence and wait for your approval before they change anything.
FAQ
Why does my HubSpot data get messy again after a cleanup?
Because the writers did not change. Integrations, workflows and old forms keep writing their own values into the same fields. Decide one source of truth per field and change the writers before you clean, or the cleanup fades within weeks.
Do HubSpot validation rules apply to workflows and imports?
They apply to imports and CRM edits, and to forms built in the updated form editor. According to HubSpot, they are not enforced in workflows, chatflows, meeting scheduling pages or legacy forms, and they do not reformat existing values.
How do I see which integration overwrote a HubSpot property?
Open the record, click Actions and select View property history, then look at the source of the latest change. Repeat on a few records before you blame one app.
This week, pick the few fields your routing and reports depend on and open the property history on a handful of records for each. If you find more than one writer on a field, write the one-line rule and name its owner before anyone touches the data.
Related reading
Alignify
On this page
Get the audit checklist
All 25 checks as a spreadsheet with auto-scoring.
Talk to Alignify
45 minutes, your portal on screen, no slides. We show what we would fix first.