Skip to main content

Drupal Upgrades and Website Migrations

Drupal 10 support ends on December 9, 2026. We upgrade Drupal 7, 8, 9 and 10 sites to Drupal 11, and move websites to a new platform or host with their URLs and search rankings protected.

Intro text

iTech4Web's Drupal upgrade services move Drupal 7, 8, 9 and 10 websites to Drupal 11, the current major version. Drupal 10 reaches end of life on December 9, 2026, and Drupal 7, 8 and 9 no longer receive security fixes. We review your site for free, send a quote with the price, timeline and scope, upgrade it on a separate copy and support it after launch. We also handle website migrations: to Drupal from WordPress, a custom CMS or another platform, and from one host to another. Your URLs and search rankings carry over to the new site.

Drupal 10 end of life

Drupal 10 support ends on December 9, 2026

After that date, drupal.org will make no new Drupal 10 releases, so Drupal 10 core gets no more security fixes. Drupal 12 is planned for the same week. Drupal.org usage statistics for the week of September 20, 2026 show that more than 200,000 sites still run Drupal 10 and about 90,000 still run Drupal 8 or 9, which are already out of support.

Support ended January 5, 2025

Drupal 7

Support ended in 2021

Drupal 8

Support ended in 2023

Drupal 9

Support ends December 9, 2026

Drupal 10

Current version, the upgrade target

Drupal 11

Planned for the week of December 7, 2026

Drupal 12

Your site keeps running

Nothing switches off on December 9. The risk grows over time, as each new security issue found in Drupal 10 stays unpatched on your site.

Modules move on

Contributed module maintainers drop old Drupal versions, so fixes and new features go to Drupal 11 and 12.

Hosting moves on too

Drupal 11 runs on PHP 8.3 or 8.4 (8.4 recommended), and Drupal 12 will need PHP 8.5, so an upgrade often comes with a server update.

Upgrades and migrations we handle

Drupal 7 to 11
Drupal 8 and 9 to 11
Drupal 10 to 11
WordPress to Drupal
Custom CMS to Drupal
Hosting moves
PHP and server updates
WordPress
Custom PHP sites
Static sites
Headless front ends

Drupal is where we have the most depth. We also upgrade, move and support WordPress, custom, static and headless sites.

Drupal upgrades, moves to Drupal and the server work around themOther platforms and stacks we move, upgrade and support

Sources: drupal.org core release schedule, Drupal core usage statistics and PHP requirements, checked October 4, 2026. Last updated: October 16, 2026.

How it works

How an upgrade or migration works

1

Review and quote

We look at your platform and version, modules or plugins, custom code, theme, content, integrations and hosting, and on Drupal 8 and later we run the Upgrade Status report. You get a written list of what needs work and a quote with the price, timeline and scope. The review is free, for upgrades and for migrations.

2

Work on a copy

We upgrade or migrate a separate copy of your site. Your live site stays as it is, and your team keeps editing.

3

Test together

You check the new site on a staging address. We compare pages, forms, redirects and search settings with the live site and fix what we find.

4

Launch and support

We switch over at a time you choose, bring over content your team added in the meantime and check the site after launch. If you want, we stay on for updates and fixes under a support plan.

Extra changes you ask for along the way, such as fixing a slow form, are priced separately so you can decide on each.

Your starting point

Every Drupal version has its own path to Drupal 11

Most urgent

Drupal 10 to Drupal 11

The shortest path, because Drupal 11 updates the site you already have. We update custom code that uses deprecated functions, replace modules that have no Drupal 11 release, move the server to PHP 8.4 and test everything on a copy. Book, Forum, Statistics, Tour and Activity Tracker left Drupal core in 11.0, so sites that use them switch to the contributed versions.

Out of support

Drupal 8 or 9 to Drupal 11

Still an update of your existing site, done in two steps through Drupal 10. Typical work: CKEditor 4 replaced with CKEditor 5, the retired Seven admin theme replaced with Claro, custom JavaScript moved from jQuery.once to the Once library, and every contributed module brought to a supported release.

Out of support

Drupal 7 to Drupal 11 migration

A new Drupal 11 site with your content moved over. We use Drupal's core Migrate API, so the migration can run again right before launch and pick up anything your team published in the meantime. We rebuild the theme and can keep your current look or refresh it.

Need more time? On a care plan, we keep your Drupal 7 site running and make fixes while the upgrade runs. The plan does not cover Drupal 7 security: the upgrade does.

Any stack

Moving to another platform or host?

If Drupal no longer fits, or you are coming to Drupal from somewhere else, see website migrations below. If a simpler platform would serve you better, we will say so in the review. We also run website support and project takeover for sites on any stack.

For the technical side, read our guide to upgrading Drupal 8 and 9 to Drupal 11.

What's included

What our Drupal upgrade services include

Upgrade review

We check your version, modules, custom code, theme, content, integrations and hosting, then send a written list of what needs work and a quote with the price, timeline and scope. The review is free.

Modules and custom code

We update or replace contributed modules and rewrite custom modules for current APIs. When a module needs a fix to run on Drupal 11, we patch it and share the patch on drupal.org.

