Compression varies by data type
Text-heavy SQL dumps often compress well, while already-compressed binary content does not. The percentage used here is a planning assumption, not a guaranteed archive size.
← All tools
Migration Planning Tool
WordPress Database Migration Size Estimator
Estimate compressed transfer size and migration complexity from WordPress database size, table count and activity level.
Free to useNo account requiredRuns in your browser
Planning result
—
Enter your site details and calculate.
How to use this wordpress database migration size estimator
This free utility is designed for migration planning. It turns a few operational inputs into a structured result so you can identify what should be checked before a production change. It does not connect to your server, registrar, DNS provider or WordPress database, so it cannot replace a real technical audit.
Import time can dominate
Database import requires parsing SQL, writing rows and rebuilding indexes. A fast network does not guarantee a fast import on slow storage or a constrained database service.
Table count exposes plugin complexity
Many tables can indicate WooCommerce extensions, LMS platforms, memberships, analytics, action queues or abandoned plugin data. Inventory custom tables before migration.
High write activity changes the method
A busy database may need a final synchronization, brief write freeze or application-specific migration process. One full dump at the start can become stale before cutover.
Important limitations
Does this tool change anything on my website?
No. It runs locally in the browser and only evaluates the values you enter. It does not log in to WordPress, connect to DNS, move files or modify hosting.
Can I use the result as a production checklist?
Use it as a starting checklist. Add the site-specific dependencies discovered during the source audit, including custom plugins, server rules, cron jobs, email, APIs, payment gateways and any third-party services.
When is manual migration planning necessary?
Manual planning is appropriate when the site generates revenue, has active customer data, cannot tolerate downtime, uses custom server configuration, has a large database or depends on integrations outside WordPress.
Professional interpretation
How to use WordPress Database Migration Size Estimator in a real WordPress project
The useful part of a planning tool is not the number by itself. It is understanding which assumptions produced the result, which production conditions can change it, and what should be checked before you act. Use this tool as part of a wider migration or infrastructure review rather than as an automatic go/no-go decision.
Interpret the result as a planning signal
Migration calculators cannot see the source host, file count, database locks, active writes, plugin behavior or provider throttling. Use the output to decide what needs verification, not as a promise of exact downtime.
Separate copy time from cutover time
A WordPress site can take hours to copy while the production cutover lasts only minutes if staging and final synchronization are planned correctly. The safer workflow is to prepare the destination first and keep the final production change as small as practical.
Protect changing data
Orders, leads, memberships, bookings, comments and scheduled jobs can change after the first copy. Any tool used for migration planning should be interpreted together with the site’s live write activity and the method used for the final database state.
Practical questions
Can this tool predict exact downtime?
No. It estimates or organizes specific migration variables. Actual downtime depends on the migration method, live changes, hosting behavior and DNS strategy.
Should I test on staging first?
Yes whenever the project permits it. A private destination test exposes compatibility, PHP, database, cache and routing issues before production traffic moves.
What should be verified after launch?
Check key URLs, forms, login, checkout if applicable, redirects, SSL, email, cron jobs, cache/CDN behavior and server logs.