WordPress Migration Inventory: A Practical Checklist
Published:
Published by: Hedou Bibi
WordPress migration inventory: review URLs, dependencies, backups and acceptance checks.

Executing a WordPress site move without a structured plan often leads to broken links and data loss. A comprehensive WordPress migration inventory serves as the blueprint for the entire process. It shifts the focus from technical execution to logical completeness. Before copying files or changing hosts, it is essential to define what is actually being moved. This guide outlines a practical framework for building that inventory.
Map URLs and Core Content
The first step is creating a complete URL map. Do not rely solely on the admin page list. Include dynamic URLs, taxonomies, tags, and media files. Mark pages that serve as business conversion points, such as inquiry forms or product pages. For multilingual sites, verify that source and translated pages are correctly paired. Note that metadata synchronization in plugins like Polylang does not guarantee the business body text is correctly translated; each version must be audited individually. The table below is a self-created example for tracking; adjust paths to your site structure:
Scroll horizontally or use the arrow keys to view the full table.
| URL Type | Example | Attribute | Priority |
|---|---|---|---|
| Core Business | /product-x/ | Contains form | High |
| Static Info | /about/ | No dynamic features | Medium |
| Dynamic List | /category/cars/ | Plugin generated | High |
| Media | /wp-content/uploads/ | Images/Docs | High |
Audit Functions and External Dependencies
List all active themes and plugins, including their version numbers. Pay special attention to integrations with external services such as payment gateways, CRM systems, or email marketing tools. Confirm that these dependencies are compatible with the new environment and that licenses are valid. If a plugin requires specific PHP versions or server modules, note these environment requirements in your inventory. Always back up both files and the database before proceeding.
Verify Data State and Changes
Before execution, export a consistent backup with minimal business impact. Record the backup time and verify recoverability. Document incremental writes and the handler for the switching window. Compare the database structure between the source and target sites to ensure consistency. For unstructured data like uploads, calculate the total file count and size to serve as a validation benchmark after the move.
Define Switching and Acceptance Criteria
Acceptance should be based on pre-defined results, not merely pages loading. Establish clear checks:
- Core business pages respond as expected (not strictly 200 for all dynamic pages).
- Forms submit successfully to the target system.
- Images and attachments load without missing resource errors.
- External plugin functions (e.g., payment, login) work correctly.
Completing these steps provides a deliverable migration baseline. For complex dependency relationships or acceptance criteria, readers may submit their inventory to Hedou Bibi for discussion. The success of the migration depends on the granularity of the initial inventory and the rigor of the final verification, rather than the speed of the switching action.
