How to avoid website vendor lock-in and keep a copy of your site you can use

By Ranjit Bhinge, founder of Blur Studio · Updated · 9 min read

Short answer: Website vendor lock-in means your site only works on one company's platform, so leaving means rebuilding it or paying whatever that company asks. You avoid it by choosing tools that give you the site's files, keeping your domain, content and accounts in your own name, and testing an export before you need it. As of November 2026, platforms differ a lot: Wix and Framer (two website builders) say they cannot export a working site, Webflow (a design-focused builder) exports code but not its CMS or forms, and Ploy's docs say source code export works on every plan, though code ownership wording is not clear, so ask in writing.

Ranjit Bhinge

You want to be sure that if a website company raises prices, changes its rules or disappears, your business can take its site somewhere else.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Lock-in is not one thing. It is a stack of small dependencies, and any one of them can trap you. The good news is you can test each layer in an afternoon. The rule I use: if you cannot rebuild the site from files you hold today, you are renting it.

This guide breaks lock-in into layers, shows what the major platforms say about export, gives a short exit test with pass and fail results, and lists questions to ask any vendor in writing. It also shows what Ploy, an AI platform that builds and hosts business websites and syncs its site code with GitHub, says about code and data, so you can weigh it on the same terms. Details change, so each platform section points you to the vendor's page.

This page may contain affiliate links from which Blur Studio earns commissions.

The six layers of lock-in

  1. The domain. The address people type. If a vendor or freelancer registered it in their name, they hold the key.
  2. The code. The files that make pages work. If you cannot get them, the site cannot run elsewhere.
  3. The content. Your words, images and product data. Often exportable in some form, even where code is not.
  4. The data and forms. Form entries, CMS items (blog posts and collection entries), customer lists and orders. These break most often.
  5. The hosting and accounts. The server, the analytics, Search Console and any logins. If one person holds them all, you depend on that person.
  6. The people. A developer or agency who is the only one who knows how it works.

This is the practical side of the ownership question covered in who owns your website and content. For apps, see avoiding lock-in with an app builder.

What each platform says about export

All rows come from each vendor's own page, read in November 2026. If a row says check, the vendor's page was not clear enough to state more.

PlatformWorking code you can host elsewhere?Notes from the vendor
WixNoWix says a site needs to be hosted and operated on Wix's servers. A domain from another company can be connected.
FramerNoFramer says it does not offer HTML export for self-hosting, because its performance features rely on its own backend. Help page updated 15 September 2026.
SquarespaceNo, partial content export onlyAn XML file for WordPress covering some page types, one blog, text and image blocks. Many page types, blocks and style settings are left out.
WebflowYes for static pages, on a paid Workspace planExport covers the site's code. Webflow says CMS content must be exported collection by collection and forms stop working. Exported code cannot be re-imported.
Lovable (AI tool that writes site and app code)YesIts docs say code is yours, synced to your own Git repository on all plans, with a .zip on paid plans. Database and uploaded files export separately. The editor itself cannot be self-hosted.
PloySource code through Git, per its docsSee below. Check the Terms for anything beyond that.
WordPress (self-hosted)YesThe software is free and open source and your files and database are in your own hosting account.

Webflow's plan prices as of November 2026 are Basic at $15 a month and Premium at $25 a month when billed yearly, with Starter free. Webflow repriced its plans in 2026, so check the pricing page for your renewal date. Prices change the cost of staying, which is one more reason lock-in matters.

Owning code is not the same as being free

Having the files helps, but a few things still lock you in:

  • The CMS. Webflow's code export leaves out dynamic content. You hold pages, not the system that made them.
  • Forms and logins. Code for a form is not the service that receives it.
  • Someone has to run it. Code with no developer, no host and no backups is a risk too. See how to export code from an AI app builder for what you need after the export.
  • Lovable's own docs note that moving the database alone does not move login, storage, realtime or functions. Check what travels together.

Ploy: what its pages say about code, data and exit

