migrations
Website migration services, run as engineering projects.
I move sites off hosted builders and page-builder plugins, and off WordPress when another stack fits better, onto platforms their owners control. Every URL is mapped, every import is scripted, and the old site stays live until the new one is verified.
- timeline
- 2–6 weeks with URL and SEO parity
- urls
- 100% mapped: kept or 301
- downtime
- none; DNS cutover only
- pricing
- fixed scope after audit
- rollback
- old site kept live 30 days
01 / migration paths
Pick your starting point.
Each path has its own page covering what transfers, the process, the risks and an FAQ. Not listed? The process is the same; ask.
from a hosted platform
- Wix to WordPress Crawl-based move to a block theme you own
- Shopify to WordPress Products, customers and orders to WooCommerce
- Squarespace to WordPress Posts, pages and products with URL parity 3–5 wks
- Webflow to WordPress CMS collections to custom post types and blocks 4–6 wks
- hubspot to WordPress Pages, blog and forms moved, CRM tracking kept
- Framer to WordPress Design-led marketing sites as an editable block theme
- Weebly to WordPress Pages, blog and store off Weebly or Square Online
from a WordPress page builder
- Elementor to native blocks Builder layouts rebuilt as core blocks and patterns
- Divi to native blocks Shortcode layouts replaced by blocks, content kept
- wpbakery to native blocks Shortcodes out, native blocks in
- Oxygen to native blocks Builder templates rebuilt as a block theme
from WordPress to another stack
02 / included
What every migration includes
The source platform changes the tooling. It does not change the standard the work is held to.
URL inventory and redirects
Every indexed URL is crawled and given a destination. Redirect rules are written as code and tested in CI before and after cutover.
redirects.csv · test suite
Scripted content import
Imports are scripts, not copy and paste. They can be run again and again, are checked with record counts, and run one last time right before launch.
import log · diff report
A repository you own
The new site lives in your Git repository, with linting, static analysis and tests running from the first commit.
git · ci · code review
Search equity carried over
Titles, descriptions, canonicals, alt text and structured data move with the content. Search Console is monitored for 60 days after launch.
metadata parity · 60-day watch
Accessibility and performance
WCAG 2.2 AA and performance budgets are checked in CI, so the new site is measured against the old one, not just moved.
axe-core · Lighthouse CI
A way back
Your current site stays live until the new one is verified. The switch is a DNS change, and the old site is kept as a fallback.
low-TTL DNS · 30-day fallback
03 / process
The migration, step by step
Each step has a written deliverable you sign off before the next one starts. Your current site stays live throughout.
-
Audit and crawl
Crawl the live site, export what the platform allows, and inventory templates, content types, forms and third-party scripts.
-
URL and redirect map
Every indexed URL gets a destination. Redirect rules are written as code and tested in CI.
-
Content model
Map source content to the target structure: post types, fields, taxonomies, blocks.
-
Build on staging
Build the theme and components in a Git repo with CI from the first commit.
-
Scripted content import
Repeatable import scripts, verified with counts and spot checks, re-run right before launch.
-
Pre-launch QA
Redirect tests, broken-link crawl, accessibility and performance checks, form submissions end to end.
-
Cutover and monitoring
Low-TTL DNS switch, live redirect verification, and 60 days of Search Console and error monitoring.
04 / an honest note
When not to migrate
A migration is a cost. If one of these describes you, I will say so in the audit, and the audit is still yours to keep.
- Your current platform does what you need and the bill is reasonable.
- The site will be replaced or retired within a year.
- Nobody will own the new site after launch. A hosted builder is safer than an install no one maintains.
- The real problem is the content or the offer, which a new platform will not fix.
05 / faq
Frequently asked questions
Will I lose my search rankings?
Rankings can dip briefly after any migration. Preserving URLs where possible, 301-redirecting the rest and carrying over metadata keeps that dip small and short. I monitor Search Console for 60 days after launch.
How long does the migration take?
Moving the content itself usually takes days. Doing it with every URL mapped, redirects tested and search metadata carried over takes two to six weeks from audit to launch. Sites with large catalogues, many integrations or multiple languages take longer; the audit gives you a firm timeline.
Will my site go down during the migration?
No. The new site is built and tested on staging while your current site stays live. The switch is a DNS change, and the old site is kept available as a fallback.
Can my team edit content during the migration?
Yes, until a short content freeze before launch, usually one or two days. The import is scripted, so it re-runs to pick up late changes.
What does it cost?
Pricing is fixed after the audit, based on page count, content types and integrations. The audit itself is a fixed fee and the deliverables are yours either way.
Start with a fixed-price migration audit.
A crawl of your current site, a URL and redirect map, and a written scope with risks named up front. Yours to keep, whoever does the build.