Platform lock-in and switching costs

Every platform is chosen once and left eventually, and the cost of leaving is rarely part of the decision that chose it. That is backwards, because switching cost predicts the platform’s real long-run price at least as reliably as its subscription fee does — a cheap platform that is expensive to leave has simply deferred its real cost to whichever year you outgrow it.

What “vendor lock-in” and switching costs actually mean here

Vendor lock-in is not a single thing. It is at least three separable costs, and platforms differ enormously in how much of each they impose: content portability (can your words and images leave cleanly), design portability (does the visual layer travel, or does it have to be rebuilt), and address portability (do your existing page URLs keep working, or does every one need a redirect). The same underlying dependence-on-a-vendor problem shows up in cloud software generally, not just website platforms — a business that has thought about switching costs for its accounting software or its booking system will recognise the pattern immediately.

Where each platform actually sits

WordPress is the most portable of the six by a wide margin, because the content lives in an open database format any competent developer can export and reshape. The exception is visual page-builder plugins, which store layout as that plugin’s own proprietary markup — genuinely owned, genuinely harder to move than plain content.

Shopify exports products, customers and orders as data, which is real and useful, but the checkout, the address structure and any app-held data do not travel. Moving off Shopify is a partial data migration plus a full rebuild of everything else.

Squarespace and Wix sit at the least portable end. Content export exists in a limited form on Squarespace and is minimal on Wix; the template and layout structure on both is proprietary and does not translate to another platform. Leaving either, after years of content, is closer to a full rebuild than a migration.

Webflow exports genuinely clean, semantic HTML and CSS on paid plans — a real, structural advantage over Wix and Squarespace — but the CMS content model, hosting and any custom interactions built on Webflow’s own logic system stay behind.

A custom build has effectively no platform lock-in by construction, because there was never a vendor platform underneath it. What it does have is a dependency on whoever built and understands the code, which is a different kind of lock-in — to a person or a team, rather than to a company’s software.

The one universal cost, whichever platform you leave

No platform exports customer account passwords, ever, on privacy and security grounds that apply industry-wide. Every migration that involves customer logins ends with a forced password reset communicated to the entire list. Plan that as the marketing and support event it becomes, on any platform, rather than as a technical footnote.

What this actually changes about the decision

It does not mean choose the most portable platform regardless of everything else — a business that will never seriously outgrow Wix has no practical use for WordPress’s superior portability and flexibility, and has paid a real cost in complexity to get it. Content stored in a genuinely open format is what makes that flexibility possible later; content stored in a vendor’s own proprietary format is what removes it. It means price the exit alongside the entry, particularly for a business expecting meaningful growth, because the platform that looks cheapest today is sometimes the one that will cost the most to leave in three years, and that cost lands on the business, not on the platform that caused it.

Why lock-in is worth pricing in at the start, not the end

A platform decision is frequently made against a first-year budget alone, with no consideration of what leaving would cost three or five years later once real content, traffic and search visibility have accumulated on top of it. The businesses most exposed to a nasty surprise are the ones that grew fastest on the least portable platform, because the amount of value at risk in a difficult migration scales directly with how successful the site has become in the meantime — the platform that looked like the easy, cheap choice at launch is sometimes the one carrying the largest deferred cost by the time it actually matters.

What a supplier should be able to state plainly

Before a build begins, a competent supplier should be able to describe, in plain terms, what content export actually looks like on the proposed platform and roughly what a future migration would involve — not because a migration is planned, but because a supplier who has never considered the question is a supplier who has not thought past the sale. A vague or dismissive answer to “what would it take to leave this platform later” is worth noticing for what it does not say.

Contract terms worth checking, briefly

Where a platform is used through a paid contract rather than a self-service signup, checking the contract itself for an explicit data-export clause and any exit notice period is worth doing before signing, not after a relationship has soured — a contract silent on export rights leaves a business relying entirely on the platform’s current, changeable policy rather than an enforceable commitment.

Where to go from here

Choosing a platform for your business works through the fuller decision this page’s fifth question belongs to. Where a migration is actually happening rather than being planned for, the mechanics of moving content and addresses without losing search visibility sit with the redesign and migration content this site is building next, not here. And what a genuine like-for-like exit actually costs to commission, once the decision is made, is priced on what drives the cost of a website.