How-to
Roll back a load
A rollback puts the destination back the way the load found it: every row it wrote is removed (except a redirect on Settings > Redirects that someone changed after the load wrote it, which is left in place and named in the result), every row it changed is put back with its dates, and people it created are removed. Existing people's profiles go back to what they were. Rows get their external ids back, tables and columns their settings, and pages every setting the load changed, including a page the load wrote as its file for its response headers, cache settings or a 307 redirect.
- Open the migration's Verify step and click Roll back this load.
- Type the new site's address, which the dialog shows (for example
acme.prod01-insites.io), to confirm. Typing it makes sure you are rolling back the site you mean. - The ROLLBACK check then confirms nothing the load wrote is still live, and every changed row is identical to how it was.
- A row the rollback removes disappears from the site at once, and Insites keeps it out of sight for 30 days before it removes it for good. Its id is not given to another row, so a later load gives those rows new ids. Their content and dates are unchanged.
- A column the load added to a table that was already there is left in place, empty.
The rollback deletes rows in the background and waits until every one is gone, so a large delete does not fail with a 504 timeout. A big rollback takes longer, and it shows its progress.
A table the load created is removed once its rows are gone. A table that holds rows sent after the load, such as a visitor's form submission, is kept, and the rollback says so.
The way each thing was is saved before the load changes it, so a load that stopped part way can still be rolled back. Rows the rollback removes are gone before it reports, so the ROLLBACK check reads the destination as it is.
A rollback is possible until you close the migration, and for 30 days after the load at most. The day before those 30 days end, whoever started the migration gets an email saying so. After that the run's record of what the load wrote is removed, and the run says it can no longer be rolled back. The copies of the old site go sooner, after 7 days with no activity on the run, but the record of the load stays for the rollback. It needs the destination's key, which the tool keeps until you close the migration: if the tool no longer holds it, the rollback says so and asks for a new one. A rollback waits while the run, or a sync that shares its keys, is still working, and says which run to wait for.