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 sample · up to 5 linked public pages · HTML, Astro or Vite
Your Drupal site moves into source files you own.
Start with the public pages you need to keep and identify where the front end still expects Drupal. Content types, Views, permissions and module behavior need their own migration plan.
Public HTML and available theme CSS, fonts, images and scripts.
Captured pages with local links and an original-to-output route map.
A report of detected Drupal settings/AJAX signals, forms, scripts and embedded content for review.
The HTML shows published results. Field schemas, Views definitions and content relationships are not recovered.
Review Drupal AJAX and module-backed interactions and replace the endpoints the front end expects.
User data, access rules and backend code require a separate migration from your Drupal instance.
Both start with an inspection and end with code you own. The difference is who writes it.
Build on your exported code with Claude Code or Codex. We review it, fix what breaks, move the data and users, and ship it. You keep the speed of AI; we take the risk out of launch.
We plan the move, rebuild the app, move data and users, and launch. You review each milestone and own the repository from the first commit.
Movers walk through the house before they quote. So do we. Then we do the heavy lifting, and the move takes weeks, not months.
1 Inspection. We list every page, data type, workflow and integration, flag what needs care, and send a plan and a quote. It costs $500.
2 Plan. We agree the stack, the hosting, the working model and the milestones. Nothing starts until the scope is signed.
3 Move. The app is rebuilt in code, by you with Claude and reviewed by us, or by our team. Data and users come across in rehearsed runs.
4 Launch. Redirects, DNS and a cutover window your users will not notice, with a rollback ready until it is stable.
5 Aftercare. Fixes, small features and handover notes, so your team or the next developer can carry on without us.
Can't find what you need? You'll get an answer from an engineer within a day.
Talk to usNo. It captures the public markup those systems produce. Structured content, Views configuration and relationships need to be migrated from the Drupal instance separately.
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.