1Footer documentation
Released migration workflows and remaining coverage
See which migration workflows are released, what has been verified and where broader native coverage is still unfinished.
Last reviewed
A released adapter still needs a verified website
1Footer owns detection, repair, publication checks and ongoing scheduling. The released code now includes more than Next.js and TanStack on Vercel: additional framework installers and native Netlify, WordPress, HubSpot and Shopify workflows are included.
This is not a claim that every migration works across the full matrix. Compiler fixtures, provider simulations, saved access and a successful build each prove a different part of the system. Real connected migrations, public delivery, navigation, pauses and recovery still need validation for each platform.
Server and prerendered frameworks
Vercel native paths cover Next.js App Router, TanStack Start, Astro, SvelteKit, Nuxt and supported Node framework-mode Remix / React Router projects. The appropriate server, build or response adapter puts the footer HTML into the document.
Framework and runtime matter together. A client-only SPA, unsupported edge runtime or dynamic configuration is not automatically covered by a server installer. The React SDK and eligible Cloudflare delivery offer other paths, with their own publishing and targeting requirements.
Native hosts and CMS platforms
Released native workflows include Netlify draft builds and recovery, WordPress plugin control and supported hosting recovery, HubSpot template publishing, and Shopify theme transactions. They use the account and installation connected to the selected website.
Remaining coverage includes original-installation retirement across rebuild histories, replacement hosts or CMS instances, legacy templates, shared installations, restrictive provider permissions and actual connected migration receipts. Wix end-to-end native publishing is still unfinished.
A current public example: DR Studio
The public drstud.io footer was checked on 3 November 2026 against its current 1Footer publication. Its initial HTML contained the current 32 links and matching footer CSS. This is public HTTP evidence for that website at that time.
It does not establish browser navigation, every future publication or migration coverage on another platform. A later deployment or publication needs a new check.
What counts as a completed migration
A needs-attention result is not successful repair. The full cross-platform automation goal remains open until its supported scope is implemented and verified.
- The destination identity and connected publishing access match the website.
- The actual public response matches the current footer publication.
- Included and excluded routes, navigation and pause/resume behave correctly.
- Unrelated site content and later edits remain intact.
- Failed or uncertain provider operations are reconciled before another write.
- Any old-installation cleanup is reported separately from destination success.