Not every Drupal site that needs work needs a migration. A site on an outdated minor version with maintained custom modules may just need a version upgrade. A site with accumulated technical debt may need remediation. A site with misaligned architecture may need modernization. Migration, meaning a move to a new platform or a fundamentally restructured version of the current one, is the right answer in specific circumstances. Knowing whether you're in one of them is what determines whether the project goes well.
When Migration Is the Right Answer
Your platform version is no longer supported. Drupal 7 reached end of life in January 2025. Drupal 8 hit it back in November 2021. Sites still on those versions aren't receiving security updates from the Drupal security team, which means documented vulnerabilities pile up with no fixes coming. If your site needs to stay secure, migrating to Drupal 10 or 11 isn't optional.
The architecture can't support what you need now. A Drupal site built on a data model that can't accommodate what your organization needs today, whether that's new content types, new integrations, new editorial workflows, or new scale, may need a migration rather than an extension. If the existing structure would have to be substantially rebuilt anyway, rebuilding on a current foundation is usually more efficient than stretching a structure that was never designed for the job.
The codebase isn't maintainable. Heavily customized Drupal 7 or 8 sites sometimes carry so much technical debt, undocumented custom modules, fragile dependency chains, patterns the community abandoned years ago, that maintaining the existing codebase costs more than rebuilding. A technical assessment tells you which side of that line you're on: a codebase that's salvageable with focused remediation, or one where the debt has compounded past the point of practicality.
Your needs have fundamentally changed. A site built for one job that now needs to do a very different one, say an informational site becoming a member portal, or a single-language site going multilingual at scale, usually needs the kind of structural rethinking that's easier as a migration than as a bolt-on.
When Migration Is Not the Right Answer
A site on a current, supported Drupal version with a sound codebase and technical debt in a few specific areas is more likely a remediation candidate than a migration candidate. Incremental cleanup, fixing the debt that's actively causing problems, updating dependencies systematically, improving documentation, is less disruptive and often faster than starting over.
A site that needs new features but has a sound foundation needs feature development, not migration. New functionality built on a working Drupal platform doesn't require a rebuild.
Telling the difference between a platform that needs attention and a platform that needs replacement is the job of a technical assessment, not a gut feeling.
What a Drupal Migration Actually Involves
Whether you're moving from Drupal 7 to Drupal 11, from a legacy custom build to Drupal CMS, or from another platform entirely, the process follows a consistent structure.
Content and configuration audit. What content exists, how it's structured, what integrations exist, what the custom modules do, and what the new platform needs to do that the current one doesn't. This audit produces the scope.
New platform architecture. Content model design, hosting and infrastructure selection, editorial workflow design, and integration architecture, all decided before build work begins, against the requirements the audit surfaced.
Content migration. Drupal's Migrate module provides a framework for moving content from a previous Drupal installation to a new one. Content types, fields, and taxonomy terms get mapped and migrated with varying degrees of automation depending on how much the data model changes. Anything that can't be migrated automatically gets recreated.
Custom module migration or replacement. Custom modules from an old Drupal version can't be installed on a new one as is. Each one gets assessed. Is it still needed? Does a contributed module now handle the same job? Or does it need a rebuild for the new architecture?
Theme development. The old theme doesn't migrate. A new one gets built for the current version, reflecting your current design and the current theme system.
Testing and launch. The full site gets tested against a defined checklist before go-live. The launch itself is a DNS change pointing your domain at the new installation.
How Long It Takes
A migration from a well-maintained Drupal 9 or 10 site to Drupal 11, with a relatively clean codebase and modest customization, runs six to twelve weeks. A migration from a heavily customized Drupal 7 site with significant custom modules and a lot of content runs three to six months. The audit produces the real estimate for your specific situation.
How Cool Fire Inc Approaches Drupal Migrations
Cool Fire Inc has managed Drupal platform migrations and modernization projects since 2005, including plenty of Drupal 7 rescues. Every project starts with a technical assessment that determines whether migration is even the right approach, and produces a realistic scope before you commit to anything. If you're trying to figure out where your site falls, book a free migration evaluation call and we'll help you sort it out.
Frequently Asked Questions
How do I know if my Drupal site needs a migration or just an upgrade?
A version upgrade updates the platform version without substantially changing the architecture or content model. A migration restructures the platform, new content model, new theme, potentially new hosting, alongside the version change. If your current codebase is maintainable and the architecture supports what you need, an upgrade is usually the right path. If either isn't true, migration is likely more practical.
How much does a Drupal migration cost?
It depends on your current platform's complexity and what the new one needs to do. A straightforward migration from a well-maintained recent Drupal version can run $15,000 to $40,000. A complex migration from a heavily customized Drupal 7 site with significant custom modules and a lot of content is a larger project. A technical assessment produces a specific number.
What happens to my content during a Drupal migration?
Content moves over using Drupal's Migrate module or custom migration scripts, depending on how much the data model changes. Structured content like nodes, taxonomy terms, media, and users migrates with high fidelity when the destination content model is designed to receive it. Anything that can't migrate automatically gets recreated.
Will my site go down during a Drupal migration?
No. The new site gets built and fully tested before the domain is pointed at it. Go-live is a DNS change that typically propagates within 24 hours. There's no required downtime.
What is the difference between a Drupal migration and a Drupal upgrade?
An upgrade updates Drupal core and contributed modules on your existing installation. A migration builds a fresh installation on the current Drupal version and moves your content, configuration, and custom functionality into it. Most transitions from Drupal 9 or 10 to 11 are upgrades. Drupal 7 to current is effectively always a migration, because the architecture changed too much to upgrade in place.