WordPress All-in-One Migration Alternative: When a Plugin Is Not Enough
A migration plugin solves half the job: it copies files and the database. The other half is DNS, serialised data, orders placed during the switch and a rollback path. When the site takes money, that half is planned before the window, not discovered during it.
What a Plugin Does and Where It Stops
All-in-One WP Migration and its forks build an archive and unpack it on a new server. For a blog or a brochure site, that is enough. Then the limits appear:
- Upload size. Hosting caps the archive, so the site gets split into parts.
- Serialised data. The domain inside the database does not always change: some options keep the old address.
- DNS and timing. The plugin does not decide when to move the domain or how low the TTL should go.
- Downtime. Orders and forms sent during the transfer can be lost.
- Rollback. If the new server fails, going back should take minutes, not an evening.
The Alternative: Migration as Work, Not a Button
We run a migration in four stages, and a plugin stays one tool in the kit, not the whole process.
- Inventory. Servers, cron, queues, mail, certificates and the plugins that write absolute paths into the database.
- Rehearsal. The full copy runs on the target environment: checkout, forms, cron, search. Problems show up before the window.
- Cutover. TTL drops in advance, traffic moves in stages, the old environment stays warm.
- Verification. Logs, Search Console, order counts and the new cost model.
What to Check Before Any Transfer
- Archive size against the new hosting limits: disk, PHP, database.
- PHP and MySQL versions on both sides.
- Mail. The sending domain changes, and messages can land in spam.
- Licences bound to a hostname: plugins, themes, gateways.
- Cache and CDN. After the move they serve old pages until purged.
- Cron. Jobs left on the old server have to be moved, not abandoned.
When a Plugin Is Enough
For a site without orders, with one language and no integrations, a plugin does the job. The test is simple: if the move takes under an hour and nobody pays money during it, the risk is low.
For a store, a client portal or a multisite network, a plan with a rehearsal works better. The cost of a mistake there is higher than the work itself: lost orders, reindexing and refunds.
Timeline and Budget
A migration takes one to four weeks, with the cutover inside a one-hour window. Setup starts at $900, hourly work at $45. Ranges sit on the pricing page.
After the move the site continues on maintenance packages: updates, backups and a written response time. When the stack changes too, see cloud migration services.
Questions We Hear
Can I move the site with a free plugin? Yes, if the archive fits the upload limit and no orders are placed during the switch. For a store, add a rehearsal and a rollback.
How much does a migration cost? Setup starts at $900, hourly work at $45. The exact quote follows the inventory.
What happens to SEO after the move? URLs stay the same, the sitemap is resubmitted and redirects are checked. The first week is watched for crawl errors in Search Console.
How long is the downtime? Minutes, usually. The window is planned for an hour, and traffic moves in stages.
Can the old server stay online? For a week. That is the insurance against anything that appears later.
Tell us what you are moving and where. We reply with the plan, the window and the rollback path.
