You do not have to move your site. A WordPress site is built to publish pages, and it is very good at that. What it is not built for is holding records about people who log in — bookings, client files, member accounts — and that is a separate thing that can live beside it, on your own domain, without touching a single page you have already written.
There is a specific point where this changes, and it is easy to recognise. Up to it, everybody who visits sees the same thing: your pages, your prices, your contact form. After it, different people are supposed to see different things — this client's documents, that member's history, only my own bookings.
That second job is an application. It needs to know who is asking before it answers, keep one person's records away from another's, and survive the day something goes wrong. A page does not need any of that, which is why the tool that serves your pages does not come with it.
The usual answer is to add a plugin, and for a while it works. What you have actually done is put personal data about your customers into the same database as your published pages, reachable by every other plugin on the site, updating on somebody else's schedule.
That is not a flaw in the plugin. It is what happens when you ask a publishing tool to also be the place customer records live: the blast radius of anything going wrong now includes both. The day you want to know exactly who can read those records and where their backups are, you are answering for the whole site, not for one feature.
It gets more expensive as it works better. The more the portal is used, the more of your business is inside it, and the harder it is to move later.
The arrangement that works is boring: your site stays exactly where it is, and the app lives on its own address — usually something like portal.yourdomain.com or app.yourdomain.com — linked from your menu like any other page.
To a visitor it is one business. Your pages, your design, your search rankings and your existing content are untouched, because nothing about them changed. What moved is the one part that needed a different set of guarantees: its own database, its own sign-in, its own backups.
It also means you can start small. One portal, one form, one member area — without a rebuild of anything that already works.
A database of its own, so customer records are not sitting next to your published content. A proper sign-in with roles, so the server checks who is asking on every request rather than hiding a menu item. Backups taken on a schedule and verified by actually restoring them, not an export somebody took once.
Keys and passwords held outside the code and handed to the app only while it runs, so they never reach the page a visitor downloads. Monitoring around the clock with a status page you can send people to. And the app and its backups in Europe by default, which is the answer your customers increasingly ask for before they sign anything.
This is the part that changed recently. Describing what you want to an AI tool and getting a working application back is now genuinely something a non-developer can do in an afternoon — a booking system, a client portal, an internal register.
What those tools do not give you is everything on the list above. They build the thing; they do not run it for real people. That gap is the whole reason softkiln exists, and it is the same gap whether you arrived from a WordPress site or from a blank page.
You bring the app — one you built, or one you described to an AI tool and got back. Softkiln gives it a database, a web address with the certificate renewed for you, a sign-in page with your own users and roles, encrypted backups it restores to check they work, and a scan on every release that blocks one leaking a password.
Your WordPress site carries on doing what it already does well. Nothing about it has to change, and nothing about it has to be migrated.
It is free for 15 days with no card, so you can have the portal standing before you decide anything.
No, and you should not. The site keeps publishing your pages exactly as it does now. Only the part that holds records about people who log in moves, and it moves to its own address on your own domain.
No. It runs beside the site rather than inside it, and that is the point: the app has its own database, its own sign-in and its own backups, so customer records are not in the same place as your published content.
Yes. On Pro the app and its status page sit on a subdomain of the domain your site already uses, with the certificate issued and renewed for you. Every app gets a softkiln.com address immediately in the meantime.
It usually comes out as an export from whatever is holding it today, and goes in as a one-off import. Do it as a rehearsal into a throwaway copy first — the same advice as any migration.
Not for the running of it. There is no server to choose, patch or size, no certificate to install and no backup script to write. If the app itself needs building, an AI tool will take you a long way, and softkiln runs what comes out.
Nothing for 15 days, and no card to start. After that it is $15 a month per app while it is still your own, and $49 once real people depend on it. Prices exclude VAT.