Content and data migration

We move pages, media, users, menus, taxonomy and custom data with Drupal's Migrate API, from an older Drupal version or another platform, and run it once more right before launch.

Theme and editing

We update or rebuild your theme, set up CKEditor 5 for your editors and replace retired admin themes with Claro.

URLs, redirects and SEO

We keep your URLs or send the old ones to the new ones with 301 redirects, and carry over page titles, meta descriptions and the XML sitemap.

Hosting and PHP

We bring the server to PHP 8.4, the version Drupal 11 recommends (8.3 is the minimum), and update the other components Drupal 11 needs, or move the site to new hosting if your current host can't run it.

Testing on staging

Your team clicks through the upgraded copy and approves it before anything changes on the live site.

Launch and support

We switch over at a time you choose, check the site after launch and, if you want, keep it updated under a support plan.

From a client project

When we upgraded Humanitarian Outcomes from Drupal 7 to Drupal 11, the site review showed they were paying for more web infrastructure than they needed. Cutting it reduced their website operating costs by a factor of three. The upgrade was finished before Drupal 7 support ended on January 5, 2025.

Website migrations

Website migrations to Drupal and between hosts

Sometimes the right move is a different platform or a different host. We move sites to Drupal and between hosts, and we plan each move around your content, your URLs and your search rankings.

To Drupal

From WordPress, a custom CMS or another platform

For sites that have outgrown their platform: more content types, more editors with different permissions, several languages or links to other systems. We map your content to a Drupal structure and move it with Drupal's Migrate API, including data from JSON files or another system's API.

Hosting

To a new host or server

When your host raises prices, ends your plan or can't run current PHP, we move the code, database and files to a new server, test the site there and switch over at a time you choose.

Any stack

Custom, static and headless sites

We also move custom PHP, static and headless sites, and rebuild a site on a new stack when an upgrade would cost more than it is worth. Drupal is where we have the most depth, and we recommend it only when your content and team need it.

From a client project

"We had a need to move our site in 72 hours, or lose all of our Data." That is how Kate Sánchez, editor-in-chief of But Why Tho?, a US entertainment publication, described the start of our project in a Clutch review. We moved the WordPress site, about 17,000 posts, to a new server before the old host's termination deadline, with zero downtime and no lost content, comments or media. We also tuned the database, and site search time dropped from between 21 and 73 seconds to 0.55 seconds. Read the review on Clutch

Search rankings

How we protect your search rankings during a migration

Traffic lost after a migration often traces back to a few technical details: missing redirects, changed page titles and wrong signals to search engines. We check them on every upgrade and migration.

A list of every URL

Before we start, we collect the addresses that visitors and search engines use, from your sitemap, the live site and, with your access, Search Console, so every page gets a destination on the new site.

A 301 for every changed URL

We keep your URLs where we can. Where an address has to change, it gets a 301 redirect to the matching new page, not a blanket redirect to the home page.

Titles, tags and language signals

We carry over page titles, meta descriptions, canonical tags, hreflang on multilingual sites, structured data and the XML sitemap, and check them on the new site.

Checks before and after launch

We compare the old and new sites before launch, then watch for broken links, 404 errors and crawl problems after it and fix what turns up.

From a client project

A multilingual real estate site came to us after another developer had upgraded it to Drupal 11, and it was losing ground in Google. Our audit found the cause in its configuration, not its speed: listing titles had lost their prices, canonical tags pointed search engines at another language version, and one domain redirected to the wrong site. We fixed all three, and the fixes went live in August 2026.

Proof

Drupal upgrades and migrations we have delivered

We have upgraded data-heavy nonprofit sites from Drupal 7 and Drupal 9, moved sites to Drupal from WordPress, a custom CMS, a headless stack and other systems, and we run our own site on Drupal 11.

Drupal 7 to Drupal 11

Humanitarian Outcomes

A research site with a global database of aid organizations, moved with the core Migrate API and finished before the Drupal 7 deadline. Patches for several contributed modules went back to drupal.org. Read the case study

Drupal 9.5 to Drupal 10

Aid Worker Security Database

CKEditor 5, the Claro admin theme and custom JavaScript moved to the Once library, on a database used by governments, NGOs and researchers. Read the case study

Drupal 11

itech4web.com

Our own site runs on Drupal 11 and gets current core releases.

Strapi and Nuxt to Drupal 11

bondarenkopsy.life

The website of a private practice psychologist. We first built it on Strapi with a Nuxt front end, then moved it to Drupal 11, where it runs today, and we keep supporting it.

WordPress to Drupal

Crowdfunding platform

A platform that had outgrown WordPress and its crowdfunding plugin. We moved more than 10,000 users and over 3,000 projects, with their contributions data, to Drupal with Drupal Commerce. Read the case study

Custom CMS to Drupal

Investment research portal

A US consultancy's subscription research site. We migrated more than 20,000 content items with their images and meta information, and over 1,000 users, then built a full-text document search. Read the case study

JSON data to Drupal

Luxury hotel booking site

