Aller au contenu

26 mai 2026

Migrating from WordPress to a pre-generated site: what actually changes

No more extension updates, pages that appear instantly, minimal hosting: what a migration changes day to day, how it is carried out, and when not to do it.

WordPress powers more than 40% of the web, and it is a legitimate tool for many projects. But for a non-profit or small-business site — a few presentation pages, some news, a contact form — it carries disproportionate machinery: database, PHP, theme, extensions, all of it to be maintained without pause. Migrating to a pre-generated site — what is usually called a static site — removes that machinery: pages are built once, at the very moment you publish them, instead of being reassembled on every visit. Here is what changes, without the jargon.

What changes for your visitors

Speed, first. A pre-generated site is a collection of pages already built and served as they are: no database to query, no code to run on each visit. The measurable result: pages that appear in under a second, and Lighthouse scores close to 100 — a criterion Google uses for ranking.

Availability, next. No “Error establishing a database connection”, no traffic spike that floors the server: pages that are already prepared take thousands of simultaneous visits without flinching.

What changes for you

No more updates to apply. This is the deepest change. WordPress demands weekly updates (core, theme, extensions), each one able to break something. A pre-generated site simply has no extensions: nothing to patch, so nothing to break, so nothing to pay for.

Security by construction. Almost every WordPress hack comes through a vulnerable extension or an exposed admin account. A pre-generated site has neither facing the public: the attack surface shrinks to almost nothing.

Editing stays simple. This is the classic objection — “but with WordPress I can change my site myself”. With a modern editing interface (we use Keystatic), you edit your pages in a back office just as simple as WordPress, with one advantage on top: every change is kept in history, and anything can be undone in one click.

How a migration goes

  1. Inventory. We list the existing pages, articles, images and forms — and take the opportunity to prune (every site older than five years carries dead content).
  2. Content transfer. Content is converted into standard files (Markdown). Much of this can be automated; the special cases (galleries, tables) are handled by hand.
  3. Design and build. The site is rebuilt with its new look — or identically, if the current one suits you.
  4. Redirects. Every old address points to the new page (301 redirects): you lose neither your readers nor your search ranking.
  5. DNS switch. The new site takes the place of the old one, without interruption. The old WordPress stays as a safety net for a few weeks, then is retired.

For a site under ten pages, the whole operation takes one to two weeks.

When NOT to migrate

Let us be honest: if your site rests on heavy dynamic features — a complex online shop, an active forum, a very specific members area — a pre-generated site alone will not be enough. Those needs call for a web application (that is our second offer), or justify staying on your current tool, properly managed.


Have a tired WordPress site? We offer an audit of what you have, with written recommendations — get in touch.

wordpressmigrationstatic sitesecurity

← All articles