01
Map the funnel before exporting
Write down the landing page, opt-in page, checkout destination and confirmation page. Open each URL as a visitor. A page behind a login, payment or private link cannot be assumed to appear in a public site capture.
Use page scope when you need a specific funnel step. Use site scope for linked public pages, then compare FNJ's report with your funnel map. Capture missing public steps separately rather than treating one successful homepage as a complete funnel migration.
02
Reconnect the services behind the page
Inspect every button destination and form action. Exporting the layout does not create a contacts database, email sequence, payment gateway or member access check. Choose the services that will handle each of those jobs.
Update links only when their replacement destinations are ready. Preserve a working payment flow during the transition, and make sure a confirmation URL cannot be used as proof of a completed purchase.
03
Test a real visitor journey
On a temporary deployment, submit a test opt-in and confirm it reaches the intended system. Follow the purchase flow using your provider's test facilities, then check confirmation messaging, membership access and follow-up email behavior.
Review campaign parameters and analytics events at every step. A static HTML page can display the original design while still sending people to old URLs; verify the actual destinations before switching ads or your domain.
Edit, deploy and protect your search URLs
Keep the downloaded HTML, CSS and assets together. Store a copy in your own GitHub repository to track changes; a repository is source storage, so configuring a deployment is a separate step. You can publish static files to your own Cloudflare account or another compatible static host.
For changes through an AI agent, connect it to FNJ MCP and give it the intended site and a specific task. Review the draft and its preview before publishing. Use the agent prompt library for content, links and CMS tasks, and the deployment guide for the next steps.
Keep existing page paths when practical. Map changed URLs to their closest replacements with permanent redirects. Check titles, descriptions, canonical URLs and internal links on the final domain, then submit its sitemap in Search Console. These checks help search engines find the replacement pages; they do not guarantee unchanged rankings.
Google Search Central: moving a site with URL changesYour systeme.io launch checklist
- 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.
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.