migration service

Webflow to WordPress migration

Move your site to a platform you own, with every URL preserved or redirected and the content model rebuilt as editable blocks.

migration.spec
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 / why teams migrate

Why teams make this move

01

Limits of the current platform

Plan caps and per-site pricing become a constraint once content and locales grow.

02

Editorial flexibility

Editors get reusable blocks and patterns instead of designer-only layouts.

03

Ownership and extensibility

Self-hosted code in your Git repo, custom post types, and any integration a plugin can reach.

02 / scope

What transfers, and what doesn’t

  • transfers
  • rebuilt
  • doesn't transfer
Area Status Notes
Content transfers Pages and collections exported via the platform’s API or export file; fields mapped to custom post types and meta.
URLs and redirects transfers Every indexed URL is crawled, mapped and either kept or 301-redirected. Tested before and after DNS cutover.
SEO equity transfers Titles, meta descriptions, canonicals, alt text and structured data carried over; Search Console monitored for 60 days.
Design and layout rebuilt Rebuilt as a component system, not copied pixel for pixel. Same look where it works, improved where it doesn’t.
Forms rebuilt Forms are rebuilt; submission history exported to CSV.
Integrations and scripts doesn't transfer Platform-specific interactions and automations don’t transfer; rebuilt only where they earn their weight.

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.

  1. Audit and crawl

    Crawl the live site, export what the platform allows, and inventory templates, content types, forms and third-party scripts.

    deliverable: inventory + scope document

  2. URL and redirect map

    Every indexed URL gets a destination. Redirect rules are written as code and tested in CI.

    deliverable: redirects.csv + test suite

  3. Content model

    Map source content to the target structure: post types, fields, taxonomies, blocks.

    deliverable: content model spec

  4. Build on staging

    Build the theme and components in a Git repo with CI from the first commit.

    deliverable: staging URL + repo access

  5. Scripted content import

    Repeatable import scripts, verified with counts and spot checks, re-run right before launch.

    deliverable: import log + diff report

  6. Pre-launch QA

    Redirect tests, broken-link crawl, accessibility and performance checks, form submissions end to end.

    deliverable: signed QA checklist

  7. Cutover and monitoring

    Low-TTL DNS switch, live redirect verification, and 60 days of Search Console and error monitoring.

    deliverable: launch report + 60-day check-in

04 / risk register

Risks, and how I reduce them

R1

likelihood: medium

Lost rankings from broken or missing URLs

Mitigation: Full URL inventory, redirects tested in CI, and post-launch crawl comparing old and new.

R2

likelihood: medium

Content lost or mangled in transfer

Mitigation: Scripted, repeatable imports with record counts and a diff report reviewed before cutover.

R3

likelihood: low

Downtime during the switch

Mitigation: DNS TTL lowered days ahead; the old site stays live until the new one is verified.

R4

likelihood: low

A missed integration or tracking script

Mitigation: Script inventory from the audit, tag verification on staging, and analytics parity checks after launch.

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.