Back up your full site files and database, plus media, design assets, extensions, settings, redirects, and user accounts before starting a CMS migration. A CMS migration means moving all site content and functions from one publishing platform to another, such as from WordPress to Drupal. A complete backup lets you restore the old site if the move stalls or breaks. Store at least one full copy off the server and check that it opens before you touch the live site.
Official resources:
- Follow the official WordPress backup checklist for files and database — Verify which database tables and site files to copy and test before migrating.
- Review NIST contingency planning guide for system backup requirements — Check federal guidance on backup scope, frequency, and recovery planning for a rollback plan.
Table of Contents
- What makes a complete file and database backup?
- Which content needs its own copy?
- How do you save design and functions?
- What access and routing details should you record?
What makes a complete file and database backup?
Save a full copy of the site directory, including core files, uploads, themes, and custom code. Export the database separately as a complete dump, not only a partial export from inside the admin screen.
Keep the two parts together and label them with the site name and backup point. Store one copy off the server, such as on a separate drive or storage account, so server failure does not take both versions.
- Copy all site files, including hidden configuration files
- Export the full database with its character settings intact
- Save the platform and PHP version numbers with the backup
- Test the backup by opening the archive and sample records
Which content needs its own copy?
Export pages, posts, categories, tags, menus, and custom fields in their native format. Many moves lose formatting, embeds, or relationships, so a separate content export makes gaps easier to spot and fix.
Back up the full media library with original filenames and folder structure. Include images, video, audio, PDFs, and captions or alternative text, because bulk import tools often skip or rename files.
How do you save design and functions?
Save your active theme or templates, style files, logos, fonts, and any custom CSS or JavaScript. Note layout choices for headers, footers, sidebars, and page templates so you can rebuild them on the new system.
List every plugin, module, extension, form, and integration, with its version and settings. Pay special attention to contact forms, search tools, membership controls, comments, backups, security tools, and connections to email, payment, or marketing services.
What access and routing details should you record?
Record administrator logins, hosting and domain controls, database credentials, and API keys in a secure location. Also record user accounts and permission levels, so members, customers, and editors keep the right access after the move.
Save URL redirects, metadata, sitemaps, and tracking codes used for traffic reports or ads. Keep the old backup untouched until the new site runs well for several weeks.
