Move your WordPress site with Reprint
You can change WordPress host and bring your existing site with you. On 13 November, WordPress introduced Reprint to a wider audience as a way to copy the files and database to a new destination. If worries about the transfer have kept you with a host you want to leave, this gives you another way to prepare the move.
- Author
- Intercube
- Published
- Reading time
- 4 min read
01
A copy you can open before you move
WordPress introduced Reprint as a free, open-source tool for copying a site to a computer or another host. It transfers the files and database directly, including the content and settings that make the site yours. The original site can continue serving visitors while the first copy is prepared.
That is useful if you want to see the website on a new server before making a commitment to switch traffic. Start with the pages customers visit most. Your theme, uploaded images and the plugin behind the enquiry form all need to make the journey.
02
What access do you need from the old host?
The Reprint plugin runs on the WordPress site you are copying. A client connects over HTTPS after you authorize it in WordPress. The destination needs a web server and database prepared for the copy. Use the official migration guide to check the access and runtime requirements before choosing this route.
Give the person managing the move a clear record of what sits outside WordPress. The domain may be held elsewhere, email can use another provider, and an external service may send data back to a specific address. These are things to bring into the migration conversation before changing any routing.
03
Choose a moment for the last changes
A site can receive new uploads and orders while the first copy is running. Agree when you will pause those writes and take the final copy. For a shop, reconcile recent orders with the team handling payment and fulfilment. Work out the fallback point before you send customers to the destination.
Test the destination with production notifications and payments kept inactive until the agreed cutover. Check an enquiry end to end, confirm that the right people can log in, and verify that scheduled tasks will run in the intended place. Once the final copy is accepted, follow the agreed domain and certificate setup and watch the first live requests.
04
Move to Intercube with the migration included
When you move to Intercube managed hosting, we agree the transfer scope with you and prepare the destination infrastructure. Your developer can validate the copy in a staging or preview environment while our engineers handle the server configuration and coordinate the cutover. We select the transfer method around the site and the access available.
Migration to Intercube managed hosting is included at no additional cost. Bring us the current website and the parts your team wants to improve, such as slow support or a deployment setup maintained by one developer. We can plan the new environment and establish who operates it after the move.
Agree the move with your host
- Confirm access to the source site and domain.
- List services connected to WordPress.
- Check the destination with your real site.
- Agree the write pause, final copy and fallback.
- Define who operates the environment after the move.