Drupal migration Colabs

Drupal migration without rebuilding everything

A Drupal migration does not automatically need to become a large rebuild project. Sometimes you need to move to a newer Drupal version. Sometimes a lighter website or simpler content model is a better fit. Colabs helps organisations with older Drupal websites decide what should happen next: maintain, simplify, migrate or rebuild only the parts that still matter.

Discuss your Drupal migration See the migration approach
Practical migration

Do not start with “which platform should we move to?”

With a Drupal migration, it is tempting to immediately discuss the new technical solution. But the better first question is: what does this website still need to do today?

Many Drupal websites have grown over the years. Content types, modules, views, forms and integrations remain in place because they were needed at some point. Not everything needs to move to the next version.

A good migration starts by separating what is essential, what can be simplified and what is no longer needed.

What we look at during a Drupal migration

  • Which content and pages still matter
  • Which content types, fields and templates are still used
  • Which forms and workflows are essential
  • Which modules or integrations add risk or complexity
  • Whether the website still really needs Drupal
  • Which accessibility issues should be addressed during migration
  • Whether a phased migration is possible
  • Which parts need temporary maintenance
Platform choice

The next website does not always need to be Drupal again

Drupal is still a strong choice for complex websites with structured content, editorial roles, multilingual workflows and integrations.

But not every older Drupal site still needs that level of complexity. Some organisations mostly use Drupal for a limited set of pages, news items or service information. In that case, a lighter website with Astro, structured content or a simpler CMS can sometimes be a better fit.

Colabs helps you make that decision calmly, based on what the website and the team actually need.

Possible migration paths

Keep Drupal and modernise it

For websites where Drupal is still the right foundation.

Simplify to a lighter website

For websites that mainly inform and only change occasionally.

Migrate in phases

For organisations that want to spread risk and budget.

Maintain temporarily with a migration plan

For websites that need to keep working while the next step is prepared.

Not sure which Drupal migration path makes sense?

Send us the website and a short description of the situation. We can help you decide whether migration, simplification or temporary maintenance is the most sensible next step.

Discuss your Drupal migration