Avoiding Vendor Lock-In When Buying Software
By CodexierPublished 4 min read
Vendor lock-in is when leaving a supplier becomes so costly or difficult that you stay even though you would rather not: after a price increase, poor service or when your needs have changed. It rarely comes from a single bad decision. It builds up through data you cannot export, accounts registered in someone else's name, custom code nobody else can read and contracts without exit terms. This guide explains how lock-in happens and what to check before you buy, so the option to switch stays open.
How lock-in happens
Data lock-in
Your customer records, orders or history can only be exported partially, or in a format nothing else can read.
Account lock-in
The domain, hosting, Google Ads or App Store account is registered to the agency, not to you.
Technical lock-in
The system is built on a proprietary framework or with undocumented code only the original developer understands.
Contract lock-in
Long terms, automatic renewal, no data return clause and fees for leaving.
Data export and formats
Ask every vendor how you get all your data out, not just some of it. A CSV export of customers is not enough if order history, notes, attachments and relations stay behind. Swedish businesses have an advantage in accounting: the SIE format lets you move bookkeeping between Fortnox, Visma and other systems. Look for equivalents elsewhere.
| System type | What to be able to export | Good formats |
|---|---|---|
| Accounting | Full ledger, vouchers, customer and supplier registers | SIE, CSV |
| CRM | Contacts, companies, deals, notes, activity history | CSV, API access |
| Webshop | Products, customers, orders, images | CSV, API access |
| Website | Pages, images, forms, redirects | Standard CMS export, source files |
| Custom system | Complete database dump and documentation | Standard SQL database |
Under GDPR, individuals have a right to data portability, and your processor agreements should require the vendor to return or delete personal data when the agreement ends. That is a legal backstop, but a practical, tested export is what makes switching realistic.
Contract terms that protect you
- Ownership: you own the code, design and content you paid for, or at least have an unlimited licence to use and change it.
- Source code access: the code is in a repository you can access, not only on the vendor's servers.
- Data return: on termination, the vendor delivers all data in agreed formats within a set time.
- Handover: a defined amount of help to transfer to a new supplier, at an agreed price.
- Notice and renewal: reasonable notice periods and no silent automatic renewal for long terms.
- Price changes: advance notice and a right to terminate if prices rise significantly.
Our guide to IP clauses in software contracts goes deeper into ownership wording.
Technical choices that keep options open
- Widely used languages and frameworks, so other developers can take over.
- Standard databases rather than proprietary data stores.
- Documentation and readable code as part of the delivery, not an afterthought.
- Integrations through documented APIs rather than screen-scraping or one-off hacks.
- Cloud and hosting accounts in your name, with the vendor added as a user.
These choices rarely cost more at the start. They cost more when they are skipped and you want to switch later. Our scaling and system upgrade service often starts with exactly this: taking over a system from another supplier and making it maintainable. Prices are on our pricing page.
Testing your exit plan
Once a year, or before renewing a large contract, do a dry run: export the data, check that it is complete and readable, and confirm you have admin access to every account. It takes an afternoon and tells you whether your exit options are real or only on paper.
When lock-in is acceptable: a well-run SaaS tool that does its job at a fair price, with a decent export, is often better value than a flexible system you must maintain yourself. Accept the lock-in knowingly where the value is high and the exit is at least possible. Book a call if you are about to sign and want a second look at the terms.
Frequently asked questions
Is using Shopify or HubSpot vendor lock-in?
To a degree, yes. Both offer good exports of core data, so switching is possible but takes work. That is usually an acceptable trade for not running the platform yourself.
Who should own my domain name?
Your company, registered in its name with your contact details. The agency can manage it with access, but should not be the holder.
What is source code escrow?
An arrangement where the code is deposited with a third party and released to you if the vendor goes bankrupt or stops supporting it. Relevant for business-critical systems you do not own outright.
Can I switch agency in the middle of a project?
Yes, if you have access to the code, accounts and documentation. Without them, switching means starting over, which is exactly what exit terms prevent.
About to sign a software deal?
Book 15 minutes. We look at the setup and the contract terms and point out where you risk getting locked in, and how to fix it before signing.
Book a free 15-minute call