We migrate your site from Drupal 7 or Drupal 10 to Drupal 11 in phases, with audit, testing and deployment without stopping your business.

Drupal 10 support ends on 9 December 2026. Drupal 7 reached end of life on 5 January 2025. If your platform still runs on either, it is time to decide. We help you choose the right path and move your site to Drupal 11 with a clear plan, in phases, without stopping your business.

Where are you now?

Every migration starts from a different place. These are the situations we see most often.

You are on Drupal 10 but still carry old custom modules.
You have not yet left Drupal 7 or Drupal 9.
Your provider cannot give you a clear route, cost or timeline.
The agency that built your site is gone and nobody really knows the code.

In every case the first step is the same. Understand what you have before deciding what to do.

How we work

We work in five phases. Each one ends with something you can review, so you always know where the project stands and what is left.

1. Audit

We review contributed and custom modules, the theme, patches, integrations, and PHP and database versions. We check what has a Drupal 11 replacement and what needs rewriting. You get a quote that states what we know and what we don't yet. If something can't be estimated, we say so.

2. Preparation and testing

We work on a copy in an isolated environment, while your live site keeps running. We update the code and test what your business depends on. Orders, translations, permissions and ERP or CRM connections.

3. Data migration, when needed

Moving from Drupal 10 to 11 rarely means moving content. Leaving Drupal 7 does. In that case we migrate content, users and files, taking care of nested data, translations and external files. To move entities between environments we also use Easy Entity Migrate, the module we maintain on drupal.org.

4. Validation with the people who use the platform

Your team tests the new version with their real tasks. Editors, customer service, shop or back office. We collect what they find and fix it. Nothing goes live without their sign-off.

5. Deployment and review

We agree with you on the downtime window, how to handle data created during the switch, and how to roll back if something fails. After go-live we review the platform in production. We document the work so the knowledge stays in your organisation.

What you get in every project

An audit report listing modules, integrations and risks.
A phased quote that separates what is known from what still needs confirming.
A test environment where your team can review the new version.
A deployment plan with an agreed downtime window and rollback.
Technical documentation of the work, for your team or whoever comes next.

Upgrade or rethink

Not all migrations are alike. Going from Drupal 10 to Drupal 11 follows a path the community has planned. It is an upgrade. Leaving Drupal 7 is a different job. The architecture, the theme and many modules change.

Sometimes the move is a good moment to rethink the platform. Drop what nobody uses, simplify integrations or rebuild whole parts. Other times the sensible choice is to upgrade and carry on. We tell you after the audit, not before.

If your platform is more than Drupal, or the problem goes beyond the version, see our legacy application modernisation and migrations service.

Drupal migration experience

We have moved Drupal platforms from old versions to current ones in projects of different sizes. Here are some published cases.

Labdoo. The initial brief was to migrate their platform from Drupal 7 to Drupal 10. During the analysis it became clear the platform needed rethinking. Read the Labdoo case.
Bodeboca. It started with a Drupal 6 core and several Drupal 8 subsystems. We have migrated it progressively to modern versions, with ERP and logistics integrations. Read the Bodeboca case.
FastBill. We have grown their corporate site into an editorial platform, including the move to Drupal 10. Read the FastBill case.
natiboo.es. Our own website, built from scratch on Drupal 11. See how we built it.

We also maintain the Easy Entity Migrate module on drupal.org. It exports and imports Drupal entities as JSON, including translations, Paragraphs and media.

Frequently asked questions

Will my site stop working on 9 December 2026?

No. It will keep running. What it loses is Drupal 10 support and security patches. Every month without upgrading adds risk.

How much does a Drupal 11 migration cost?

It depends on custom modules, integrations and data. That is why we start with an audit. It gives you a quote that separates what we know from what we don't yet.

I'm on Drupal 7. What does that involve?

It is a migration, not an upgrade. The architecture, the theme and many modules change, and the data has to be moved. We cover it in detail in our article on migrating from Drupal 7 to Drupal 11 (in Spanish).