Discover public pages from site links and the sitemap.
Example: https://your-site.systeme.io
Forms, payments, member access, and automations need a separate integration. Next.js export is in development; HTML is available now.
What a systeme.io HTML export includes
FNJ captures the visitor-facing HTML of published systeme.io pages. That gives you files you can inspect and edit without recreating the visible layout from scratch. Funnel logic behind the pages is a separate service, not part of the static export.
How to convert a systeme.io site to HTML
- 01 / Paste a public URL
Use a published systeme.io page you own or are allowed to convert. A private project link cannot be captured.
- 02 / Choose the scope
Capture one page, or discover linked public pages and pages exposed in the site's sitemap. Review the capture report for omissions.
- 03 / Preview and export
Check the HTML preview, then edit, download or deploy the captured files according to your FNJ access.
What FNJ captures
FNJ saves public page markup and accessible styles, images and other assets. You can capture one page or let it discover linked public pages. Uncopied assets and external scripts may still load from the original service.
Before you publish
Convert a published funnel URL and check each step separately. Links to checkout or thank-you pages may still point to the original systeme.io site; update them only after you have replacement payment and email flows ready.
systeme.io migration checks
A static export captures public pages, not the builder account or its hosted workflows. Check these before directing visitors to the new host:
- Capture and open every public funnel step, including the thank-you page if it is accessible.
- Trace each CTA, form and checkout link to its actual destination; static HTML does not recreate the funnel backend.
- Test contact capture, payment and follow-up emails with your replacement services before switching traffic.
Keep your pages findable after the move
Keep important URLs and page titles where possible. If a path changes, redirect its old URL to the matching new page. Review canonical URLs and your sitemap on the final domain, then check indexing and crawl errors in Search Console. The export cannot guarantee that a search ranking will stay the same.
Follow the edit and deployment guide →systeme.io to HTML: export and hosting FAQ
- Does the HTML export include my email automations?
- No. Sequences, contacts and automation rules live behind systeme.io and are not present in public page HTML.
- Can I host the funnel pages elsewhere?
- Yes, as static pages. Reconnect forms, payments and member access first, then test the full journey on the new host.
- Does exporting a systeme.io funnel move my contacts?
- No. Contacts, automation rules, email sequences, payments and membership records are not in public page HTML. Migrate those through the relevant services separately.
- Can I edit the systeme.io HTML and CSS after downloading?
- Yes. The captured HTML, CSS and accessible assets are editable files. Work in your code editor or use supported FNJ MCP tools with a connected agent. The export is a snapshot; changes made later in systeme.io do not automatically sync.
- Can I host the systeme.io HTML export on Cloudflare?
- You can deploy the static files to your own Cloudflare account or another compatible static host. Preview every page and reconnect hosted forms, payments and other services first. A GitHub repository can hold the source files; pushing code is separate from configuring its hosting.
- Is the systeme.io converter free or does it need an account?
- Converting requires a signed-in FNJ account and the access shown in current FNJ pricing. You can read this guide without signing in. Check the pricing page for current purchase terms; no builder subscription or private account access is used to fetch public pages.
Need the next step? Connect your agent through MCP, copy a site editing prompt, or check current FNJ pricing.
Where to take your systeme.io HTML
Host your systeme.io HTML export on Cloudflare
Deploy systeme.io HTML to your own Cloudflare Pages account. Review the captured pages, upload assets, test dependencies and connect your domain.
Follow the workflow →Export your systeme.io HTML code to GitHub
Put your systeme.io HTML export in your own GitHub repository. Choose the right files, review the fnj-export branch and plan updates and hosting.
Follow the workflow →Make your systeme.io export work for you
Practical guides for editing the captured HTML, reconnecting services and checking the result before launch.
Edit with MCP →
Connect an agent to FNJ MCP, inspect the correct route, change content and review the draft before publishing.
Reconnect forms →
Audit form actions, connect your own submission service and verify delivery, validation and error feedback after moving hosts.
CMS & content →
Separate captured article pages from the original CMS, inventory content and choose a tested publishing workflow for future updates.
URLs & SEO →
Map old and new routes, check canonical tags and metadata, test redirects and review indexability on the final domain.
Mobile layout →
Compare narrow and wide previews, fix overflow and navigation, and verify touch, keyboard and reduced-motion behavior.
Images & fonts →
Find failed asset requests, correct relative paths, inspect external dependencies and preserve typography on the new host.
Export troubleshooting →
Separate URL access errors, capture limits, missing content and deployment problems using a small reproducible conversion.
Explore related converters