A spreadsheet has three empty cells, but the team intends three different actions. One value is unknown, one should remain unchanged, and one is obsolete and should be removed from the CRM. If the import file uses a blank for all three, it has discarded the decision that the operator needs to execute.
Before delegating CRM cleanup, define what an empty source cell means. This is especially important when a manager expects an import to clear old data. A successful file upload does not establish that the receiving system interpreted blanks as deletion instructions. The task needs an explicit before-and-after target for each kind of change.
Establish the product's blank-cell behavior
HubSpot documents that its import tool ignores blank spreadsheet cells. If a record already has a property value, a blank import cell does not clear it. The documentation points to supported editing methods for clearing values in bulk. HubSpot import-file guidance
That behavior means the assistant should not test deletion by repeatedly uploading the same empty column. It also means a file can be accepted while the supposedly removed values remain. Treat the documented behavior as a design constraint and prepare distinct work for changes that need an explicit clear operation.
Classify the intended action before formatting
For every field under review, distinguish keep, set, clear, and investigate. Keep means the existing value should remain. Set means an approved replacement is available. Clear means the owner has decided the current value should be removed. Investigate means the available evidence does not yet support a change.
These actions belong in a preparation sheet or controlled change record, not necessarily in the import payload itself. The final payload should contain only the columns and values required by the supported operation. Sending an internal action column into an unrelated CRM property would create a new data-quality problem.
A blank source value often belongs in investigate rather than clear. If an enrichment provider did not return a job title, that does not prove the existing title is wrong. The absence could reflect incomplete coverage, a temporary source problem, or a mismatch in the lookup. Deleting the CRM value would turn an evidence gap into a destructive decision.
Write a field-specific rule
Different properties require different treatment. An expired temporary routing code may be appropriate to clear after an owner confirms the transition. A historical acquisition source may need preservation even when a new campaign is active. A phone field may need correction rather than removal if a verified replacement exists.
The data owner should define the rule for each property in scope. Include the source of authority, the conditions for a change, and any exceptions. Avoid a global instruction to clear everything that is blank in the new export. That instruction assumes the export is a complete and authoritative representation of every relevant field.
For a hypothetical cleanup of 200 contacts, the preparation sheet might contain 140 keeps, 35 replacements, 10 approved clears, and 15 unresolved records. Those counts are more informative than describing all 200 as updated. They also give the reviewer a way to check whether the execution matched the approved scope.
Preserve the state needed for recovery
Before changing values, retain an authorized record of the affected identifiers and existing values. Keep the capture narrow: the fields being changed and the information needed to identify the records. There is usually no reason to copy every property from every contact just to correct one routing field.
Record the observation time. Another user or integration may update the same field between preparation and execution. If the current value no longer matches the approved before-state, stop that row for review rather than overwriting a newer change. A cleanup process should not assume it is the only writer in the CRM.
The recovery note should explain how an incorrect change would be reversed using supported controls. Do not promise that an import rollback restores every property or downstream effect unless that behavior has been verified for the actual operation. A recoverable value change and a triggered workflow are different concerns.
Test representative actions separately
Use a small approved set that includes a keep, a replacement, and a clear. Verify the result in the CRM after the action, not only in an import summary. For the clear case, confirm that the property is actually empty and that any dependent process behaves as expected.
The person who executes the change needs the appropriate permissions, but broad access should not be the default fix for a failed test. Determine which supported action is required and who is authorized to perform it. A reporting assistant can prepare the evidence while a CRM owner performs a consequential edit.
Check fields used in routing, segments, or workflows with particular care. Removing a value may change which records qualify for an operational process. The owner should review that effect before the batch, especially if the field influences outreach or assignment. The spreadsheet alone does not reveal every dependency.
Reconcile by action and record
After execution, compare the intended after-state with the actual state for each record in scope. Count successful keeps, replacements, clears, and unresolved exceptions separately. A total processed count cannot show whether the desired deletion happened or whether an unrelated value changed.
If five approved clears remain populated, report five unresolved clears. Do not mark the job complete because the other changes succeeded. Likewise, a value that disappears unexpectedly should be investigated even if the overall number of empty cells matches the target. Correct totals can conceal changes to the wrong records.
Keep failed rows in a separate recovery queue with the observed result and next action. The queue should be actionable: identify whether the owner must clarify intent, the operator must correct a mapping, or a supported editing method is needed. Repeating the whole batch is rarely the best first response to a small, well-defined exception set.
Give the next operator the meaning, not just the file
A CRM upkeep assistant can maintain the action sheet and reconcile the result. The related CRM data-hygiene research addresses recurring ownership; this procedure handles the narrower ambiguity of empty values during a cleanup.
The handoff is complete when the owner can see what remained, what changed, what was intentionally cleared, and what still needs a decision. That clarity prevents the next assistant from interpreting the same blank cells differently and repeating a cleanup that never expressed the intended action in the first place.
Sources
- HubSpot Knowledge Base, Format import files, checked October 2, 2026.
