Book an inspectionInspection
Drupal
HTMLAstroVite
Drupal theme output → rebuild reference

Keep your Drupal front end
while you rebuild the backend.

Capture public theme markup, page routes and available assets. Use the project and dependency report to plan replacement of Drupal AJAX, forms and module-backed behavior.

Free · no account · nothing changes on your live site

Use a public page or node URL reachable without a login. Capture a representative page for each layout you need to preserve.

What comes with you

Your Drupal front end

  • Rendered theme markup

    Public HTML and available theme CSS, fonts, images and scripts.

  • Published page routes

    Captured pages with local links and an original-to-output route map.

  • Drupal dependency signals

    A report of detected Drupal settings/AJAX signals, forms, scripts and embedded content for review.

Plan the rest of the move

Replacements to build

  • Content types and Views

    The HTML shows published results. Field schemas, Views definitions and content relationships are not recovered.

  • Form API and modules

    Review Drupal AJAX and module-backed interactions and replace the endpoints the front end expects.

  • Accounts and permissions

    User data, access rules and backend code require a separate migration from your Drupal instance.

Built for the move

Your Drupal move,
one step at a time.

  1. Capture representative layouts.

    Choose a public landing page or node page and include a small linked-page sample.

  2. Review the theme and AJAX dependencies.

    Run the project and inspect the downloaded assets and detected services. Compare every important interaction with the original.

  3. Plan the structured-content migration.

    Move content types, relationships, Views behavior and permissions separately, using the front-end capture as your design reference.

Questions,
answered.

Can't find what you need? You'll get an answer from an engineer within a day.

Talk to us
Does this migrate Drupal content types or Views?

No. It captures the public markup those systems produce. Structured content, Views configuration and relationships need to be migrated from the Drupal instance separately.

What happens to Drupal AJAX and behaviors?

Available script files can be copied and detected Drupal runtime signals appear in the report. Endpoints and module behavior still need to be reviewed and rebuilt.

Will I get the original PHP code, CMS database or a React rewrite?

You get the public front-end HTML, downloaded assets and a runnable project structure. PHP source, database content, user accounts and CMS workflows cannot be recovered from a public URL. Astro and Vite outputs retain editable HTML; they are not generated component rewrites.

Can the exported project work without the original hosting?

Downloaded assets and copied pages can be served locally. CSS imports, fonts and background images are followed and localized when available. Missing assets remain remote, while forms, embedded services and runtime scripts may still depend on the old host. The report identifies detected dependencies so you can rebuild them.

How much can I export free?

Choose one, three or five linked public pages. Each project is capped at 100 asset attempts, 5 MB per asset, 2 MB per page and 25 MB total fetched data. Query-based pages are kept distinct. Pages and assets beyond the caps are listed in the report. No account or card required; request limits apply.

Explore website to code export →