Modernise in Drupal
Keep Drupal where its content and workflow strengths are still needed.
A useful estimate needs more than a page count. Colabs maps the content, modules, integrations, editorial work and accessibility needs that affect a Drupal migration, then recommends a route and scope.
Older Drupal sites often contain content types, views and modules that outlived their original purpose. Moving all of them increases cost and carries old problems into the new site.
We separate essential content and workflows from items that can be simplified, archived or removed. That gives the estimate a defensible scope.
The Drupal 7 risk checker helps you separate immediate risk from migration planning by looking at updates, hosting, custom code, data and critical workflows.
Use it before scoping a migration if the current site still needs to stay online for a while.
Use the Drupal 7 risk checkerDrupal remains a strong fit for complex structured content, editorial permissions, multilingual workflows and integrations. A lighter CMS or static website may suit a site that now mainly publishes stable information.
We compare the operational tradeoffs with the team that will own the next site. Familiarity and support capacity count alongside features.
Keep Drupal where its content and workflow strengths are still needed.
Reduce ongoing complexity for a smaller publishing model.
Split the work when dependencies, risk or budget require it.
Address urgent issues while the replacement is scoped.
Keep the current site stable while migration work is prepared.
View Drupal maintenanceStabilise Drupal 7 and make the replacement decision.
View Drupal 7 supportImprove or simplify an existing site before committing to a rebuild.
View existing website supportConsider a static site when the content no longer needs Drupal.
View CMS-free websitesSend the website URL, Drupal version and what you already know about the desired outcome. We will identify the information needed to scope the migration and prepare an estimate.
Request an estimate