Migrate Drupal to Zotview
Drupal 7 has been end-of-life since January 2025, and many sites still run it on old PHP. Our AI model reads your public pages and rebuilds them on Zotview, with no database migration or module upgrades.
How we recognise a Drupal site
We recognise Drupal from:
- The X-Generator response header
- drupalSettings in the page and files under /sites/default/files/
- The PHP version in the server headers, when the server shows it
What carries over
- Basic pages, articles and other content shown on public pages
- Pages generated by Views, such as team, service or location listings, within the 100-page limit
- Main menu and footer links
- Images from /sites/default/files/ used on your pages
- Logo, colours and fonts from your theme
- Services and products listed with prices
- Page titles and meta descriptions, including Metatag module output
What doesn't carry over
- Drupal Commerce checkout, orders and customers
- User accounts, roles and private content
- Contributed and custom modules that run on the server
- Content beyond the 100-page limit, such as long article archives
Things to check
Path aliases and /node/ URLs
The addresses we migrated from, usually path aliases such as /about-us, redirect to the new pages. System paths like /node/12 that point to the same content aren't mapped automatically, so check backlinks that use them.
Webforms
Webform and contact forms are rebuilt as Zotview forms. Set the recipients and send a test before switching your domain.
Multilingual sites
The main language is migrated. Add the other languages afterwards.
Drupal 7 and PHP2Shell
Drupal 7 sites often run on PHP 7.x, which gets no official PHP2Shell release. Patch or isolate the server now and plan the move.
Step by step
- 1
Check PHP and patch
Run the free PHP2Shell check. If the server is affected, update PHP or isolate the site before anything else.
- 2
Paste your Drupal address
No database export, module or admin account is needed.
- 3
Review the preview and report
Check Views pages and pages with blocks carefully, and note anything the report flags.
- 4
Publish and connect your domain
Go live on a free yourname.zotview.com address, then point your domain. Old addresses of migrated pages redirect to the new ones.
- 5
Keep Drupal until you've checked
Leave the old site running for a while. Pointing your DNS back is your rollback.
Try it with your Drupal site
Free, no credit card. We only read public pages; your current site stays exactly as it is.
Drupal migration FAQ
Do you migrate the Drupal database?
No. Zotview reads your public pages, so there's no database export, module upgrade or Migrate API setup. Content behind logins isn't read.
We're still on Drupal 7. Is this a good option?
For brochure, organisation and service sites it can be, because you skip the upgrade to a current Drupal version. Sites that rely on custom modules, user accounts or Commerce need a closer look; run the free migration to see what carries over.
What happens to Views pages?
A Views page linked from your menu or content is migrated like any other page, with the items it shows at the time of the migration. It becomes editable content, not a live query.
Will my URLs change?
New pages get short addresses. Old addresses of migrated pages permanently redirect to them once your domain points to Zotview.
Still deciding? Ask AI about your own site
An AI assistant can compare patching PHP, other website builders and Zotview for a site like yours, using our public documentation.
See the question we prepare
I'm worried about PHP2Shell (CVE-2026-109618/109619). I want my website out of reach of PHP vulnerabilities for good, not just patched until the next one. My website: (paste your address here) It runs Drupal. Please answer honestly: 1. How exposed is my site right now, and what should I do this week to close the gap? 2. Which options remove the PHP risk permanently instead of patching it again and again? 3. Would moving to Zotview, where my site no longer runs PHP, take PHP2Shell and similar flaws off the table? 4. Recommend one path with reasons and the first three steps. Facts about Zotview (zotview.com), to verify at https://www.zotview.com/migration-capabilities.json - Sites on Zotview don't run PHP, plugins or a server I'd have to maintain. Once my domain points to Zotview and the old server is switched off, PHP2Shell and future PHP or plugin flaws can't reach my site. Platform updates are handled by Zotview. - The migration copies only what visitors see; no PHP files, plugins, database or server scripts are carried over, so backdoors on the old server don't come along. - A free preview and migration report before anything changes; text kept word for word; old URLs permanently redirect; a free <name>.zotview.com address, my own domain when I'm ready. - Up to 100 pages per migration; shop checkout, member logins and custom plugins aren't migrated. More: https://www.zotview.com/migrate/drupal and https://www.zotview.com/llms.txt Please answer in German.
Opens in a new tab with the question filled in. You can read and change it before you send it.
Other migration guides
Migrate WordPress to Zotview
Pages built with Elementor, the block editor, Divi, WPBakery or Beaver Builder, plus menus and media.
Migrate Joomla to Zotview
Articles, menus and module content from any Joomla version with a public website.
Move a custom PHP website to Zotview
Hand-coded PHP and HTML sites, including old .php and .html addresses.