Drupal 7 Migration Services
Move your Drupal 7 website or portal without losing the content, workflows and search visibility it depends on. We assess the current site, then plan a suitable destination such as Payload CMS with Next.js or a bespoke Laravel or Python application.
What needs to survive a Drupal 7 move?
Drupal 7 reached end of life on 5 January 2025, according to the Drupal project. Before choosing a replacement, we inventory content types, fields, taxonomies, user roles, contributed modules, custom code, forms, integrations and URLs. A site may look simple on the surface while its editors depend on years of custom publishing rules. Drupal's end-of-life notice explains the support position.
What could it move to?
For a content-led website, Payload CMS with Next.js may provide a cleaner editing and presentation model. If the site also runs substantial business processes, we may separate the content system from a Laravel or Python application. Moving to a supported Drupal version can also be evaluated where retaining Drupal makes sense. We recommend the destination after inspecting the actual site, not because every Drupal 7 installation needs the same rewrite.
Three decisions that shape the scope
A useful migration plan makes these choices explicit before the implementation budget is fixed.
Content and editor experience
Map content types, revisions, permissions, media and publishing workflows before deciding what editors need in the replacement.
Custom features and integrations
Identify which module behaviour and bespoke code still matters, then scope equivalent features or deliberate improvements.
Search and launch continuity
Plan URL mapping, redirects, metadata, analytics, forms and a cutover that can be checked before the old site is retired.
How does the live system stay safe?
We can prepare the replacement while the existing site remains available, trial an export and import, and reconcile content counts and samples. The launch plan needs a freeze or synchronisation approach for late edits, plus checks of permissions, forms, links and search-critical URLs. We agree what happens if a launch check fails before moving production traffic.
From assessment to release
Each stage has a tangible decision point so you can review cost and risk as the work progresses.
Assess the existing site
Review code, modules, hosting, editors, integrations, URLs and security exposure.
Design the destination
Agree the content model, workflows, scope of bespoke features and platform choice.
Migrate and verify
Trial content and media migration; check routes, forms, roles and representative records.
Release and support
Test the new site with users, launch with monitoring and resolve post-launch issues.
Drupal 7 Migration questions
Official community support ended in January 2025. The urgency depends on your exposure, current controls, any third-party support and the cost of maintaining the site. An assessment gives you a defensible plan.
That is an option to evaluate. Scorchsoft's current new-build focus is Payload CMS and bespoke Laravel or Python applications, so we would compare a Drupal upgrade with these routes and recommend the best fit for your content and workflows.
No agency can guarantee rankings. We can map existing URLs, preserve relevant content and metadata, set redirects, test crawling and monitor the launch to reduce avoidable disruption.
Usually, yes. We plan how to carry over edits made during the build and agree the cutover window. Complex editorial workflows may need a staged transfer or short publishing freeze.
Need help building your ideas?
Tell us where you're headed and we'll come back with our thoughts, a realistic plan and a rough cost estimate. Scorchsoft is a UK-based team of app, portal and AI developers, working in-house from Birmingham's Jewellery Quarter.