If you are considering a Ploy plan, here is what its own pages say as of November 2026.

  • Source code. Its docs FAQ says you can get your site's full source on every plan, including Free. Install its command-line tool and run ploy site git clone. You need the Member role or higher.
  • GitHub sync. Code Sync, which keeps your code in a GitHub repository you control, is free through the command line on every plan. Connecting it from the app needs a paid plan (pricing page: Starter at $50 a month, Pro at $300 a month, Enterprise by quote, with Free at $0).
  • Moving a repo in. Compatible Astro repositories can be imported with a command. Other frameworks such as Next.js and Vite/React are ported to Ploy's Astro starter by your own coding agent. Astro is a web framework for content sites. Repo migration with your own coding agent uses no Ploy AI credits, per its docs.
  • Data. The Terms say you keep all right, title and interest in the data and content you submit, that you keep ownership of AI outputs generated from your data, and that Ploy will make your customer data available for export for 30 days after termination. Ploy's Privacy page says it keeps customer data for 60 days after termination to allow export. The Terms are dated April 13, 2026 and the Privacy page April 15, 2026, so export within the first 30 days.
  • Database tables. The built-in database exports CSV, up to 10,000 rows per view, and the docs say CSV is for interchange, not backup.
  • The model. Ploy's site runs on its own component library (reusable page parts) and design tokens (saved colours and fonts), written in code with React, Tailwind and Astro, per its docs. React and Tailwind are common web code tools. That is a plain starting point, though how easily the exported code runs on a different host depends on what your site uses. Test it.
  • Not stated: whether code export continues after termination, and whether the exported code carries every feature your live site uses. Ask Ploy in writing.

Ploy's code export is a real strength compared with Wix and Framer. It is not a guarantee. See Ploy pricing, whether Ploy is legit and safe and the Ploy review for the wider picture.

The exit test: prove you can leave

Do this once now, and once a year. It takes an afternoon.

  1. Check the domain. Log in at the registrar with your own email. Pass: you are the registrant and can unlock it. Fail: it is in a vendor's or freelancer's name.
  2. Export what the platform allows. Download code, pages, images and CMS items. Pass: you hold a copy outside the vendor. Fail: no export exists.
  3. Run the copy. Open the exported files in a basic host or on your own computer. Pass: the main pages load with images and styling. Fail: pages are blank or broken.
  4. Count what is missing. List forms, CMS content, logins, redirects, scripts and plugins that did not come with it. Each is a rebuild task.
  5. Price the rebuild. Use the migration cost guide. Pass: the cost is one you could pay. Fail: you would have to start over.
  6. Save the exports on your own drive, in two places, with the date.

