How to Move a WordPress Site to a New Host (Free Reprint Tool)

To move a WordPress site to a new host, you copy two things, the site’s files and its database, onto the new server. Then you test the copy before you point your domain at it. On November 13, 2026, WordPress.org released a free official tool for that copy step, called Reprint. Below we cover what Reprint does, who it’s built for, the other ways to move a WordPress site, and what tends to break after a move. Some of that we learned moving our own site this month.

Rather not move it yourself?

We move WordPress sites onto our own servers, test email, forms and SSL on the copy, then switch the domain over. Hosting starts at $15 a month with security updates and weekly backups.

See our hostingCall (919) 444-2005

How do you move a WordPress site to a new host?

Copy the site’s files and database to the new host, update wp-config.php with the new database details, test the copy on a preview address, then point your domain’s DNS at the new server.

Google’s guide to changing your hosting describes the same four stages for any website: prepare and test the new hosting, change the DNS settings to start the move, monitor traffic, and shut down the old hosting once everything comes from the new one. WordPress’s own Migrating WordPress guide adds the WordPress part: if your domain and URLs stay the same, you can move by copying your files and database, and you only edit wp-config.php if the database name or user changes.

There are four common ways to do the copy:

  • Ask the new host to do it. Many hosts move sites for new customers, so ask before you sign up.
  • Use a migration plugin that packs the site into one file you import on the new host.
  • Use Reprint, WordPress.org’s new tool, which copies the site piece by piece from the command line.
  • Do it by hand: download the files over SFTP, export the database, upload both, and edit wp-config.php.

Whichever you pick, most problems show up after the copy, in email, DNS, SSL, caching and the outside services your site connects to.

What is WordPress Reprint?

Reprint is a free, open-source tool from WordPress.org that copies a WordPress site’s files and database to another server or computer. It has a plugin for the old site and a command-line client.

WordPress.org announced Reprint on November 13, 2026 as part of its Data Liberation work. You install the Reprint plugin on the site you’re moving, then run the client on the computer or server that should receive the copy. According to the announcement, Reprint:

  • sends your files and database straight to the destination, one piece at a time, without an outside service in the middle;
  • doesn’t need your old host to have room for one big backup file of the whole site;
  • picks up from the last saved point if the connection drops;
  • can rewrite links that point to the old address when you give it a new one, including links stored in serialized data and custom fields;
  • copies only what changed when you run it again.
Move a WordPress site to a new host with Reprint, the free WordPress.org plugin
The Reprint plugin on WordPress.org. You install it on the site you’re moving.

It’s early software. The plugin was at version 0.11.8 when we wrote this, so expect changes.

Who is Reprint for, and who should skip it?

Reprint suits developers and hosts who are comfortable in a terminal. If you’ve never run a command-line PHP command or set up a web server, a host-run move or a migration plugin is easier.

Reprint’s requirements page says you need a terminal, command-line PHP 7.4 or newer, enough disk space and administrator access to the site you’re copying. The plugin side needs WordPress 4.7 or newer and a working HTTPS address. You don’t need SSH access to the old host, which is handy when your current host makes that hard.

The move-to-another-host guide also assumes you can configure the new server’s web server and create an empty database there. On most shared hosting plans, that’s a support ticket, not something you do yourself.

If your site sits behind Cloudflare, like many of the sites we look after, check your security rules first. Reprint’s troubleshooting guide says the client can’t get past a Cloudflare browser challenge, and a Wordfence request limit or a proxy that strips custom headers can stop it too. You may need to relax those rules for the copy. If you’re not sure your site is behind Cloudflare, our post on whether Cloudflare is safe explains what it does.

How do you move a WordPress site with Reprint?

Install the Reprint plugin on the old site, authorize the client on the new server, run one pull command to copy files and database, test the copy, then switch your domain over.

Here’s the short version of WordPress.org’s step-by-step guide to moving your site and its guide to making your first copy:

  1. Prepare the new server. Download the client (one file, reprint.phar), create an empty MySQL database with its own user, and pick folders for the copy.
  2. Install the plugin on the old site. In WordPress, go to Plugins, Add New Plugin, search for Reprint, install and activate it, then open Tools, Reprint Server.
  3. Authorize the client. Run php reprint.phar keygen with your site’s address on the new server, then paste the Migration Token it prints into the Reprint Server screen.
  4. Copy the site. Run php reprint.phar pull with your new database details. If the transfer is interrupted, run the same command again to continue.
  5. Set up and test. Point the new web server at the copy, fill in wp-config.php for the new database, and test pages, images, logins, forms and plugins on a preview address.
  6. Switch traffic. Pause changes on the old site, run a final copy, then change your domain’s DNS through your normal process. Reprint doesn’t do this step for you.

Treat the second copy carefully. Reprint’s page on what it doesn’t do is clear that it never merges: running the copy again replaces the new site’s database with the old site’s. Anything you changed on the new copy in between is overwritten.

