FNJ / CMS & content
Maintain CMS content after exporting a website
Separate captured article pages from the original CMS, inventory content and choose a tested publishing workflow for future updates.
Start with the outcome
An explicit inventory of captured pages and a publishing plan for new content. Static article HTML can remain available even though the source collection database, filters, permissions and editor did not move.
Choose your original builder below. The task is shared, but the dependencies, URL structure and missing features to check depend on the platform. Each guide includes a reviewed platform note, a full procedure and a prompt you can adapt for your agent.
Choose your website builder
Framer / CMS & content
Maintain CMS content after exporting a website
Inventory Framer collection item paths before conversion. Captured articles can survive as static files without the Framer CMS editor or its future publishing pipeline. In FNJ, inspect whether an extracted collection actually has a publishing template before adding items; storage fields and a rendered item URL are different capabilities.
Read the guide →Webflow / CMS & content
Maintain CMS content after exporting a website
A captured Webflow collection item is an HTML page, not a transferred collection record with all field definitions and filters. Compare public CMS paths with your inventory and rebuild the future publishing workflow explicitly. Do not promise Webflow designer editing or automatic sync from later collection updates.
Read the guide →Gamma / CMS & content
Maintain CMS content after exporting a website
Gamma cards and linked public pages should be inventoried as captured content rather than assumed to be a CMS collection. If you need repeatable articles afterward, define a new content schema and page template. Keep presentation/deck data separate; FNJ does not import Gamma workspace records into that schema.
Read the guide →systeme.io / CMS & content
Maintain CMS content after exporting a website
Inventory public sales, content and confirmation steps separately from member-only course material. Public-page capture does not transfer contacts, course entitlements or email sequences. A new FNJ collection can organize public content, but it must not be treated as a replacement for member authentication or purchase records.
Read the guide →Carrd / CMS & content
Maintain CMS content after exporting a website
A one-page Carrd export may need only manually maintained cards or sections, rather than a full CMS. If you add a collection, choose how its records reach visible content: a listing section or separate cloned pages. Do not mistake section anchors for collection item routes.
Read the guide →Duda / CMS & content
Maintain CMS content after exporting a website
Separate public Duda content pages from dynamic data and account-managed widgets. Use the capture report to identify which pages exist, then plan new content in a supported static or CMS workflow. A blocked source route cannot be replaced by inventing a collection record with the same title.
Read the guide →Elementor / CMS & content
Maintain CMS content after exporting a website
Keep a separate WordPress database backup when records, users and plugin configuration matter. Captured posts are public pages, not a transferable WordPress admin. Decide whether future posts use static files or another CMS, and preserve article routes while verifying one new publishing example.
Read the guide →Squarespace / CMS & content
Maintain CMS content after exporting a website
List public blog articles and gallery pages; protected member content is not part of a public HTML export. Future Squarespace posts will not sync automatically. Choose how article listings and detail pages are maintained in the new workflow, and confirm that a draft item actually gets a reachable published route.
Read the guide →Strikingly / CMS & content
Maintain CMS content after exporting a website
Distinguish Strikingly sections from real public content pages and protected member material. Public HTML cannot transfer membership records or access rules. If you introduce a public content collection, verify its rendering and URLs separately from any service responsible for authenticating members.
Read the guide →Tilda / CMS & content
Maintain CMS content after exporting a website
Inventory public Tilda content and unlinked campaign pages separately. Static page capture does not recreate an editor-managed content collection or CRM. When adding a new FNJ publishing workflow, reuse a suitable page layout, define structured fields deliberately and test the rendered item route before publishing a larger set.
Read the guide →Weebly / CMS & content
Maintain CMS content after exporting a website
Inventory public Weebly blog or content pages with their exact paths. Keep any structured records through an authorized backup from the original service; the HTML bundle is not a Square or Weebly database export. A new collection needs a verified template or a separately maintained page workflow.
Read the guide →Wix / CMS & content
Maintain CMS content after exporting a website
Wix CMS, member records and booking data are not exported by capturing a public page. Inventory visible content and obtain authorized structured data separately when needed. Rebuild missing dynamic sections or choose a new CMS workflow; verify a real item page instead of treating a successful fetch as a collection migration.
Read the guide →What a completed task should demonstrate
- Captured item URLs match the content inventory.
- Collection storage and page publishing are distinguished.
- A new test page can be reached directly and from its listing.