How to Undo a Bad Import in HubSpot

A bad HubSpot import can damage thousands of CRM records in minutes.

An incorrectly mapped spreadsheet column might replace contact owners, lifecycle stages, deal values, phone numbers, or custom properties. An import can also create duplicates, break associations, or accidentally add records that were never meant to enter the CRM.

The correct recovery method depends on what the import did:

  • Created new records
  • Updated existing records
  • Created incorrect associations
  • Overwrote property values
  • Triggered workflows or other automation

Can you undo a HubSpot import?

Sometimes.

HubSpot maintains a history of previous imports and allows you to review the records and errors associated with each import.

If an import created new records, you may be able to identify and delete those records. However, deleting an import does not reverse updates made to records that already existed.

For eligible accounts and objects, HubSpot’s CRM restore feature may allow recent import changes to be rolled back within 14 days.

Step 1: Stop further changes

Before trying to fix the data, prevent the problem from spreading.

  • Workflows using the affected properties.
  • Lead-routing automation.
  • Data-sync integrations.
  • Customer notifications.
  • Sales sequences.
  • Webhooks and custom applications.
  • Calculated processes based on corrupted values.

Restoring the original imported property may not automatically reverse these secondary actions.

Step 2: Identify the affected import

Open your HubSpot import history and locate the relevant import.

  • The import name.
  • The user who ran it.
  • The date and time.
  • The imported object types.
  • The number of created records.
  • The number of updated records.
  • The properties included.
  • The error file.
  • Any associations that were created.

Do not begin bulk-correcting records until you clearly understand the scope.

Step 3: Determine what type of damage occurred

The import created unwanted records

Use the import history or a list containing records created by the import to identify the new records. After confirming the selection, move unwanted records to the recycle bin rather than permanently deleting them.

The import overwrote existing property values

Deleting the import will not restore the old values.

  • HubSpot’s CRM restore feature.
  • Individual property history.
  • A previous export.
  • Another connected system.
  • An independent HubSpot backup.
  • A corrective import containing the original values.

The import created duplicates

Compare email addresses, company domain names, HubSpot record IDs, custom unique-value properties, creation dates, associated activities, ownership, and lifecycle information before merging or deleting records.

The import created incorrect associations

  1. Identify every association created by the import.
  2. Export the affected record IDs.
  3. Remove the incorrect relationships.
  4. Recreate the correct associations using a verified source file.
  5. Check whether workflow or reporting logic used the wrong associations.

The import triggered workflows

  • Sent emails.
  • Assigned record owners.
  • Created tasks.
  • Generated deals or tickets.
  • Added contacts to lists.
  • Sent webhooks.
  • Updated connected systems.

Step 4: Use HubSpot’s CRM restore feature

For supported HubSpot subscriptions, objects, and actions, CRM restore can roll eligible records back to an earlier point within the previous 14 days.

  1. Open Settings.
  2. Navigate to Data Management.
  3. Open Backup & Restore.
  4. Select the CRM restore option.
  5. Choose the affected object.
  6. Select Import as the change source.
  7. Select the specific import.
  8. Choose a restore date and time from before the import.
  9. Review the affected records.
  10. Confirm the restoration.

Before confirming a restore, understand whether valid changes were made to the same records after the bad import.

Step 5: Use property history for smaller incidents

Property history can help determine the previous value, new value, timestamp, and whether the source was an import, workflow, integration, or user.

Step 6: Restore from an earlier export

  1. Locate an export created before the bad import.
  2. Identify a stable unique identifier, preferably HubSpot record ID.
  3. Keep only the properties that need correction.
  4. Compare the old and current values.
  5. Exclude records that received legitimate updates afterwards.
  6. Run a small test import.
  7. Validate the result.
  8. Import the remaining records.

A corrective import should be treated as another potentially dangerous bulk operation. Do not upload the original file blindly.

Step 7: Verify the recovery

  • Record counts
  • Important properties
  • Associations
  • Automation history
  • Reporting
  • External systems

How to prevent bad HubSpot imports

  • Export the affected objects first.
  • Use HubSpot record IDs.
  • Test with a small file.
  • Review mappings carefully.
  • Disable risky workflows.
  • Give imports clear names.
  • Keep the original source file.
  • Maintain automated backups.

Recover bad imports with Restor

Restor automatically creates historical HubSpot backups, giving your team a clearer route back when an import overwrites or corrupts CRM data.

Restor adds independently maintained history for supported HubSpot data, so recovery does not rely solely on a native rollback window or an old folder of CSV files.

Before your next large import, make sure there is something reliable to restore.

Official sources

HubSpot: back up CRM dataHubSpot: restore deleted recordsHubSpot: restore CRM changes