Questions to ask any vendor in writing

  • Can I download the full source of my live site on my current plan? In what format?
  • Does the export include CMS content, forms, logins and uploaded files, or only pages?
  • Who owns the code and content, in the terms' own words?
  • For how long after I cancel can I still export, and does that cover code as well as data?
  • If you change pricing, how much notice do I get, and can I leave without penalty?
  • Is there a data processing agreement (a contract on how my customers' data is handled) and a list of the companies that process data for you?
  • Can you share your security report? For Ploy, the Trust Center lists a SOC 2 Type 1 report and a feature page mentions Type II controls (as of November 2026), so ask for the report itself and read its type and dates. SOC 2 is an independent audit of a company's security controls.

Put the answers in an email thread you keep. Terms change, and an answer you can point to helps.

A worked example with made-up numbers

These numbers are invented to show the method. Say a salon owner has a 20-page site on a builder that gives no export, and pays $30 a month. She runs the exit test and finds: the domain is in her name (pass), no working copy exists (fail), the text and photos can be saved by hand (partial), and the booking form is the builder's own (fail). She scores the rebuild at about 25 hours of her time, or a freelancer quote. She then decides: keep paying, because the site is small and the rebuild cost is low, but move booking to a separate booking tool this month, and save all text and photos to her own drive every quarter.

A second owner has a 150-page site with a blog that brings in most of his enquiries. His platform exports code but not CMS content. The rebuild is large, so lock-in is a real business risk. He asks for a CSV export of each collection, keeps a Git copy of the code, and writes a redirect list now, so a future move is a plan and not an emergency. The same test gives two different answers, which is the point.

If an agency or freelancer built your site

Lock-in often sits with a person. Ask for the domain, hosting, analytics, Search Console and any code repository to be in accounts you own, with the agency added as a user. Ask for a handover note listing every tool, plugin and login, kept short and dated. If the agency uses AI tools to write pages or code, ask which ones and under whose account. The terms of those tools and the rules on who owns generated work vary, so check local law and your contract.

Who should not worry, and who should

  • Light concern: a one-page brochure on a platform with a plain domain and little traffic. A rebuild would be cheap.
  • Real concern: a site with many pages that brings in leads from search, a large CMS, a store, or custom features.
  • Choose differently: if owning every file matters most, use WordPress hosted in your own account, or a custom-coded site. Both cost more upkeep.
  • Skip Ploy if: you need written code and data ownership terms beyond what its pages say, an uptime promise (none is published on its pricing or docs pages), or a white-label agency dashboard (none is described).

How I'd approach this

Decision rule: pick the platform for the job, then make sure you can leave it. If a vendor will not tell you in writing what you can take out, assume the answer is "little" and price the rebuild into your plan.

If you want a custom site you own, or a half-built AI site finished, taken live on your own domain and looked after, Blur Studio does that. See what that includes.

First-week plan.

  1. Day 1: confirm you control the domain and the analytics and Search Console logins.
  2. Day 2: export everything your current platform allows, and save two copies.
  3. Day 3: try to open the exported files and list what is missing.
  4. Day 4: send the written questions above to your vendor.
  5. Day 5: if you are choosing a new platform, test a small import. Ploy's free plan is one way to test a small import and a Git clone with no payment, but read its terms first.
  6. Days 6 and 7: write the one-page exit plan: who does what, what it costs, how long it takes.

When you do decide to leave, follow how to cancel, downgrade or export from a website platform.

Questions people ask

What is vendor lock-in for a website?

It is when your site only works on one company's platform, so leaving means a rebuild or paying that company's price. It can involve the domain, code, content, data, hosting and the people who know the setup. Test each layer with the exit test above.

Can I export my website code from Wix, Framer or Squarespace?

Not as a working site. Wix says its sites must be hosted on Wix's servers, Framer says it offers no HTML export for self-hosting, and Squarespace exports a limited XML file made for WordPress. See moving off Wix or Squarespace.

Does Webflow let me export my site?

Yes, on a paid Workspace plan you can export code and host it anywhere. Webflow says CMS content is exported collection by collection, forms stop working, and exported code cannot be re-imported. Check Webflow's pricing page for current plan rules.

Do I own my website code if I use Ploy?

Ploy's docs FAQ says you can get your site's full source on every plan, and its Terms say you keep all right, title and interest in the data and content you submit. Code ownership wording beyond that is not stated, so ask Ploy in writing. See Ploy pricing.

What happens to my data if I leave Ploy?

Ploy's Terms say it will make customer data available for export for 30 days after termination, after which it may be deleted. Its Privacy page says 60 days. Export within the first 30 days and ask support in writing which period applies to you.

How do I know my domain is really mine?

Log in at the registrar, the company the domain is registered with, using your own business email, and check that you are the registrant and can unlock the domain. If an agency or builder holds it, ask them to move it to an account you control.

Is WordPress free of lock-in?

The software is free and your files and database sit in your own hosting account, so you can move them. You can still be locked in by a theme, plugins or one developer. See moving off WordPress for the other side.

Is this legal advice?

No. Contract and data rules vary by country. Check local law and read each vendor's current terms before you sign.

More in this topic: Websites: Google rules, privacy and ownership (6 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…