Capture public template markup and available assets. Keep query-based page URLs separate and use the source project to plan a move away from Joomla extensions.
Free sample · up to 5 linked public pages · HTML, Astro or Vite
Your Joomla site moves into source files you own.
Preserve the published template output as a starting point. Older sites can use query strings to identify content, so the exporter keeps those pages distinct and records their new local paths.
Rendered HTML and discoverable design files from your published pages.
URLs with different query strings get separate files instead of being merged into one index page.
Original URLs mapped to local pages, plus detected forms, scripts and component endpoint dependencies.
The captured front end does not recover server-side template logic or override files.
Replace extension-backed forms, user flows and AJAX endpoints as needed; copied markup alone cannot implement them.
Move the content store separately and use the route map to prepare redirects from your existing URLs.
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 usThe exporter treats query strings as part of page identity and maps captured pages to distinct local files. The original-to-output mapping is included in routes.json.
No. Public output and available assets are captured. Extension PHP code, administrator settings and database tables need a separate migration.