Roll back
Roll back deletes what the migration created, from its ledger. It never touches records that already existed, and it does not restore values it overwrote.
Last updated: 28 October 2026
"Roll back" is offered on a finished or failed migration. On a running or paused one the control is "Cancel", which stops the run and rolls it back. A sample can be rolled back too. After a rollback the run reads "Rolled back" and lists what was left.
Shuttio keeps a ledger of every record, note, task, meeting, file and list entry it creates. A rollback deletes those, in reverse order. A record that already existed has no ledger row, so it is never deleted.
What a rollback cannot do
- It does not restore values it overwrote on a record it matched. The Fields step warns you before the run.
- Into Attio, it renames each list it created to "<name> (rolled back, safe to delete)", because Attio has no delete-list call. It archives the fields and options it created, and deletes a custom object it created only when the object is empty.
- Into Clarify, it removes records, notes, tasks, files and custom objects it created. Clarify's API cannot delete a field, so fields it added to your existing objects, and the list fields, stay. The rollback names them.
- Into Odoo through an API key or the app, it removes what it created, and leaves a stage, team, tag or partner that your own records now use, naming each one.
- Into Odoo through an import package, Shuttio wrote nothing to your Odoo and cannot remove it. In Odoo, filter by the tag "Migrated <date>", select all and delete.
A rollback needs a live connection. If the 14-day token purge already ran, reconnect first. Rollback is also the condition for a refund: see refunds.
Not answered here? Email help@shuttio.com.