To roll back a failed CMS migration without losing content, restore the complete pre-migration backup of files, database, and media to the live server. Then export any posts, orders, or edits made on the failed new site and add them back to the restored site. A CMS migration moves pages, media, users, and settings from one content management system to another, such as WordPress to Drupal. A rollback returns visitors to the stable old system while you protect anything created during the attempt.
Official resources:
- Run and roll back Drupal migrations with Drush commands — Verify the official rollback command to undo imported content after a failed migration.
- Back up and restore a WordPress database safely — Follow the official backup steps to preserve posts and settings before migrating.
Table of Contents
- When should you roll back instead of fixing forward?
- What do you need before you restore?
- How do you restore without losing content?
- How do you save content created during the failed migration?
- How do you check the restored site?
When should you roll back instead of fixing forward?
Roll back when core functions stay broken after basic fixes. Those functions include login, checkout, forms, publishing, and page display.
Fix forward when only styling, redirects, or minor plugins fail and content loads correctly. Continuing a broken migration risks lost orders, lost leads, and search damage.
- Roll back if the new database misses pages, users, or media.
- Roll back if editors cannot publish reliably.
- Roll back if checkout, registration, or payments fail.
- Stay the course if only themes, menus, or redirects need work.
What do you need before you restore?
You need a full pre-migration backup made immediately before the move. It should include the site database, site files, themes, plugins or modules, configuration, and the uploads folder.
Keep the login credentials, DNS records, and redirect map from the old site. Store the backup in a separate location from the live server so a failed migration cannot overwrite it.
How do you restore without losing content?
Put the old site in maintenance mode to stop new changes during the restore. Restore the database first, then files and media, then clear caches and test logins.
Point the domain back to the restored installation and check file permissions, connection settings, and scheduled tasks. Keep the failed new site on a staging address so you can review its content later.
- Freeze changes on both sites.
- Restore database, files, and media in order.
- Reconnect domain, SSL, and email sending.
- Clear cache and test admin, editing, and publishing.
How do you save content created during the failed migration?
List everything added after cutoff, including posts, pages, products, comments, form entries, and orders. Export those items from the failed site using built-in export tools or database queries for the affected tables.
Re-enter the items on the restored site by hand or by import, starting with customer records and transactions. Check authors, dates, images, links, and categories because IDs often change between systems.
How do you check the restored site?
Compare the restored site against your pre-migration content inventory. Open key templates, test navigation, search, forms, and mobile layouts, and confirm media loads.
Test redirects from old URLs, submit a test order or lead form, and review SEO basics such as titles, meta descriptions, and sitemap access. Ask editors to publish a test post and confirm backups run again before you announce recovery.
