The essentials · 30-second read
Vendor lock-in is a dependency nobody priced or planned an exit for. Four checks keep it under control:
- Keep the domain, DNS, platform project, analytics and Search Console in your company's name, with recovery on company addresses.
- Separate account access from intellectual property: list what is assigned, licensed or kept by the supplier.
- Ask for a representative export and note which functions would have to be rebuilt elsewhere.
- Make handover an acceptance test and write exit deliverables, fees and personal data return into the contract.
Summarize this article with AI
To avoid vendor lock-in when choosing website vendors, keep the critical accounts (domain, DNS, website platform, analytics, Search Console) in your company's name, and get written answers on what you own, what an export really contains and how another team would take over. Agree on these points before signing, then test them before you accept the project.
Lock-in is not the same as using a hosted platform. It is a dependency nobody priced or planned an exit for: a retainer that ends, a domain registered under a former supplier's email address, an export that leaves out the functions the business relies on. This guide separates agency lock-in from platform lock-in and turns both into checks you can ask website vendors to demonstrate.
What is vendor lock-in for a website?
In economics, vendor lock-in describes a customer who depends on one vendor and cannot switch to another without substantial switching costs. For a website, those costs appear as lost access, rebuilt functionality, broken URLs or weeks spent negotiating access to your own infrastructure.
Three kinds of dependency usually combine:
| Type | Where it comes from | Typical example | What reduces it |
|---|---|---|---|
| Agency lock-in | The supplier controls accounts, undocumented code or operational knowledge | The domain is registered by the agency; only one developer knows how to publish | Company-owned accounts, a handover pack, a handover test |
| Platform lock-in | Reliance on a platform's hosting, CMS, components or managed services | Forms, search or member areas that only work on the original platform | A documented exit scenario, a representative export, a separate migration scope |
| Contract lock-in | Ownership, licences or exit terms left vague | Design files or code whose transfer depends on unclear conditions | An explicit rights clause, defined exit deliverables, transition fees stated upfront |
None of these automatically makes a provider unsuitable. A managed platform can be a sound choice when convenient publishing matters more than independent hosting. The question is whether the dependency is understood, acceptable and backed by a workable exit route.
Is vendor lock-in a real risk for your website?
It becomes a risk when changing providers would cost far more than expected, or when you cannot change at all without the current supplier's cooperation. Warning signs:
- nobody inside the company knows who holds the domain registrar login;
- publishing or correcting a page requires a request to the agency;
- no one can list the integrations and who pays for each subscription;
- the contract says nothing about what happens when the engagement ends.
Before signing, define two separate outcomes: replacing the agency while keeping the platform, and leaving the platform itself. The five checks below cover both.
How to avoid vendor lock-in: five checks before you sign
Evaluate control, rights, portability, handover and contract terms before approving a proposal. Ask for a representative demonstration during procurement, then repeat the relevant tests on your own website before final acceptance.
1. Keep critical accounts under company control
Account ownership should survive the supplier relationship. When website vendors create accounts, agree on the ownership structure first and tie recovery details to business-managed email addresses.
| Account | Who should own it | What to ask the vendor for |
|---|---|---|
| Domain registrar | Your company, as registrant | Registrant name, a login on a company address, the renewal date |
| DNS | Your company | Access to the DNS zone and a record of every entry |
| Website platform and billing | Your company, or a documented transfer at launch | Who owns the project, who pays, how another agency gets access |
| Analytics | Your company, with an internal Administrator | Administrator access for a named internal owner |
| Google Search Console | Your company, as verified owner | Verification by a company account, not a supplier's personal one |
| Integrations (CRM, forms, email) | Your company | The list of accounts and the owner of each subscription |
The registrant matters for the domain. ICANN's Transfer Policy requires registrars to give the registered name holder the AuthInfo code used to move a domain to another registrar, and ICANN reminds registrants that they must keep their contact details accurate and up to date. Recovery emails sent to a former supplier's address will not help you. If DNS is new territory for your team, start by documenting who can change it.
Give suppliers the permissions they need without sharing a single administrator login. Google Analytics separates Administrator, Editor and Viewer roles, so an agency can work with the access it needs while your company keeps the Administrator role. In Search Console, removing an owner does not revoke their verification tokens: Google's page on owners, users and permissions explains that a removed owner can verify again until those tokens are deleted. This is a practical foundation for getting outside website help without surrendering control.
2. Separate intellectual property from account access
Being an account administrator does not establish what your business legally owns.
The agreement should distinguish custom deliverables from pre-existing supplier tools and third-party assets. A supplier cannot transfer rights it does not hold, and some licences may need to be purchased directly by your company.
| Deliverable | Question to settle in writing |
|---|---|
| Design files | Are they delivered, in which format, and can another team edit them? |
| Custom code | Is it assigned to you or licensed, and can another developer modify it? |
| Copy and photography | Who holds the rights, and are there usage limits? |
| Fonts and templates | Whose licence is it, and does it follow the site if the supplier leaves? |
| Supplier's own tools and components | What remains the supplier's property, and on what terms can you keep using it? |
A licence to display the finished site may not give the same flexibility as the right to adapt the underlying work. Have counsel review ambiguous language, especially where assignment depends on payment or other conditions. Ownership and licensing are among the details website development packages can leave unclear, so put them in the statement of work rather than in sales emails.
3. Test what can actually leave the platform
An export button is not proof that the website can operate elsewhere. Request a demonstration with a representative page and content collection, then separate content portability from functional portability.
| Element | What an export may contain | What may stay behind |
|---|---|---|
| CMS content | Text and fields, for example as CSV | Templates, relationships between records, publishing workflows |
| Images and files | The files themselves | References between records, alt text if not exported |
| Pages | Static code that reproduces the layout | An editable CMS for your team |
| Forms, search, member areas | Usually nothing that runs on its own | The hosted services that make them work |
Require website vendors to explain what a migration would retain, rebuild or replace. If you are still choosing a development platform for B2B growth, document these trade-offs alongside your publishing and integration needs. Do not choose an unsuitable platform only because its exports look more complete.
4. Make handover an acceptance test
Documentation is useful only if another qualified person can use it. Agree on a handover exercise before development begins: a replacement developer or an internal technical owner should locate the project, understand its structure, make a controlled change and explain the publishing process without relying on the original developer's memory.
The handover pack should list:
- custom scripts and integrations, with the account each one uses;
- subscription owners and renewal dates;
- deployment or publishing steps;
- an SEO baseline: important URLs, redirects, metadata and indexing settings.
Credentials belong in a password manager, not in an unprotected document. The SEO baseline matters most if you ever leave the platform: Google's guide to site moves with URL changes asks you to map old URLs to new ones, use permanent server-side redirects and keep them generally for at least a year. Access to a website builder's SEO controls is not enough if the incoming team cannot see how they were configured. For the full list of launch deliverables, see what professional website developers should deliver at launch.
5. Put exit obligations in the agreement
An exit route needs defined deliverables, timing and costs. The exit terms should specify the handover materials, transfer responsibilities, notice requirements and any charge for transition assistance. Separate routine delivery of agreed assets from migration work that genuinely falls outside the project scope.
A useful clause might require delivery of the agreed project files, content exports and integration documentation within a defined period after termination, subject to clearly stated payment conditions. Have counsel adapt the wording to your agreement and jurisdiction rather than copying a generic clause.
Personal data needs its own line. If the vendor processes personal data on your behalf (form submissions, CRM records), Article 28 of the GDPR requires the contract to state that the processor, at the controller's choice, deletes or returns all the personal data at the end of the services. Also settle cancellation terms, renewal dates and third-party subscriptions before signing. When comparing website package pricing, include these obligations so a lower project fee does not hide an undefined exit bill.

