Drupal to Wagtail migration

Drupal to Wagtail migration

I move Drupal sites to Wagtail CMS, content and custom features included. We look at how your editors work and decide what to simplify. I build the editing tools, migrate the content, and handle the launch.

Who this service is for

You might be a site owner, publisher, agency, or team planning a move from Drupal. You want to keep your content and the features you use, but on a more robust, modern CMS.

How the service works

For example

Your Drupal site has years of articles, resources, and topic pages. Editors work through a growing set of fields and modules, and the coming rebuild is a chance to simplify. I bring that content into Wagtail, organize the editing tools around your work, and plan where every existing URL will lead.

This is an example. We'll work out the details for your project together.

  1. I map what your Drupal site does

    We walk through how you publish. I review content types, fields, taxonomy, media, and menus, along with custom modules, Views, languages, and integrations. Then we decide how each feature you need will work in the new site.

    What you get: A content and feature inventory, with a shared plan for what we're moving and improving.

  2. We try the new editing tools with your content

    I turn your content into clear page types and reusable blocks, then build a small working example with the permissions and publishing steps your editors need. They try it on real tasks, and we refine it together.

    What you get: An editing setup you've tried with your own content before the full migration.

  3. I move your content, then we review it together

    I build a repeatable import for the content, media, and relationships we've agreed to move. I check content counts, links, and any translations on a preview site. We review sample pages together, and I refine the import from what we find.

    What you get: Your content in Wagtail, checked, with an import I can run again at launch.

  4. I prepare the site for visitors and search

    I keep useful URLs and redirect the ones that change. I check titles, descriptions, canonical URLs, internal links, and the sitemap. I also test forms, search, integrations, and key pages across screen sizes.

    What you get: A tested site, with redirects for changed URLs and checked search metadata.

  5. You publish in Wagtail with your latest content in place

    We agree on the final content sync and any brief publishing pause. I move the latest content, launch the site, and show your editors how to use it, so they can start publishing in Wagtail. After launch, I usually stay on for maintenance and improvements.

    What you get: Your content live in Wagtail, editors ready to publish, and continued maintenance from me.

What you get

  • A Wagtail site with page types, editing tools, and features designed around your content.
  • A repeatable content migration, checked media and relationships, and a URL redirect map.
  • Launch support, editor training, and arrangements for maintenance after launch.

How we’ll work together

We plan the move around the size of your content library, custom Drupal features, and how often you publish. A sample migration gives us something concrete to review before we settle the full schedule.

Relevant experience

I worked with Drupal for eight years before I discovered Wagtail, so I know Drupal inside out. That helps me untangle your existing content types and custom features and work out how to rebuild them in Wagtail. I've also spent years building and maintaining Django and Wagtail projects.

Questions about Drupal to Wagtail migration

Can you move custom content types and taxonomy?

Yes. I map your content types, fields, and taxonomy to matching Wagtail structures. The plan also covers relationships between pages, shared content, images, documents, and the languages you publish in.

What happens to Drupal modules and Views?

I look at what each one does for your site and recreate the features you need with Wagtail, Django, or a suitable integration. That's also a chance to simplify the setup around how you work today.

How do we look after SEO during the move?

I record existing URLs and search metadata, keep URLs where practical, and redirect the ones that change. Before launch, I check links and indexing settings. After launch, I monitor crawl results and search performance and adjust where needed.

Can we keep publishing during development?

Yes. Your Drupal site can stay live while I build and test the Wagtail site separately. We plan the final sync together, including any brief publishing pause, so the new site launches with your latest content.

Coming from WordPress? See WordPress to Wagtail migration.

Drupal to Wagtail migration

Tell me what you need

Send me a link to your Drupal site and tell me what you'd like to make easier. A rough idea of your content, custom features, and preferred timing helps us start planning.

I'll read your message and reply with questions or a suggested next step.

Your message is sent to Tim about this service. This form does not subscribe you to the newsletter.