What are the other ways to move a WordPress site?

Have your new host move it, use a migration plugin that exports one file, or move the files and database by hand. For most small business sites, the first two are easiest.

Host migration. If you’re moving to a managed WordPress host, ask whether they’ll move the site for you. It saves you the database work, and the host knows its own server setup. Ask what they test afterwards, though. A copied site that loads its home page can still have broken forms or email.

Migration plugins. WordPress migration plugins such as All-in-One WP Migration and Duplicator export your site into a file you import on the new host. We use All-in-One WP Migration for full-site backups ourselves. The catch is size: big sites can hit upload limits, which is one of the problems Reprint was built to avoid.

By hand. WordPress’s Migrating WordPress guide covers it: copy the files, copy the database, edit wp-config.php if the database details change, and if you had permalinks set up, reconfigure them once the site goes live. It’s the most control and the most chances to miss something.

What breaks after you move a WordPress site?

Outgoing email, DNS, SSL certificates, caching, scheduled tasks and premium plugin licenses are the usual problems. A copy that loads its home page doesn’t prove forms or email still work.

Reprint’s own documentation lists several of these. It doesn’t disconnect live services, so mail, payments and scheduled jobs in the copied site still point at your live accounts until you change them. The move guide says to turn those off on the copy before you open it, so a second site doesn’t send emails or charge cards. It also warns that a completed copy doesn’t mean every plugin works on the new server.

Here’s what we check after every move, including the ones that bit us when we moved our own website to snazzysolutions.com in November:

  • Outgoing email. SMTP plugins such as FluentSMTP store your mail password encrypted with the security keys in wp-config.php. If the new setup uses different keys, email stops with “Could not authenticate.” After our own move, our site’s outgoing email stopped with that exact error until we re-entered the mail password. We wrote up the same failure in how WP Engine’s salt change broke FluentSMTP.
  • Premium plugin licenses. Some licenses are tied to the site address. Our Elementor Pro license dropped after our domain change and had to be reconnected.
  • Scheduled tasks. Many hosts run WordPress’s scheduled tasks from a server cron job instead of on page visits. On a new server, or even after a domain change, that job may not exist. Ours disappeared after the change, and scheduled jobs sat stuck for about four and a half hours until we recreated it.
  • SSL. The new host needs a certificate for your domain before you switch DNS, or visitors get a security warning.
  • Caching and PHP version. Clear every cache layer after the switch, and make sure the new server runs the PHP version your plugins need. Our guide to updating PHP in WordPress covers how to check.
  • Forms, logins and payments. Submit a real test form, log in, and run a test order if you sell online.

How do you move a WordPress site without downtime?

Build and test the copy while the old site stays live, pause edits, run one final copy, switch DNS, and keep the old host running until everything checks out.

Reprint’s move guide explains why the pause matters. A copy of a live site isn’t one frozen snapshot, so new posts, uploads, orders and accounts created while it runs can be missed. Plan a short write pause and a final copy. Test the new server with your host’s preview address or a local DNS override before you change public DNS.

Google’s hosting change guide gives the same advice for the end of the move: only shut down the old hosting once all users, including Googlebot, are getting the site from the new one. Keep the old host for a few days after the switch so there’s a way back.

Does moving hosts hurt your SEO?

Not if your domain and URLs stay the same and the new site works. Google treats it as a hosting change. Changing the domain at the same time is a much bigger job.

Google has separate guides for changing your hosting without changing URLs and for site moves with URL changes. A plain host move keeps every address the same, so there’s nothing to redirect. The risks are practical ones: the new copy blocking search engines by accident, missing pages, or a slow server.

If you’re also changing your domain or rebuilding the site, plan redirects and a Search Console change of address. That’s the move we just did with our own site. Our website migration SEO checklist walks through it.

Frequently asked questions

Is WordPress Reprint free?

Yes. Reprint is free and open source, made by WordPress.org. The plugin is in the WordPress.org Plugin Directory, and the command-line client is a free download.

Does Reprint change my domain’s DNS?

No. Reprint copies files and the database. You still point your domain at the new host yourself, through your domain registrar or DNS provider, after you’ve tested the copy.

Will my email stop working when I move hosts?

Your inbox usually won’t, because email is often hosted somewhere else. Emails your website sends, like form notifications, can stop if the SMTP password was encrypted with old security keys. Send a test form after every move.

Can I keep my old host running during the move?

Yes, and you should. Keep the old site live while you copy and test, pause edits for the final copy, then switch DNS. Cancel the old hosting only once everything works on the new server.

Does moving to a new host change my URLs?

No, not if you keep the same domain. Your pages keep the same addresses, so you don’t need redirects. Changing the domain at the same time is a separate job that needs redirects.

Moving hosts is a good time to fix what the old host got wrong. If you’d like us to handle the move, test everything on the copy and keep your site updated afterwards, talk to us or see what a WordPress maintenance plan includes.

How We Help
Real Results