Planning a Drupal Migration

Planning a Drupal Migration: Upgrading from Older Drupal Versions to Current Releases

Drupal websites evolve over years. At some point, the question arises whether a simple update is sufficient or if a major migration is necessary. Particularly with very old Drupal versions, heavily customized themes, obsolete modules, or grown content structures, a migration should be carefully planned.

This article explains the difference between update, upgrade, and migration, and shows you how to structure the transition to a current Drupal version.

Update, Upgrade, or Migration?

The terms are often mixed up, but they do not mean the same thing.

Why Migrations Become Necessary

• The old Drupal version no longer receives regular support.
• Modules are obsolete or incompatible.
• The theme is technically outdated.
• The PHP version or hosting environment needs to be modernized.
• The website structure has grown organically and needs to be cleaned up.
• Performance, security, or editorial workflows need improvement.

A migration is also an opportunity to clean up old content, duplicate categories, unnecessary modules, and poor structures.

Conducting an Inventory

Before any migration, a technical and editorial analysis should take place. Check:

• Drupal version and PHP version,
• installed modules and their status,
• active themes and custom adjustments,
• content types and fields,
• taxonomies and menus,
• user roles and permissions,
• forms and integrations,
• SEO-relevant URLs and redirects,
• media and downloads.

Test Environment Instead of Live Experiments

A migration should never be attempted directly on the live website. First, create a full backup and set up a test or staging environment. There, the migration, theme adjustments, module changes, and database updates can be tested risk-free.

A good test environment should be as close as possible to the subsequent live environment: the same PHP version, a comparable database, the same domain structure, or at least clean test URLs.

Checking Modules and Themes

Not every old module is available or necessary in current Drupal versions. Some features are now included in the core, while other modules have been replaced or discontinued. Check for each module:

• Is the feature still required?
• Is there a compatible version?
• Is there a better alternative?
• Are there dependencies on other modules?
• Can the feature be replaced by Drupal Core?

Themes also often need to be rebuilt or heavily adapted. Simply continuing to use an old theme is rarely sensible.

Protecting SEO During Migrations

Migrations can jeopardize rankings if URLs, metadata, and internal links are not cleanly preserved. Therefore, create a list of important URLs before the migration and plan redirects.

• Record important old URLs.
• Define the new URL structure.
• Set up 301 redirects.
• Transfer or improve meta titles and descriptions.
• Update the sitemap.
• Check for 404 errors after going live.

When is a Fresh Rebuild Better?

With very old, heavily modified, or poorly maintained websites, a complete fresh rebuild is sometimes more efficient than a complex migration. This is especially true if content types are illogical, modules are outdated, themes are incompatible, or content is of poor quality.

A fresh rebuild can be useful if:

• only a small amount of content needs to be transferred,
• the design is being renewed anyway,
• the information architecture needs to be replanned from scratch,
• old modules have no future,
• the SEO structure needs to be heavily improved.

Hosting and Technical Foundation

A current Drupal version requires a compatible PHP version, sufficient memory, clean file permissions, Composer support, and ideally SSH access. Before migrating, check whether your hosting package meets these requirements.

For complex migrations, staging environments, and larger Drupal projects, a VPS Cloud Server from CURIAWEB can be beneficial. For classic corporate websites, Swiss Web Hosting from CURIAWEB provides a solid foundation.

Migration Checklist

• Create a full backup.
• Document the current state.
• Check modules and themes.
• Analyze content and media.
• Secure SEO URLs.
• Set up a test environment.
• Perform and log the migration.
• Test forms, logins, menus, and search functionality.
• Set up redirects.
• Plan and post-audit the live launch.

FAQ

Can I simply update an old Drupal website with one click?
Usually not across major version jumps. A careful migration or a planned upgrade process is required.

What is more important: content or design?
Both are important. Technically, however, the migration often begins with the content structure, modules, and data model. The design is frequently rebuilt in parallel.

How do I prevent SEO losses?
Through a URL inventory, 301 redirects, preserving important metadata, an updated sitemap, and monitoring after going live.