Skip to content
Get a quote

Can a CRM migration be rerun or rolled back if something goes wrong?

Short answer

Partly. Most native importers can delete the records an import created, but they can't put back fields an import overwrote. HubSpot, for example, says changes to existing records can't be reversed by deleting. Plan for this: take a snapshot of the destination first, tag every record with its import batch, and test on a sample before the full run.

By

Rerun and rollback are different problems

A rerun loads the same source again after you fix a mapping. It works only if every destination record stores its source ID, so the second pass can update in place instead of creating duplicates. A rollback returns the destination to how it was before the run. That covers more than deleting new records: values on records that already existed have to be restored too. Native importers handle the first half, deleting what they created, and not the second.

What native tools do / where they stop

PlatformWhat you can undo nativelyWhere it stops
HubSpot importFilter the records an import touched and bulk-delete themHubSpot says that if an import updated existing records, “you will not be able to reverse the changes by deleting”
Salesforce Data Loader / Import WizardDelete inserted records by ID; the Recycle Bin keeps them for 15 days (30 if Support extends it)Records you updated aren’t versioned. You need your own pre-load export
Zoho CRM Migration WizardAn Undo option in Import HistoryZoho’s API-based migrations, such as the one from HubSpot, can be undone or rerun only a limited number of times

The common thread: no native tool snapshots the values it overwrites. Anyone migrating into a CRM that already holds data, such as a merge or a second wave, needs that snapshot.

How to make a migration reversible

  1. Export the destination before the run, including every field the migration could touch.
  2. Write the source ID into a custom field on every record, so a rerun can update in place.
  3. Tag each batch with a run ID, so you can find and delete exactly that batch.
  4. Run a sample of a few hundred records that covers every object and association, and compare it field by field.
  5. Freeze automations in the destination during the load, so workflows don’t send emails or change fields you’d then have to undo.
  6. Keep the source system read-only, not deleted, until counts and spot checks pass.

Where FlitStack AI fits

Every FlitStack AI migration runs against a sample first, uses hash-based validation, and has one-click rollback to the pre-migration state. Delta sync covers changes made during cutover. See the CRM migration checklist or scope a migration.

Questions, answered

A few useful answers.

Is deleting the imported records the same as a rollback?

Only for records the import created. If the import updated records that already existed, deleting won't restore their old values. For that you need a snapshot taken before the run.

Can we rerun a migration after fixing the mapping?

Yes, if every record carries its source ID. The rerun can then update in place instead of creating duplicates. Without a source ID, a rerun will create duplicates.

How long do deleted Salesforce records stay recoverable?

Salesforce keeps deleted records in the Recycle Bin for 15 days. Salesforce Support can extend that to 30 days. After that window, the Recycle Bin can't restore them.

A closer look

Tell us what you’re moving.

Share your source, destination and rough record counts. We scope the migration and the process work with you and send you a quote.

Get a quote