WordPress Migration

Who this is for

• A business moving from Wix, Squarespace, Shopify, Webflow or another platform to WordPress
• A site owner changing hosts for speed, cost or support reasons
• A company consolidating several sites into one, or splitting one into several
• A team moving from a page builder or an abandoned theme to a clean custom build

What's included

• Full backup before anything moves
• Staging copy to test the new setup
• Complete transfer of content and media
• Redirect mapping to protect SEO
• DNS and hosting configuration
• Post move testing of pages and forms
• Speed check on the new environment
• A launch plan that avoids downtime

Scope: what is in and what is usually separate

A fixed-scope quote only works if the scope is clear. This is how we usually draw the line; anything in the right column can be added and priced separately.

Included in a typical quote	Quoted separately or not included
An audit of the current site: pages, posts, media, forms, URLs	A new design or theme (often combined with a migration but quoted separately)
A full backup before anything moves	Rewriting content or fixing old SEO problems
Transfer of content, media, users and settings	Moving email hosting (we advise and coordinate)
A redirect map from every old URL to its new home	Hosting, domain and licence fees
DNS, SSL and hosting configuration	Store order-history migration beyond what the platform exports
Post-move testing of pages, forms, search and speed	Ongoing maintenance after the move

How we approach it

1. Audit and plan. We crawl the current site, list every URL and asset, note forms and integrations, and choose a migration method that fits the source platform. You get: a migration plan, a URL inventory and a fixed quote.
2. Back up and stage. We take a complete backup and build the new site on staging, so the live site keeps working untouched. You get: a staging copy to review.
3. Transfer. We move content, media, users and settings, then clean up what the export mangled: formatting, embedded images, internal links. You get: content in place and checked.
4. Redirects and testing. We map old URLs to new ones, test every important page, form and integration, and measure speed on the new host. You get: a tested site and a signed-off redirect map.
5. Go live. We switch DNS at a quiet time, verify SSL, redirects and forms, and monitor search traffic for the following weeks. You get: a live site with rankings protected.

What you receive at handover

• The full pre-migration backup
• A URL inventory and redirect map
• Hosting, DNS and SSL configured and documented
• A post-move test report
• Search Console checks after launch
• A defect warranty period on what we built

Migration paths and what each one involves

The source platform decides most of the work. Some exports are clean; some need rebuilding by hand.

Option	When it fits
WordPress host to WordPress host	The simplest case. Files and database move as-is, DNS switches, and we test. Usually days, not weeks.
Wix or Squarespace to WordPress	Content exports are partial. Pages are rebuilt in a theme, posts and images imported, redirects set for every URL.
Shopify to WooCommerce	Products, customers and often orders export well. Payment, shipping and tax must be rebuilt and tested with real orders.
Page builder to a custom theme	A rebuild of layouts into clean blocks while keeping URLs and content. Often paired with speed work.
WordPress.com to self-hosted	Content moves easily; the work is choosing hosting, replacing built-in features with plugins and redirecting the old address.

Technologies we use

• WordPress
• PHP
• MySQL
• WP-CLI
• Cloudflare
• phpMyAdmin
• Git
• REST API

What drives the cost

We quote fixed-scope after a free consultation rather than publishing a rate card, because the same service can be a small job or a large one. These are the factors that move the number.

• Source platform. A clean export saves days. Platforms with locked-in layouts mean pages are rebuilt by hand.
• Volume of content and media. Fifty pages is different from five thousand posts and a decade of images.
• URL structure changes. Keeping URLs is cheap. Changing them means mapping and testing every redirect.
• Forms, integrations and store data. Each connection is rebuilt and tested on the new site.
• Whether a redesign is included. Moving as-is is a migration. Moving into a new theme is a migration plus a build.

See the pricing page for how we scope and quote, or send a brief through the contact page for a written estimate.

How long it takes

A host-to-host move usually takes 2 to 5 days. A platform migration takes 2 to 6 weeks depending on content volume and whether pages must be rebuilt.

• Content volume and how clean the export is.
• Number of URLs that change and need redirects.
• Store data and payment testing for ecommerce moves.
• DNS propagation and access to the registrar on launch day.

Risks and how we manage them

• Lost rankings. Every old URL is redirected, titles and metadata carry over, and we watch Search Console after launch.
• Downtime during the switch. The new site is fully tested on staging and DNS switches at a low-traffic hour with the old site still running.
• Broken forms or missing images. A post-move checklist covers every form, embed and image path before we call it done.

A worked example (illustrative)

Illustrative only. A landscaping company on Wix with 22 pages, a blog of 80 posts and a quote form wants a faster WordPress site with the same URLs where possible. Week one: audit, plan and staging build. Weeks two and three: page rebuild, post import, image cleanup and 110 redirects. Week four: testing, DNS switch on a Tuesday evening and Search Console monitoring.

Why choose us

• No lost content and no broken pages
• Redirects that protect your rankings
• Testing on staging before the switch
• Launches timed to avoid disruption