Migrations and upgrades

We have experience in migration services, from Drupal 7 or Drupal 9 to the Drupal 10 version, migrating contents, functionalities, modules and SEO ranking.

Start a Drupal project

An upgrade is a migration with a deadline

Moving from Drupal 7 or Drupal 9 to Drupal 10, and on to Drupal 11, is not a version bump. Contributed modules retire, APIs change, and the content model often needs to be said again in the new system. The useful question is which behaviour must survive, which URL must keep its place, and which custom code should be retired instead of ported.

GeoNovation starts with that map. Core and contributed projects first. Custom modules only where the organisation's rules are real. Content, files, users, and translations move through Drupal's Migrate API so the import can be run again after the first rehearsal, not invented on the night of the cutover.

What has to arrive intact

Search visibility is part of the migration. Paths, redirects, and the metadata that described the old URLs are planned with the content, so a ranking is not treated as something to rebuild from zero after launch. Multilingual sites move each language with its source, not as a copy pasted into a second tree.

Editors should recognise the work. A migration that looks complete in the database and broken in the editorial interface is not finished. We check the content types, the permissions, and the screens people use, then run the import again until the difference is understood.

  • A written map of modules: keep, replace with a contributed project, or rewrite.
  • Content, files, users, and translations imported through Migrate, and re-runnable.
  • URLs, redirects, and on-page metadata carried across so existing visibility is not discarded.
  • A rehearsed cutover, with the old site still the reference until the new one is accepted.

After the new platform is live

The point of the upgrade is a platform on a supported major version, with configuration that can be deployed and a codebase someone else can read. We document what was dropped and why, and we stay for the first cycle of updates if you want the same squad on support.

This work sits inside Drupal Development. Start a Drupal project — tell us the organisation, the platform, and the constraint.

More under Drupal Development