Most of what goes wrong in a move is invisible on the day. We ran a small test on 10 October 2026. A setting held a web address, and a plain find and replace swapped in a new domain. PHP 8.4.13 then returned false when it tried to read the setting back. The site would have loaded. The theme would have lost an option, quietly.
Planning a move? Tell us about the site
We are DistroCode, a US company that builds WordPress sites and writes its own plugins under the name PluginSprout. We have been building websites since 2017, and DistroCode LLC was registered in 2023. Moves are one part of that work. We copy WordPress sites to a new host, and we rebuild Wix, Joomla and Squarespace sites in WordPress.
The same list for every move, large or small.
Your old site stays as it is until you have seen the new one and said yes. Nothing is switched off or deleted on our side before then.
Each kind of move carries over a different share of the old site, so each one gets its own plan. Joomla sites are rebuilt the same way as Wix sites, and the quote says what carries across.
This is the closest to a straight copy. The files and the database move across, and WordPress itself stays the same.
The risk is in the details. WordPress stores its own address in two settings named siteurl and home, and many themes and plugins store full web addresses inside their settings too. If the domain changes, every one of those has to change with it.
A plain find and replace on the database can break them. We tried it before writing this page. A setting saved by PHP read s:22:"https://old-host.test/", where 22 is the length of the address. After a plain replace with a 29-character address, the 22 stayed. PHP’s unserialize returned false, and that is what WordPress 7.1.2 hands back to the theme in place of the setting (PHP 8.4.13 on our own machine, October 10, 2026; maybe_unserialize, wp-includes/functions.php, lines 653 to 659).
The WordPress handbook gives the same warning: “If you do a search and replace on your entire database to change the URLs, you can cause issues with data serialization” (Moving WordPress, checked October 10, 2026). So we use a replace that rewrites those lengths, and we check the settings pages afterwards.
A Wix site cannot be moved as files. Wix says a site “needs to be hosted and operated on Wix’s servers” (Wix Help Center, checked October 10, 2026).
So a Wix move is a rebuild. We copy the text and images across, build the pages again in WordPress, and set the layout to match as closely as WordPress allows. Your domain name can come with you, and we check where it is registered before planning the switch.
Squarespace exports a file in WordPress format, but only part of the site goes into it. Its help page lists what stays behind: store pages, product blocks, drafts, custom CSS, and “More than one blog page” (Squarespace Help Center, Exporting your site, checked October 10, 2026).
A one-blog site with simple pages comes across fairly whole. A Squarespace store does not: the products have to be moved another way, and the quote says how.
If you want to stay on Squarespace and change the design instead, that is our Squarespace website design service.
Often, for a plain WordPress site moving from one host to another. Some hosts move a site in for free when you sign up, and if the domain stays the same, that may be all you need.
It is not enough when the site is moving off Wix, Joomla or Squarespace, because that is a rebuild and not a copy. It is also thin when the site takes orders or bookings, or when nobody will check the forms and the checkout once the copy lands.
If the host’s free move suits your site, take it. We would rather tell you that than quote for it.
We cannot promise rankings. What we can do is keep the addresses search engines already know working.
That is what the address list is for. Before the move, we list every page address on the old site. After it, each old address either works as it did or redirects to the page that replaced it.
Moves off Wix or Squarespace usually change addresses, because WordPress builds its addresses its own way. A host-to-host move with the same domain usually changes none.
In six steps.
Before the domain switches, we check:
After the switch, we check the same list again on the live domain.
Moves have limits, and these are ours. Read them before you ask for a quote.
Every move is quoted per site, after we have seen it. The quote names the price and lists what moves and what is rebuilt.
On a WordPress to WordPress move, yes. Orders, customers and products live in the database, and the database moves with the site.
The risk is the gap. An order placed on the old site after the final copy is taken is not on the new one. That is why we pause new orders for the final copy.
A Squarespace store is different, because its export leaves products and store pages behind. The quote says how the products will move.
We will not give a number before we have seen the site. The new site is built and checked while the old one keeps running, so most of the work happens with no downtime at all.
Yes: admin access to the old site, and access to the new hosting account. For a domain switch, we also need access where the domain is registered, or someone who can make the change with us.
A separate admin user for us is better than sharing your own password, and you can delete it when the move is done.
You can take it from there yourself. If you would rather have someone keep it updated, our WordPress maintenance plan is $99 a month, or $229 a month for a WooCommerce store.
By email at sales@distrocode.com or through the contact form. We reply in writing within one working day, Monday to Friday, so you keep a record of what was said.
Tell us where the site is now, where it is going, and whether it takes orders or bookings. Contact us or email sales@distrocode.com, and we will reply with the questions we need answered before we can quote the move.