HubSpot Record ID imports: update the intended records

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Separate updating from creating

HubSpot's import guide distinguishes Create and update, Create new only and Update existing only modes. Updating existing records requires a supported unique identifier. Record ID is available across record types and takes precedence over other included identifiers. The guide notes that a row without a Record ID can create a new record in a create-and-update import. Inspect both the selected mode and the actual identifier values before finishing.

Our recommendation is to treat a correction import as a controlled change set. A spreadsheet containing familiar customer names is not proof that the importer will update the intended records.

A fictional ten-record correction

Assume an operations team needs to correct the region on ten existing companies. Export the authorized target IDs and retain the current region beside the proposed region in a separate audit worksheet. Include only the actual columns intended for import in the upload file.

For this example, the expected result is ten specific company IDs with changed region values and no new companies. These numbers are hypothetical acceptance targets. A destination total that increases by one requires investigation even if most rows appear correct.

Validate the correction file

1. Confirm the object type and account from which the IDs came.
2. Check for blank IDs, repeated rows and identifiers altered by spreadsheet formatting.
3. Choose the mode that matches the update-only purpose where supported.
4. Map the identifier column explicitly and review the proposed property updates.
5. Run a small synthetic or otherwise authorized pilot.
6. Compare the final values on the exact target IDs, and inspect any rejected rows.

Do not invent an identifier

Our identity recommendation is to retain the CRM-provided ID as text and avoid reconstructing it from row position, a customer number or a displayed name. A source system's identifier can be valuable for reconciliation, but it is not automatically the HubSpot Record ID.

If an external ID is used through a supported unique-value property, document that contract separately. Do not label the column Record ID merely because it contains a number. Verify one known mapping before trusting thousands of rows.

Control what gets overwritten

For the region example, decide which source is authoritative and what an empty source cell means before uploading it. Inspect the current import options for property replacement behavior rather than assuming blanks erase values or preserve them. Keep unrelated properties out of a narrowly scoped correction unless their changes are intentional.

Where several operators or integrations update the same field, record when the source snapshot was taken. A correction based on yesterday's data can overwrite a more recent legitimate change if the process ignores that conflict.

Reconcile the business change

Accept the batch when all ten intended IDs have the approved values, rejected records are explained and no unintended records were created. Retain the before-and-after evidence in an authorized location. A reversal needs its own verified change set; do not assume repeating the old spreadsheet safely undoes every side effect.

This guide proposes a controlled update procedure. It does not perform a live import or establish that every identifier combination is safe in every account. Consult the current importer and official guide when selecting a supported identity mechanism.