MoveMyWebsites

Craft CMS migration

Move Beyond Your Current CMS. Not Your Brand.

Document sections, custom fields, asset relationships and localization. Recreate the content model and editor previews deliberately, whether Craft remains a backend or the project replaces it.

Where Craft CMS sites get stuck

Specialist dependency

Craft is a capable CMS, but Twig templating and plugin development knowledge can be harder to find than general React expertise.

Licence and upgrade cycles

Major Craft versions can require coordinated updates across plugins and templates, which adds planning overhead to small changes.

PHP hosting requirements

Self-hosted Craft sites need a maintained PHP runtime, database and server configuration that someone must keep current.

Who this is for

Craft CMS Migration: what we migrate.

For well-structured Craft sites where sections, entry types and Matrix blocks deserve a front end that is easier to staff and extend.

Keeping Craft as your content backend and changing only the public site? Compare our approach to website modernization.

  1. Scope 01

    Schema mapping

    Sections, entry types, fields, categories and globals are documented and mapped one-to-one into the destination content model.

  2. Scope 02

    Matrix and Neo blocks

    Flexible content blocks become typed React components, so editors keep the same building-block approach.

  3. Scope 03

    Twig to components

    Templates, macros and includes are translated into components with equivalent markup and responsive behaviour.

  4. Scope 04

    Headless or replatform

    We compare keeping Craft headless through its GraphQL API against moving content to a different CMS, and recommend one with reasons.

Benefits of modernizing

What you gain.

  • Keep your Matrix and entry structure
  • Recreate Twig templates as components
  • Preserve URLs and metadata
  • Choose a modern editing experience
  • Reduce server-side runtime dependencies
  • Broaden your developer pool

Features we preserve

What comes with you.

Sections, entry types and fields
Matrix content blocks
Asset volumes
Multi-site and localisation structure
SEOmatic metadata
Forms and integrations

Migration process

How a Craft CMS migration runs.

  1. 1

    Inventory

    We crawl and catalogue your Craft CMS pages, templates, media, forms and integrations so nothing is left to memory.

  2. 2

    Map

    Every existing URL is paired with its new destination, metadata and redirect rule before a single component is built.

  3. 3

    Rebuild

    Your design and content are recreated as typed React components on a modern framework, with an editing workflow that suits your team.

  4. 4

    Verify

    Forms, redirects, responsive layouts, metadata and analytics are checked against the original inventory.

  5. 5

    Launch

    We coordinate DNS, hosting and post-launch monitoring with you, on a schedule agreed after project review.

Migration considerations

What we plan for before building.

Image transforms

Named Craft transforms are replaced with modern responsive image handling. Focal points are carried across where available.

Relations between entries

Entries, categories and assets relationships are preserved by ID during import so related listings still work.

Commerce and plugins

Craft Commerce, Formie, Freeform and custom modules are each reviewed in discovery for rebuild or replacement.

Deliverables

  • Content model map from Craft fields
  • Component equivalents for Matrix blocks
  • Asset volume transfer with transforms
  • SEOmatic metadata and redirect export
  • Multi-site and locale routing plan
  • Editor walkthrough before launch

Not promised

  • Fixed timelines before template review
  • Recreating unused fields

Interactive assessment

See what your Craft CMS site is made of.

A read-only, preliminary look at public signals. Takes a few seconds.

movemywebsites / assessment read-only

Paste your website address.

Likely platform
SEO and content
Sitemap and robots
Complexity

A migration plan built around your website

Document sections, custom fields, asset relationships and localization. Recreate the content model and editor previews deliberately, whether Craft remains a backend or the project replaces it.

Analyze, plan, rebuild, verify, launch

We review publicly visible signals first, then confirm content, design and functionality requirements with you. We inventory URLs, map integrations and agree acceptance criteria before rebuilding. Verification covers responsive layouts, important journeys, forms, redirects and SEO essentials. Launch is coordinated with the people responsible for hosting and domain access.

What we aim to preserve

Your branding, useful content, media, important URL paths and business-critical functionality are reviewed individually. Not every plugin or feature has a direct equivalent. We explain what can be recreated, what should change and which third-party services need separate configuration.

Clear expectations

Discovery determines scope, pricing and timing. We do not promise guaranteed rankings, automatic performance gains or a completion date before review. Ongoing maintenance and security responsibilities remain part of the plan.

Plan your next step

Request a personalized migration assessment at /start. We will review your existing website and requirements before proposing scope, pricing or timing.

FAQ

Craft CMS Migration, answered.

Talk to us

Get hands-on help moving your website.

Need to move quickly? Share your site and preferred timeline. A specialist reviews the requirements and replies with options and next steps. No obligation.

Bring your website address, your essential features and your preferred timeline. We’ll discuss what can move, what needs rebuilding and what requires a separate integration before proposing a scope.

Request your migration assessment

Common for these industries

Related migration services