If you ever wanted to move your website to a different developer, could you? Not in theory. Actually. That question matters more in 2026 than it has for years, and most business owners only find the answer when it is too late to change it.

A short history, and why it matters now

Years ago we built websites with custom backends. Every developer had their own way of doing it, and if you wanted to move to someone else, you usually started again from scratch. Then open source platforms arrived. By the mid 2000s, WordPress, Drupal and Joomla had changed the economics completely. It was cheaper and safer for a business to sit on a platform that thousands of other developers already knew how to work with.

For about fifteen years that was settled. Pick an open platform, own your site, move it when you want.

What changed in the last couple of years

Websites are being built differently now, even compared with 2024. A lot of developers have moved away from the open source model towards headless setups, static site generators, or their own in-house system.

There are real reasons for it. Those approaches can be fast and secure, and in the right hands they are excellent. A large publisher with its own development team can do very well out of a headless build. The problem is what happens when that same approach is sold to a local business with no developer on staff.

What portable actually means

People assume their website is portable because they can see it and they paid for it. Portability is really three separate things, and a site can pass one and fail another.

  • Your content. Can the words, images and pages be exported in a form someone else can use?
  • The site itself. Can another developer open it up and change a page, or would they have to rebuild it first?
  • The keys. Are the domain, the hosting and the licences in your name, or in theirs?

A custom-built static or headless site often passes the first and the third, and fails the second. Your content comes out fine. The site that displays it was written for one developer’s setup, and editing it means knowing that setup.

The test is not what your website is built with. It is what happens the day you want to leave.

Why we still build on WordPress

WordPress is not the newest thing on the shelf, and that is part of the point. It is reliable. It gives you the back end access most owners want, so you can log in and change your own text and photos. It scales from a five page site to a large one without the cost jumping every time you grow. And because so many developers know it, you are never stuck with one person.

If you decide to leave us, you take a WordPress site with you. Any competent WordPress developer in the country can pick it up on day one.

Quick tip

WordPress on its own is not a guarantee. A site packed with one builder’s private blocks, or held together with custom code nobody documented, can still be painful to hand over. Ask how it is built, not just what it is built on.

What we see around Cairns

We come across a lot of static sites around Cairns, built by all sorts of people. They usually look sharp. The owner is happy until the day they want a new page, or a price changed, or they simply want to work with someone else. That is when they find out the site is not something another developer can just open and edit.

These sites can be rebuilt, and AI tools have made that work faster than it used to be. But it still takes a developer who understands the framework it was written in, and a rebuild is still a rebuild. You are paying again for something you already bought.

None of this makes those builds wrong. It makes them a decision, and a decision you should get to make with your eyes open rather than discover two years later.

Ask before you sign

  • What platform is it built on, and is it open source?
  • Can I log in and edit my own text and photos?
  • If I move to another developer, what exactly do I get handed?
  • Whose name are the domain, hosting and licences in?
  • Would the next developer be able to edit it, or rebuild it?
  • Can you show me a site you have handed over to someone else?

The short version

WordPress is not the only good answer, and we are not against newer ways of building. We build on it because it keeps your options open. You get a site you can log into, a platform any developer can work with, and no bill waiting for you if you ever decide to go elsewhere. Plain and simple.