Changing agencies is not the same as changing platforms
These are different projects and need different acceptance criteria.
| Question | Changing agency, keeping the platform | Leaving the platform |
|---|---|---|
| What must transfer | Project ownership, permissions, billing, documentation | Content, assets, URLs and every function rebuilt elsewhere |
| Proof to ask for | Another team publishes a controlled change | A representative export and a written migration scope |
| SEO exposure | Limited if URLs stay the same | URL mapping and permanent redirects required |
| Nature of the work | Handover time | A migration project, often with redevelopment |
If you want to replace an agency while keeping Webflow or Framer, focus on project ownership, permissions, billing and documentation. The business needs a usable route to appoint another qualified team, not necessarily an independently hosted copy of the website.
If independent hosting is a requirement, assess it separately. For Webflow, review the official code export guidance and confirm which proposed functions would still depend on hosted services. For Framer, check the official help documentation for current transfer, export and hosting constraints. Verify what the proposed plan and configuration allow before committing, and treat a platform exit as a website migration with its own scope.
Mistakes that make switching expensive
Most preventable lock-in comes from an assumption that was never tested.
- Accepting ownership language without operational access. A contract can assign deliverables while the registrar, platform account or integration credentials remain under supplier control. Check both the legal position and the actual account setup.
- Treating exports as complete backups. An exported file may omit workflows, settings or hosted functions. Define what recovery means for you: restoring content, the published website or the full editing environment.
- Comparing website vendors only on build price. Include subscriptions, maintenance, training and the work needed to change providers. The same logic explains why a cheaper website builder can cost more over time.
Checklist before signing
Turn the five checks into documented acceptance criteria rather than verbal assurances.
- Name the account owners. Domain, DNS, platform project, analytics, Search Console and critical integrations, with recovery arrangements.
- Confirm usable rights. Custom deliverables, third-party licences, supplier-owned components and any limits on modification or transfer.
- Define both exit scenarios. How you would replace the agency, and what leaving the platform would require.
- Inspect a representative export. Content structure, assets and metadata, plus the functions that would need replacing.
- Specify the handover pack. Project structure, integrations, subscription owners, publishing instructions and SEO baseline.
- Schedule a handover test. Who performs it and what they must demonstrate before acceptance.
- Agree on exit terms. Notice, deliverables, transition fees, access removal and the return or deletion of personal data.
Mark each item as demonstrated, contractually committed or unresolved. Close ownership and access gaps before signature; schedule project-specific tests for acceptance once the build exists.
How BeBranded approaches vendor lock-in
BeBranded works in two stages: consulting first, then production. During project scoping, we help you list the accounts, rights and handover criteria that belong in the brief, before any platform is chosen. The platform then follows your constraints: a custom build with Next.js and Payload, Webflow when it is the right fit, or a combination. Both options carry dependencies, and we prefer to write them down rather than leave them implicit. If you are comparing website vendors and want a second opinion on ownership and exit terms, book a call with the two founders.
Sources
- 1. Wikipedia: Vendor lock-in · en.wikipedia.org/wiki/Vendor_lock-in
- 2. ICANN: Registrants' benefits and responsibilities · icann.org/resources/pages/benefits-2013-09-16-en
- 3. ICANN: Transfer Policy · icann.org/en/contracted-parties/accredited-registrars/transfer-policy-01-06-2016-en
- 4. Google Analytics Help: add, edit and delete users · support.google.com/analytics/answer/9305788
- 5. Search Console Help: managing owners, users and permissions · support.google.com/webmasters/answer/7687615
- 6. Google Search Central: site moves with URL changes · developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes
- 7. GDPR Article 28: processor · gdpr-info.eu/art-28-gdpr/
- 8. Webflow: code export · university.webflow.com/lesson/code-export
- 9. Framer Help Center · framer.com/help/



