How to avoid vendor lock-in when choosing website vendors

Avoid vendor lock-in with website vendors by keeping critical accounts in your company's name and getting written answers on rights, exports, handover and exit terms before you sign.
Roland Vekemans, co-founder of BeBranded
Development · 11 min read · Published Nov 19, 2026
Illustration for the article “How to avoid lock-in when choosing website vendors”

Share this article

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:

TypeWhere it comes fromTypical exampleWhat reduces it
Agency lock-inThe supplier controls accounts, undocumented code or operational knowledgeThe domain is registered by the agency; only one developer knows how to publishCompany-owned accounts, a handover pack, a handover test
Platform lock-inReliance on a platform's hosting, CMS, components or managed servicesForms, search or member areas that only work on the original platformA documented exit scenario, a representative export, a separate migration scope
Contract lock-inOwnership, licences or exit terms left vagueDesign files or code whose transfer depends on unclear conditionsAn 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.

AccountWho should own itWhat to ask the vendor for
Domain registrarYour company, as registrantRegistrant name, a login on a company address, the renewal date
DNSYour companyAccess to the DNS zone and a record of every entry
Website platform and billingYour company, or a documented transfer at launchWho owns the project, who pays, how another agency gets access
AnalyticsYour company, with an internal AdministratorAdministrator access for a named internal owner
Google Search ConsoleYour company, as verified ownerVerification by a company account, not a supplier's personal one
Integrations (CRM, forms, email)Your companyThe 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.

DeliverableQuestion to settle in writing
Design filesAre they delivered, in which format, and can another team edit them?
Custom codeIs it assigned to you or licensed, and can another developer modify it?
Copy and photographyWho holds the rights, and are there usage limits?
Fonts and templatesWhose licence is it, and does it follow the site if the supplier leaves?
Supplier's own tools and componentsWhat 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.

ElementWhat an export may containWhat may stay behind
CMS contentText and fields, for example as CSVTemplates, relationships between records, publishing workflows
Images and filesThe files themselvesReferences between records, alt text if not exported
PagesStatic code that reproduces the layoutAn editable CMS for your team
Forms, search, member areasUsually nothing that runs on its ownThe 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.

A staff member prepares domain transfer paperwork and account recovery details during a handover from website vendors.

Changing agencies is not the same as changing platforms

These are different projects and need different acceptance criteria.

QuestionChanging agency, keeping the platformLeaving the platform
What must transferProject ownership, permissions, billing, documentationContent, assets, URLs and every function rebuilt elsewhere
Proof to ask forAnother team publishes a controlled changeA representative export and a written migration scope
SEO exposureLimited if URLs stay the sameURL mapping and permanent redirects required
Nature of the workHandover timeA 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.

  1. Name the account owners. Domain, DNS, platform project, analytics, Search Console and critical integrations, with recovery arrangements.
  2. Confirm usable rights. Custom deliverables, third-party licences, supplier-owned components and any limits on modification or transfer.
  3. Define both exit scenarios. How you would replace the agency, and what leaving the platform would require.
  4. Inspect a representative export. Content structure, assets and metadata, plus the functions that would need replacing.
  5. Specify the handover pack. Project structure, integrations, subscription owners, publishing instructions and SEO baseline.
  6. Schedule a handover test. Who performs it and what they must demonstrate before acceptance.
  7. 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. 1. Wikipedia: Vendor lock-in · en.wikipedia.org/wiki/Vendor_lock-in
  2. 2. ICANN: Registrants' benefits and responsibilities · icann.org/resources/pages/benefits-2013-09-16-en
  3. 3. ICANN: Transfer Policy · icann.org/en/contracted-parties/accredited-registrars/transfer-policy-01-06-2016-en
  4. 4. Google Analytics Help: add, edit and delete users · support.google.com/analytics/answer/9305788
  5. 5. Search Console Help: managing owners, users and permissions · support.google.com/webmasters/answer/7687615
  6. 6. Google Search Central: site moves with URL changes · developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes
  7. 7. GDPR Article 28: processor · gdpr-info.eu/art-28-gdpr/
  8. 8. Webflow: code export · university.webflow.com/lesson/code-export
  9. 9. Framer Help Center · framer.com/help/

FAQ

Questions about this topic.

Another question?

Write to us
What is vendor lock-in for a website?
Vendor lock-in is a dependency that makes changing providers much harder or more expensive than expected. For a website it comes from three places: an agency that controls accounts or undocumented code, a platform whose hosting or managed services cannot be moved, and a contract that leaves ownership or exit terms vague. Each one needs its own check before you sign.
Which website accounts should your business control?
Your business should control the domain registrar and DNS, with recovery details on business-managed email addresses. Apply the same rule to analytics, Google Search Console, tag management and critical integrations. Confirm who owns the website project, who pays the subscription and how another agency would get access. Give suppliers role-based permissions instead of a shared administrator login.
Does owning the finished website guarantee you can change providers?
No. Contractual ownership does not guarantee operational access or unrestricted rights to every component. Distinguish custom deliverables from supplier-owned tools and third-party assets such as fonts, templates and photography. Clarify whether another developer can modify the work and whether separate licences are needed. Have counsel review ambiguous ownership and licensing terms before signing.
Does a website export mean the site can run unchanged elsewhere?
No. Content portability and functional portability are different. A CSV may keep text without templates, relationships or publishing workflows, and static code may reproduce pages without an editable CMS. Request a representative export, inspect content, images and metadata, and list the functions, such as forms, search or member areas, that would need rebuilding.
How should you test a website vendor's handover?
Make handover an acceptance test agreed before development starts. An internal technical owner or a replacement developer should locate the project, understand its structure, make a controlled change and explain publishing without the original developer's help. The handover pack should cover scripts, integrations, subscription owners and an SEO baseline of important URLs, redirects and metadata.
What exit terms should a website vendor agreement include?
Define notice, handover deliverables, transfer responsibilities, delivery timing, payment conditions and transition fees. Separate routine delivery of agreed assets from extra migration work. If the vendor processes personal data for you, GDPR Article 28 requires the contract to provide for its deletion or return at the end of the services. Settle renewals and third-party subscriptions too.

Keep reading

Keep reading, more from the blog.

Illustration for the article “Why your Webflow contact form is not sending leads”
Development

Why your Webflow contact form is not sending leads

A Webflow contact form usually loses leads at one of four stages: submission, storage, notification or CRM routing. This guide shows how to find the broken stage with one traceable test, fix it and verify the full route.

Read the article
Illustration for the article “How to plan a website for an online business pre-launch”
Development

How to plan a website for an online business before launch

Planning a website for an online business starts with four decisions: what the launch must prove, how a visitor becomes a customer, how you will deliver and who runs the site. This guide turns them into a build-ready brief.

Read the article
Illustration for the article “What the best business websites show on pricing pages”
Development

What the best business websites show on pricing pages

The best business websites put the billing unit, commitment, scope, limits and next step beside the price. Here is what to show on a pricing page, how to check it and how to measure it.

Read the article

Let’s talk

Tell us what you want to build.

Thirty minutes with the people who will work on your project. You leave with a clear view of the scope, the timeline and the next steps.

What happens next

  1. 1A 30-minute callWe listen to your goals, your constraints and your context.
  2. 2A clear scopeWe map what is worth doing first, and what it takes.
  3. 3A costed proposalYou decide, with no commitment and no sales pitch.