Quick answer: replatforming means moving a website, web application or browser-based software system to a different platform, for example from Drupal 7 to Laravel, from custom PHP to WordPress, or from a traditional CMS to a headless or static setup. It’s worth considering when your current platform is unsupported, hard for your team to use, or holding back what your site needs to do. Done properly, your content and data come with you and your search rankings are protected with redirects. AI-assisted development has also made it far more affordable than it used to be.
Most websites and web applications aren’t replaced because they look dated. They’re replaced because the platform underneath them has become a problem: it’s out of support, every change costs too much, or the site or system has grown into something the original system was never designed for. Replatforming fixes the foundation rather than just the paintwork.
What is replatforming?
Replatforming is moving a website or web application from one technology to another. That might be one content management system to another, a CMS to a custom application, ageing custom code to a modern framework, a traditional website to a headless or static architecture, or a web application to a mobile app. Your content, users and data are migrated, and old URLs are redirected to their new homes so visitors and search engines can find them.
It applies just as much to portals, SaaS products, intranets and internal business systems that run in the browser as it does to websites. For these, the focus shifts from content to data, users, permissions and integrations, but the principle is the same: move onto a modern, supported platform without losing what you’ve built.
It’s different from a platform upgrade, which keeps you on the same platform and moves you to a newer version of it, such as Drupal 7 to Drupal 11 or Drupal 8 to Drupal 11. With Drupal 10 reaching end of life on 9 December 2026, the same week Drupal 12 is scheduled for release, many Drupal site owners are facing that choice right now. If your platform still suits you, upgrading is usually simpler. If it doesn’t, replatforming is often the better long-term investment.
Signs it’s time to change platforms
- Your platform is out of support. Drupal 6 and 7, old PHP versions and abandoned frameworks no longer get security fixes.
- Simple changes need a developer. Your team avoids updating the site because the editing experience is too complicated.
- Every new feature is a battle. Old code or a rigid platform makes changes slow and expensive.
- Few developers still work with it. Finding help is getting harder, and the original developer has moved on.
- Your site has become an application. Complex logins, workflows and data are being forced into a CMS that wasn’t built for them.
- You’re locked in. You’re tied to a proprietary system, a website builder or a single vendor.
Common replatforming paths
There’s no single right destination, and a good partner shouldn’t push you towards their favourite platform. The best choice depends on what your site or system needs to do, who uses it and where it’s heading. Almost any combination is possible. Some of the moves we see most often:
- Drupal to WordPress, when a simpler, easier-to-edit CMS is a better fit for a smaller team.
- WordPress or Drupal to Laravel, when the site behaves more like software than a website.
- Custom PHP or older frameworks such as CakePHP to Laravel, keeping your data and business rules while making the code secure and maintainable.
- Browser-based business systems, portals and SaaS products on ageing stacks to Laravel, keeping users, records, permissions and integrations intact.
- Website builders such as Wix or Squarespace to WordPress, when you need more control and want to own your site outright.
- A traditional CMS to headless or static, when speed, security and low running costs matter more than an all-in-one system.
- Web apps to mobile apps, extending a browser-based system into iOS and Android apps that share the same data and back end.
- A single iOS or Android app to both platforms, rebuilt in Flutter so one codebase runs on each.
For help weighing up the options, see hosted platforms vs custom CMS solutions and, if you’re on Drupal 7, your options after Drupal 7 end of life.
How to replatform without losing data or search rankings
The biggest risks in any migration are losing data and losing the traffic you’ve built. A careful replatform includes:
- A data migration plan covering users, records, files and integrations, tested before go-live.
- A content and URL inventory of every page that matters, including the ones that bring in search traffic and backlinks.
- A redirect map sending each old URL to its closest new page with a 301 redirect.
- Carrying across SEO details such as page titles, meta descriptions, headings and structured data.
- Testing on a staging site before launch, so problems are found before visitors see them.
- Watching Search Console after launch for errors, missing pages and changes in rankings.
How much does replatforming cost?
It depends on the size of the site, how much content and data needs to move, and how much custom functionality has to be rebuilt. A small brochure site is a very different job to a large portal with years of data and integrations.
The good news is that replatforming is far more affordable than it used to be. AI-assisted development means migrating content, rebuilding features and modernising old code takes a fraction of the time it once did. Projects that were once hard to justify are now often within reach. See how much a website costs for more on what drives price.
Frequently asked questions
How long does replatforming take?
A small site can move in a few weeks. Larger sites with lots of content, integrations or custom features typically take a few months.
Can we keep our existing design?
Often, yes. Many replatforms recreate the current design on the new platform, while others take the opportunity to refresh it. It’s your choice.
What happens to our content and users?
They’re migrated to the new platform. Content, media, users and other data can almost always be brought across, even from very old systems.
Should we upgrade instead?
If your platform still suits your site and your team, a platform upgrade is usually quicker and cheaper. If it’s unsupported, hard to use or limiting, replatforming is usually the better choice.
Thinking about a new platform?
Itomic has been building and looking after websites and web applications for Australian organisations since 2000, on WordPress, Drupal and Laravel. We’ll give you an honest recommendation on whether to upgrade or replatform your website or web application, and which platform suits it best. Explore our replatforming services or talk to us.