Over 2,000 pages with images and meta information migrated to Drupal, and every page, the home page included, made editable by the client's team. Read the case study

SaaS API to Drupal

Recruiting platform

Candidate records pulled from an applicant tracking system's REST API into Drupal through a custom migration source plugin, then kept in sync with a graph database. Read the case study

"We give them a 10/10 on everything they have done."

Meriah-Jo Breckenridge, Digital Development Manager, Humanitarian Outcomes. Review on Clutch

Drupal credentials

Official Drupal services provider
Drupal Association member
Acquia-certified developers
Open-source contributor on drupal.org
Pricing

A quote after a free review

Every site is built differently, so we quote after we have seen yours. The quote lists the price, the timeline and the scope.

Upgrade or migration review

Free

We check the version, modules, custom code, content, integrations and hosting, and send a written list of what needs work.

Drupal 10 to Drupal 11

Fixed quote after review

For sites that should be on Drupal 11 by December 9, 2026.

Drupal 7, 8 or 9 upgrade, or a migration

Quote after review

Priced by the size of the site, the content to migrate, the platforms involved and how much custom work it has.

Support after launch

Updates, security fixes and help when you need it, with a monthly hours statement.

Payment by phases.

FAQ

Upgrade and migration questions

When does Drupal 10 reach end of life?

On December 9, 2026. Drupal.org will make no new Drupal 10 releases after that date, which means no more security fixes for Drupal 10 core. Drupal 12 is planned for the same week. Drupal 11 stays supported, and drupal.org has not published its end date yet.

What happens if we stay on Drupal 10 after December 9, 2026?

The site keeps working on the day support ends. Security releases for core stop, and contributed modules gradually drop Drupal 10 as their maintainers move on. Every vulnerability found after that date stays open on your site, so the risk grows each month. If you can't upgrade before the deadline, set a date and start the review now.

Should we wait for Drupal 12?

We recommend upgrading to Drupal 11 now. Drupal 12 will need PHP 8.5, and contributed modules usually need time to support a new major version. Since Drupal 8, a major upgrade updates the existing site instead of rebuilding it, so moving from 11 to 12 later is a much smaller job than a Drupal 7 migration.

How long does a Drupal upgrade take?

It depends on your starting version and how much custom code the site has. A well-maintained Drupal 10 site is the quickest case. A Drupal 7 site is a rebuild with a content migration and takes the longest. You get a timeline with the quote after the free review.

What usually breaks during an upgrade?

Mostly custom code and modules. Custom modules and themes that call deprecated functions need updating, some contributed modules have no new release and need a replacement or a patch, and editor setups change from CKEditor 4 to CKEditor 5. On Drupal 7 sites the views, fields and theme are rebuilt. We list all of this in the review, so the quote already covers it.

What drives the cost of a Drupal upgrade?

Your starting version, the number of contributed and custom modules, custom theme work, the amount and structure of content to migrate, integrations with other systems such as a CRM, payments or search, and any design or feature changes you add to the project. You get a quote after the free review.

Will we lose content, URLs or search rankings?

We plan for all three, whether you upgrade or move to another platform or host. We migrate all content, keep your URLs or send the old ones to the new ones with 301 redirects, carry over page titles and meta descriptions, and compare the old and new sites before launch. After launch we check for broken links and crawl errors.

What is the process of a website migration?

First we review the current site and list every URL, content type and integration. Then we map the content to the new platform and plan a redirect for every address that changes. We run the migration on a copy as many times as needed, and your team checks the result on a staging address. At launch we run it once more to pick up recent content and switch over at a time you choose. After launch we check redirects, forms and crawl errors.

Can you move our site from WordPress or another CMS to Drupal?

Yes. We map your posts, pages, custom fields, users and media to a Drupal content structure and move them with Drupal's Migrate API. Data from a custom CMS, JSON files or another system's API can come in through a custom source plugin. We have moved a WordPress crowdfunding platform with more than 10,000 users and over 3,000 projects to Drupal.

Can you move our site to a new host without downtime?

We plan every host move so the site stays online. We set up the new server, copy the code, database and files, test the site there and switch DNS at a time you choose. For But Why Tho?, a US entertainment publication on WordPress that had a deadline from its old host, the move finished in time with zero downtime and no lost content, comments or media.

Our site is still on Drupal 7. What are our options?

Upgrade to Drupal 11, or keep the Drupal 7 site running on our care plan while you decide: we make fixes and keep it working, but the plan does not cover Drupal 7 security. A care plan buys time but adds nothing new, so most teams use it as a bridge to an upgrade.

Can you upgrade or move a site another developer built?

Yes. Many of our clients come to us after their previous developer left. We first make sure the code, hosting and accounts are in your name, then review the site and plan the upgrade or migration.

Get started

Get your upgrade or migration plan

Send us your site's address and the Drupal version it runs. We will review it for free, list what needs work and send a quote with the price, timeline and scope. Planning a move to Drupal or to a new host? Use the same form and tell us about the site.

Any Questions?
Dima Storozhuk, founder and CEO of iTech4Web
Dima Storozhuk
Founder & CEO