Free WordPress Migration Tool

Migration Monkey includes one standard self-service WordPress migration every 30 days for each account. A qualifying move can contain up to 3 GB of website files and 500 MB of WordPress database data. It can keep the same domain, move to a new domain, or restore to a temporary domain for testing.

No payment card is required for the free route. Use the public migration estimator before signup, then let the source agent measure the actual install before creating the job.

Exactly What The Free Migration Includes

• One qualifying self-service WordPress migration every rolling 30 days.
• Up to 3 GB of files in the detected WordPress install.
• Up to 500 MB of database data in tables using the detected WordPress prefix.
• Same-domain, new-domain, and temporary-domain destination routes.
• Serialized-safe replacement of the old WordPress URL when a domain changes.
• Direct source-to-destination file and database transfer through signed endpoint agents.
• Checksums, resume checks, transfer progress, rewrite counts, warnings, and completion logs.

What Qualifies As A Standard Route

The source and destination must be reachable by the signed migration agents, the selected source folder must actually contain WordPress, and the destination must provide a writable install path plus working database credentials. A normal cPanel, DirectAdmin, Plesk, VPS, or managed host can qualify when it permits those endpoint connections.

Help4 enterprise proxy routes also qualify when their signed origin path is available. A Cloudflare or Sucuri site may still be easy to migrate, but it does not use the free standard-route estimate until the agent path can bypass or satisfy the third-party challenge without operator intervention.

Domain Changes Are Included

A free move is not limited to copying a site back to the same URL. For a new or temporary domain, Migration Monkey can replace the configured WordPress URL in normal text, PHP-serialized values, protocol-relative URLs, escaped JSON, and URL-encoded values while the destination rows are imported. The source database is not rewritten.

Use the WordPress domain search-and-replace guide to understand what changes, why a plain SQL replacement can corrupt serialized data, and what to verify after the move.

What Does Not Use The Free Standard Route

• More than 3 GB of files or more than 500 MB of database data.
• Custom PHP, Node.js, Laravel, Magento, or unknown applications labeled as WordPress.
• WordPress.com export-only plans that expose XML and media instead of server files and database access.
• Locked-down hosts that block the agent, database export, file reads, or destination writes.
• Operator-assisted repair, malware cleanup, database recovery, custom code changes, or live in-place overwrites.
• Cloudflare or Sucuri routes that require a managed WAF exception or manual origin work.

These jobs are not rejected automatically. The estimator shows the applicable credits or marks the job for an assisted runbook. Most standard non-custom website migrations at 10 GB or less are designed to fit within the 500-credit Website Owner pack.

How To Migrate The Site For Free

1. Use the public estimator with the best file and database measurements available.
2. Create an account, accept the terms, and confirm that you own the data or have written permission to move it.
3. Choose WordPress, the source access route, and the destination method.
4. Download the generated source agent, destination agent, and .user.ini runtime helper.
5. Install the destination agent first, then run Analyze source from the source agent.
6. Confirm detected WordPress version, file bytes, database size, table prefix, domain route, and the zero-credit estimate.
7. Start the direct transfer, review checksums and rewrite counts, then run the post-migration checklist before changing DNS.

Why The Account Is Still Required

The estimate is public, but running the migration requires an account because Migration Monkey must record the data-ownership authorization, sign the endpoint agents, associate progress and warnings with the correct job, enforce the 30-day free interval, and protect the migration logs. Creating the account does not require a card, and server or mailbox passwords are entered per migration rather than stored in a reusable endpoint profile.

How The Free Limit Is Enforced

The source analyzer measures the selected install instead of trusting a lower application choice or a typed guess. The control plane checks the detected application, measured file size, measured database size, route, source constraint, and the account's last free migration before it creates a zero-credit job. If the allowance has already been used, the same job receives its normal credit estimate until the next 30-day window opens.

How We Test The WordPress Route

The current integration harness verifies source and destination agents against PHP and MariaDB, including files, chunks, checksums, resume behavior, WordPress tables, serialized values, JSON, URL-encoded values, binary columns, generated columns, destination credentials, and fail-closed cases. Read the WordPress migration test methodology and current result before using the tool for a high-risk production site.

Continue With The Migration

Use the screenshot walkthrough for the workspace and agents, the destination WordPress preparation guide before transfer, and the post-migration checklist before DNS cutover.