Should Your Website Revamp Change Platforms?

Change website platform when the platform is the thing costing you: you cannot make a change without going back to whoever built the site, the feature the business now needs is something the platform will not do, or the bill keeps arriving while the site stays as it was. Any of those three and a move pays for itself. None of them, and a revamp on what you already have lands sooner for less.

That decision is usually settled in an afternoon. The planning goes into what the move bills you for afterwards, and it is never the design. It is the page addresses, the content that does not survive the export, and the person who has to learn a new editor.

Should you change website platform, or just revamp on it?

Put the complaint into one of two layers. The platform layer is who can change the site, what it is technically able to do, and what it costs to keep the lights on. The revamp layer is what the site says, how it looks and the order the pages sit in. A move only helps with the first layer, and three complaints sit squarely in it:

• You cannot edit it yourself. Every price change and every Raya opening-hours notice goes through a freelancer who may or may not reply this week. Who actually owns the website is worth settling before you spend anything on it.
• The platform will not do the thing you now need. A second language, FPX at checkout, a booking calendar tied to real availability, a CRM that has to receive the enquiry. If whoever maintains the site says it cannot be added, that is a platform problem.
• The cost keeps rising while the site stands still. Licences, add-ons and a retainer for changes you could make yourself: what a page builder costs after the build and a website becoming expensive to maintain are both the platform layer billing you monthly.

Everything else argues for staying. Dated design, weak copy, a homepage that buries the thing you actually sell — a new platform rewrites none of it. If visitors cannot find what they came for, the problem is usually the structure rather than the content, and structure is rebuilt on any platform at roughly the same price. So the question our revamp or full rebuild article keeps asking applies here too: what, specifically, is broken?

What does moving platform actually bill you for?

Three lines, and the design is not one of them.

The first is the addresses: if every page gets a new URL, every old URL needs a permanent redirect to whatever replaced it, and someone writes that mapping by hand. The second is the content the export leaves behind, which you rebuild page by page. The third is the time your staff lose while the new editor is unfamiliar, plus documenting it for the next person.

We are not going to attach a ringgit range to that, because the figure turns on a number you can count yourself before anyone quotes you. Open your sitemap, or ask for the page list, and count. A fifteen-page site with one blog is a different job from a two-hundred-page site with eight years of posts and three forms wired into a CRM.

The last row is the one people forget. A platform the business can actually use beats a platform with a longer feature list — the same argument we made about what you are paying a web agency for.

What survives the export, and what does not?

Read your current platform’s own export documentation before you agree a price, not after. The published lists are specific, and shorter than people expect.

Squarespace is the clearest example, because it writes the limits down. Its guidance on exporting your site content explains that the export is a WordPress-format .xml file, and that “Many features rely on our platform’s JavaScript and CSS, so some content doesn’t export.” What does not come across is listed outright: album, cover, index, info, calendar, portfolio and store pages; content in page-specific headers, footers and sidebars; dropdowns; audio, product and video blocks; drafts; style settings; custom CSS. And on a site with more than one blog: “Only one blog page exports.”

None of that makes a move wrong. It tells you what the second half of the project is: a shop, a portfolio and a second blog are pages a person rebuilds, and they belong in the quote. Treat the export as the start of a content audit, which raises the same questions as any revamp about what to keep from the old website and keeps the revamp timeline honest, because rebuilding forty pages by hand is weeks nobody costed.

Where a platform publishes no such list, ask for an export file before signing and open it. A file you can read is evidence; an assurance that everything transfers is not.

Will changing platform hurt your Google rankings?

Only if the addresses change and the redirects are wrong. Keeping the same paths on the new platform is the cheapest protection available, and most platforms allow it. Where they have to change, Google’s guidance on site moves with URL changes asks for a mapping from every current URL to its replacement, server-side permanent redirects, and patience: “for medium-sized websites, it can take a few weeks or more for Google to gradually start showing the new URLs instead of the old ones (and for larger sites, even longer).” It also warns against stacking redirects, advising a chain of “ideally no more than 3 and fewer than 5”.

Two consequences for a Malaysian SME. Pick a quiet month rather than the fortnight before a Raya campaign, because weeks of movement in your busiest season is a real cost. And keep the old URLs resolving: cancelling the old hosting the day after launch takes the redirects down with it, the failure our guide to moving a website without breaking it exists to prevent. More on the ranking side in how to redesign without losing SEO rankings.

Email dies quietly in a platform move. If the current platform also hosts your mail, enquiries stop arriving and nobody notices for days. Check the email and DNS side before launch day, not on it.

What should you do before committing to a platform move?

Four things, in this order, and all four are cheap:

• Count the URLs and list the pages. That number decides the quote.
• Download an export from the current platform, open it, and note what is missing.
• Write down every system that receives an enquiry today, the WhatsApp number included.
• Name whoever will update the site afterwards, and have them try the new editor before you buy it.

Then put the move and the redesign in one release. The addresses, the templates and the platform all change everywhere at once, which is the argument in our piece on revamping in stages or all at once; two rounds of disruption buys nothing. If the four answers show the platform is fine, write a revamp brief instead and spend the budget on the pages.

Where iRevamps fits

We do both: a revamp on the platform you have, and a move when the platform is the constraint. Either way the first conversation is the audit above, and the pre-launch checks are the same. To go through the count, the export and the redirect map with someone, that is our web development and design work.

Frequently asked questions

A platform move buys control and capability, and is worth it when either is missing. It cures nothing on a site that says the wrong things. Count your pages, open an export, and the answer usually arrives within a day.