Migration without the hassle
Your site stays, the system underneath goes. Visitors see the same website — only faster, safer and without the updates, the login and the database that tug at your sleeve every month.
We take over your WordPress or Joomla site, rebuild it as clean, static HTML and keep your URLs and search rankings intact. Including the honest story about what you give up.
Six kinds of gain
No login page being hammered day and night, no database to inject into, no third-party plug-ins that turn out to have a vulnerability tomorrow. What is no longer there cannot be abused either — the biggest security benefit of this step.
A CMS rebuilds every page on every visit: running code, querying the database, working through the theme and plug-ins. After the conversion the page is already there and the server sends it straight out. That saves waiting time, and better Core Web Vitals count towards how well you are found.
No more dashboard you have to know your way around, no more notices that something needs updating again. If you want a change, you write to us in plain language telling us what should be different. Small text and image changes are usually handled within one working day.
No maintenance subscription for a system you barely use, no paid premium plug-ins, no security package on top. Static pages also call for lighter hosting. See also website without maintenance costs.
A CMS site ages from the inside out: at some point a plug-in is no longer compatible or a theme builder stops supporting it. HTML and CSS simply keep working. And because it is clean standard code, any web builder can pick it up — you are not tied to anyone.
Less computation per page view means less energy on the server. What that saves at your visitor numbers is worked out in the comparison of CMS versus HTML.
Many people picture a migration as starting over. It is not. Your website consists of two things: the pages your visitor sees and the machinery that assembles them on every visit. When converting to bespoke HTML we keep the first and remove the second.
In practice that means: your texts, photos, design, menus and web addresses stay. The CMS, the database, the admin environment, the theme and the pile of plug-ins go. What remains are ready-made files the server only has to hand over on a visit — no code that has to run first.
Ideally: only that the site is faster. Static does not mean dull. Everything that happens in the browser still works — a drop-down menu, animations while scrolling, a dark and a light theme, a photo gallery, a map, a working contact form. “Static” refers to the server, not to the screen.
If you want to use the conversion to freshen up the site straight away, we take the design along in the same move. That saves a second project, and afterwards you are not stuck with whatever a theme or page builder happens to allow. What else is possible is set out on benefits of HTML without a CMS.
From A to go-live
Your current site stays online throughout the project. Only at the very last moment do we switch the domain over, outside office hours, so nobody finds a closed door.
Inventory: which pages, addresses and features are there, and what is actually being used?
Settling the design: carrying over your current look, or freshening it up right away.
Moving the content across and rebuilding it in clean HTML, including titles, texts and images.
Setting up forms, interactivity and redirects, so that no old address leads nowhere.
Testing for speed and accessibility, going live and keeping an eye on things for the first few weeks.
No dogma, just the honest differences you notice in practice. A broader comparison is on a CMS or not.
| Item | Your current CMS site | After converting to HTML |
|---|---|---|
| Publish it yourself | Always, through a login and an admin environment | Not yourself; you email or message the change and we handle it |
| Maintenance | Updating the core, the theme and the plug-ins, at a rhythm the system dictates | No update obligation; only the changes you want yourself |
| Attack surface | Login page, database and third-party code | Little more than hosting, email and the contact form |
| Speed | The page is assembled on every visit; caching softens that | The page is already there and is served straight away |
| Hosting | PHP and a database needed, so a heavier package | Lighter and cheaper; static files are enough |
| Costs after delivery | Hosting plus maintenance, licences and security | Hosting plus the changes you actually ask for |
| Web shop and members' area | Available off the shelf through extensions | Not straightforwardly; a CMS or a separate service still makes more sense here |
| Portability | Welded to a theme, a page builder and plug-ins | Standard HTML and CSS; any web builder can continue |
Security gains, concretely
A public /wp-admin or /administrator is hammered relentlessly with leaked passwords. After the conversion that address no longer exists, and neither does that entire category of attempts.
No database means no injection, and nothing an attacker can read out or quietly alter. It also removes a backup obligation: there is no live data collection left to lose.
Every extension was third-party code on your server. Once that pile is gone, so is the race between a newly disclosed vulnerability and your next update. More on that at website that cannot be hacked.
Unhackable does not exist: hosting, the domain name, email and the form remain real links in the chain. But they are small and manageable. We take care of HTTPS, security headers, server-side validation and spam protection on the hosting we manage ourselves.
A conversion is a trade-off, not free gain. The main thing you give up is the ability to publish yourself. No dashboard also means: no button to put a news item online yourself tonight. For most business sites that is no great loss — the content is largely fixed anyway — but it is the point on which the choice stands or falls.
We would rather say it beforehand than afterwards: if you recognise yourself in two or more of these points, a well-maintained CMS is probably the better choice, and we will simply say so.
This is the question that keeps clients awake most, and the answer is reassuring: Google indexes pages, not the system behind them. A search engine sees exactly the same thing on a CMS site as on an HTML site — an address with content on it. So what you have to protect is not the CMS, but the continuity of your addresses.
This is what we watch for in every conversion:
sitemap.xml goes to Google Search Console, so reindexing gets under way quickly.hreflangreferences.In practice things usually improve slightly rather than get worse afterwards, simply because the pages load faster. How we approach findability further is set out at web design that is easy to find in Google.
Almost every CMS site has a few parts that do more than show text. They do not disappear, they get a lighter solution. In the conversation beforehand we go through all of them:
The price depends mostly on the number of pages and on whether we carry over your existing design or renew it. You get a fixed price up front, so nothing is added along the way. For a typical business site we allow one to three weeks.
The return is in the years that follow: no maintenance subscription, no licences for premium plug-ins, no security package and a lighter hosting package. If you want to start out sharply, also take a look at having a website built cheaply and a budget website build.
We are no opponent of WordPress or Joomla — they are powerful if you really use them. Do you publish daily, does an editorial team work on the site, do you run a web shop with hundreds of products or do you have a closed members' area? Then the answer is not “no CMS”, but a well-secured and actively maintained CMS. We take care of that too, including updates, backups and monitoring.
If your current site has instead broken down or become infected, you do not have to choose straight away: we can first repair a WordPress site or fix a broken Joomla website, and then look calmly at whether converting to HTML is the better next step for you.
Yes, if that is what you want. We take your current design as the starting point and rebuild it in clean HTML and CSS. Your visitors see the same site, only faster. If you would rather use the conversion as a moment to freshen things up, we do that in the same move — which saves you a second project.
Not if the conversion is done properly. Google looks at addresses and content, not at the system behind them. We keep the existing URLs wherever we can and set up 301 redirects wherever an address changes, carry over titles, meta descriptions and structured data, and submit a new sitemap. Because the pages load faster afterwards, the Core Web Vitals usually improve rather than suffer.
For a typical business site of five to fifteen pages we allow one to three weeks, depending on how much content there is and how quickly we receive your texts and images. Your old site stays online throughout; only at go-live do we switch the domain over.
The contact form comes back as a dedicated, shielded script with server-side validation and spam protection — you will not notice a difference, attackers will. For a calendar, newsletter, search function, bookings or payments we pick a lightweight solution or an external service case by case. Only for a real web shop or a members' area do we usually advise keeping a CMS.
Not through a login — that is exactly what goes away. You send us changes by email or WhatsApp in plain language; small text and image changes are usually handled within one working day. If you publish weekly or more often yourself, that is the main drawback of this step, and we will tell you honestly whether a well-maintained CMS suits you better.
That depends on the number of pages and on whether we carry over your design or renew it. We quote a fixed price up front, so there are no surprises. After that, the recurring costs for CMS maintenance, updates and security plug-ins disappear; what remains is hosting and the changes you actually ask for.
Yes. Your texts, images and URL structure remain yours, and in clean HTML they are in fact easier to move than out of a locked-down CMS theme. So the choice is not irreversible: if your organisation grows into publishing daily, we will move the site to a CMS after all.
Send us the address of your current website. We will look at it free of charge, tell you honestly whether converting makes sense in your case and give you a fixed price.
A quick reply, always personal.