“Clean up HubSpot” can describe anything from correcting a short field list to redesigning the way customer information moves through your business. If those meanings stay unresolved, you cannot judge whether a proposal covers the work you need.
We recommend buying a defined set of changes and evidence of their acceptance. The statement of work should make the boundaries visible before anyone edits, merges or removes records.
TLDR: A HubSpot CRM cleanup scope should name the baseline, records and properties in scope, decision rules, exclusions, approval steps, validation evidence and handover. Ask the agency to separate recommendations from authorized changes. Require a way to reconcile the result against the agreed starting point.
Define your HubSpot CRM cleanup scope and baseline
Describe the operational consequence you want to address. Missing account ownership, inconsistent lifecycle stages and duplicate-looking records are different data quality problems. They may require different decisions, permissions and acceptance tests.
Ask the agency to document the current condition before proposing a bulk correction. For each issue, capture the selection criteria, the source of the evidence and the date of the baseline. A count without its filter definition is difficult to reproduce later.
We suggest tracking completeness, accuracy, consistency and uniqueness separately. Count required fields with values, verify a sample against the approved source, test agreed formats, and review duplicate candidates. Require the same population and definitions before and after cleanup. A populated field can still be wrong.
Use the HubSpot portal audit checklist to organize the findings. The cleanup scope should then select the findings the engagement will address, with the rest left explicitly outside the current commitment.
Separate CRM data cleanup from data enrichment
Ask each provider to separate correction, enrichment and process repair. These are useful buying categories, not promises that a particular HubSpot subscription includes every tool the work might require.
| Work category | What you should ask the agency to deliver | Boundary to resolve before approval |
|---|---|---|
| CRM data cleanup | Approved rules for correcting existing values, duplicate candidates and missing fields. | Which records can change, what counts as an exception and what evidence proves the correction? |
| Data enrichment | A named source and a proposed method for adding information you do not already hold. | Which source is authorized, how conflicts are handled and whether usage costs are included? |
| Process repair | A defined change to a form, integration, workflow or reporting dependency. | Which business process is included and who approves its behavior after the change? |
For example, correcting inconsistent job titles is different from purchasing new job-title data. Neither automatically includes redesigning your sales process. Keeping those commitments separate makes the proposal easier to accept and the invoice easier to understand.
Put duplicate records and property cleanup in scope
HubSpot properties store information on records, and HubSpot provides default properties as well as support for custom properties. HubSpot's property documentation is the starting reference for checking the fields involved.
For each included property, request its object, label, internal identifier, business definition and authoritative source. Do not accept a request to “standardize all fields” without a list and a decision rule.
The scope should distinguish what the agency can decide from what your team must decide. An agency can propose a normalization rule. The business owner should approve what a category means, which source takes precedence and what happens when information conflicts.
- Included records. Define the population using reproducible criteria, including how newly arriving records will be handled during the work.
- Included changes. State which values, relationships or configurations may be corrected and under which rules.
- Exceptions. Identify ambiguous cases that require review instead of an automatic decision.
- Exclusions. Name work that is not included, such as new integrations, historical reconstruction or changes to customer communications.
For duplicate contacts and companies, require matching evidence and a manual review path for uncertain cases. Similar names do not establish that two records describe the same person or business. Ask which record would be retained, which associations must survive and what happens to conflicting values. The scope should define the decision; it does not need to repeat a merge procedure.
For property cleanup, ask for a register of unused properties, conflicting definitions and proposed naming conventions. Do not equate property sprawl with permission to delete fields. Have the agency identify known reports, forms and integrations that depend on each proposed change.
This list should be short enough to operate and detailed enough to resolve a disagreement.
Require approval before changing CRM data
Do not treat access to a portal as permission to perform every possible action. Ask the agency to identify changes that need separate approval, especially bulk updates, merges, deletions, workflow changes or modifications to data shared with another system.
The statement of work should specify how the proposed change set is reviewed, who authorizes it and what happens if the actual records differ from the sample. It should also require an assessment of recovery options before execution.
Avoid a generic promise that every cleanup action is reversible. Have the team explain what can be restored, what cannot, what evidence is preserved and what conditions would stop the work.
Write acceptance criteria that you can inspect
Hypothetical scope example: Your team wants approved customer-segment values applied to a defined set of company records. The agency proposes a mapping from existing values to the approved list. Values with no agreed interpretation remain in an exception queue.
Acceptance could require the final mapping, the exact included record identifiers, before-and-after evidence, a reconciliation of changed and unchanged records, and a report of unresolved exceptions. A reviewer then checks representative records and any cases selected as higher risk.
The scope should also say whether connected forms, reports or integrations that use the property are included. If those dependencies are excluded, the handover should identify them so your team does not mistake a field correction for a complete process repair.
HubSpot's import tool can create records, update existing records and establish associations, using unique identifiers to match records where required. HubSpot's import overview explains why identifier handling belongs in a cleanup plan that uses imports.
Ask how the proposed method will avoid changing the wrong record. A successful upload is an execution result. Your acceptance criteria should still describe the business result.
State the workflow and reporting boundary
A field correction can be a small assignment. Repairing every process that touches that field can be a different engagement. Ask whether the agency will inspect workflow triggers, form submissions and integrations that can write the same value. Require an explicit decision about which dependencies it will test or change.
If your sales team uses lifecycle stages or pipeline stages differently from your marketing teams, have the business owners agree the definitions first. A cleanup agency should not settle that disagreement by choosing the most common existing value. Cleaner reporting should mean that reports follow an accepted definition, not merely that the totals look better.
Do not create workflows solely because a proposal promises automation. Request a reason for each proposed rule, the population it affects and a test for an excluded case. Complex workflows and broken workflows may need separate investigation. Have the provider identify that work before it becomes an unplanned dependency.
Ask for a useful CRM cleanup handover
The final deliverable should help your team maintain the decisions after the engagement. A presentation of problems found is not enough if the work also changed the system.
Request the approved rules, change log, exception register, validation evidence and a concise operating guide. Identify which role owns each rule and who can approve a future change. Where recurring checks are included, specify their scope and how failures will reach a person who can act.
If training is part of the engagement, define the audience and the tasks they should be able to perform. You can discuss that work through HubSpot onboarding and training, rather than assuming a configuration handover includes team adoption.
Agree how to keep CRM data clean
Ask who will regularly review the data issues most likely to return. The maintenance commitment should name the check, its frequency, an owner and the response when it fails. A general promise of ongoing support is not a measurable maintenance scope.
Include a decision for new contacts arriving during the cleanup. Otherwise, the baseline and final contact count may describe different populations. For inactive contacts or outdated contacts, specify the activity date and other evidence used to select candidates. Low activity alone should not be treated as permission to delete them or change communication permissions.
If hard bounces, stale deals or missing fields are in scope, require a separate rule and exception queue for each. Do not allow one bulk action to stand in for unrelated decisions. These boundaries turn reactive cleanup into an operating routine without claiming that bad data will never return.
Compare proposals on the same data quality boundaries
When two proposals look different, ask both providers to answer the same questions: Which findings are covered? Which changes are authorized? Which decisions remain with your team? What evidence will you receive? What would create additional scope?
We recommend resolving those questions before comparing the final commercial terms. A smaller engagement with explicit acceptance can be easier to evaluate than an open-ended promise to make the CRM healthy.
Review HubSpot operations and CRM architecture if you need to turn the findings into a defined engagement. Bring the HubSpot Portal Audit Scorecard and ask for a scope you can accept item by item.
Product documentation checked August 28, 2026. This article offers scoping guidance, not a statement of Selworthy contract terms or legal advice.
