Integration

Foundation CMS and WordPress

Most sites that move to Foundation CMS come from WordPress. The move carries the content across as records, every image as a library item referenced by id, and every old address as a redirect, so search rankings and old links survive the switch.

Overview

This integration connects Foundation CMS with WordPress, in one direction: off it. Foundation CMS is Swarm Labs' multi-tenant content management system on Cloudflare Workers. It holds a site's content and hands it to the site as whole, typed records, and every site runs as its own Worker with its own database and media bucket. WordPress stores pages and their layout together and points content at image addresses; Foundation CMS stores content as typed records and points at media by id.

Business Context and Core Use Case

A WordPress site that has grown for years usually carries a theme nobody wants to touch, a stack of plugins to keep updated, and a server to look after. Moving it is daunting mainly because of what might break: images, links and search rankings. A planned move to Foundation CMS treats each of those as part of the job.

The Applications Involved

WordPress (WordPress) is the source: its posts, pages, media and addresses.

Foundation CMS (Foundation CMS) is the destination: content types modelled on what the site actually holds, a media library, and a redirects list.

How the Integration Works

The site's content is mapped onto content types in Foundation CMS, so a case study becomes a case study with its own fields rather than a page full of shortcodes. Content and media are imported by script, images becoming library items that content refers to by id. Every old address that changes gets a 301 redirect in the Foundation CMS redirects list; one recent move carried 1,662 of them. The new front end is built in the site's own repository, and the domain is switched with a DNS change that can be reversed.

Immediate Operational Value

No plugins to patch and no server to maintain; the site runs as its own Worker. Editors get an admin that knows their content, and because media is referenced by id, future moves and redesigns do not break images.

Security, Access, and Governance

A large class of WordPress risk, from outdated plugins to an exposed admin login, simply goes away. The Foundation CMS staff plane signs in with passkeys only, and the platform had a full security audit in September 2026.

Summary

Moving from WordPress to Foundation CMS keeps the content, the images, the links and the rankings, and leaves the plugins and the server behind.

Frequently asked questions

Will we lose our search rankings?

Every changed address gets a 301 redirect to its new home, which carries rankings and old links across.

Do images survive the move?

Yes. They are imported into the media library and content refers to them by id, so they do not depend on old addresses.

Can we keep our plugins?

Foundation CMS has no plugins. What they did is either built into the platform, such as forms, redirects and search settings, or done in the site's own code.

Want Foundation CMS and WordPress
wired up for you?