Old Drupal is already costing you
The bill hides in workarounds, emergency fixes and fear of touching the site.
We identify blocked tasks, unsupported modules, forgotten accounts and content that is hard to update.
The first decision is which functions belong to the business and which have become historical weight.
- Unsupported modules
- Difficult security updates
- Fragile editing
- Knowledge held by one person
Map the model before exporting
Drupal content lives with types, fields, taxonomies, files and relationships.
We count content, languages, media, roles, views and integrations. That map shows what can move automatically and what needs human review.
URLs still producing visits or enquiries are treated as assets, not technical waste.
- Content types and fields
- Taxonomies and relationships
- Files, users and permissions
- Aliases and redirects
Choose the right migration route
An upgrade chain and a clean rebuild carry different risks.
Drupal documents stepwise migrations across major versions. With heavy customisation or missing modules, a clean rebuild may be safer than a long upgrade chain.
We prove the route on a sample before moving the whole catalogue, exposing unknown dependencies early.
- Module audit and replacements
- Sample migration
- Rejected-content report
- Timed cutover and rollback
Check what search engines can reach
The migration ends when visitors and crawlers consistently land in the right place.
We submit sitemaps, verify redirects and monitor both old and new properties. Temporary movement can happen; persistent errors need repair.
Each language keeps a clear URL and explicit internal links. That supports classic search and AI answers alike.
- Direct 301 redirects
- Consistent canonicals
- Distinct URLs per language
- Google, Bing and AI monitoring
Before launch
Leave Drupal 7 without guessing
- Module inventory
- Complete export retained
- Sample migration compared
- Historic URLs redirected
- Permissions and forms tested
Official sources