Vendor Lock-In: How to Date a Cloud Provider Without Marrying Them
Every relationship starts the same way. They are attentive. They give you free credits. They promise you will never have to worry about anything again. You move a few things in. Then a few more. Before you know it, your entire business is living at their place, and one day they announce that rent is going up. Choosing a cloud provider in Kenya can go exactly like this if you are not careful.
This, in short, is vendor lock-in. It happens when moving away from a technology provider becomes so difficult or expensive that you effectively cannot leave, even when you want to. It is one of the most common regrets businesses have about the cloud, and one of the most avoidable.
How you end up locked in
Lock-in rarely happens through one big decision. It builds up through many small conveniences:
Using features that only one provider offers, with no equivalent elsewhere
Storing data in formats that are hard to export or read without their tools
Building custom workflows that only exist inside one platform
Signing long contracts with steep penalties for leaving early
Letting one person set everything up and never documenting how it works
None of these is automatically wrong. Proprietary features can be genuinely useful and save time. The problem is using them without realising what you are giving up.
Choosing a cloud provider: questions for the first date
Before committing to any cloud service, whether it is accounting software, a school system or a full hosting platform, ask a few awkward questions. A good provider will answer them happily. A provider who gets defensive is telling you something important.
Can I export all my data, at any time, in a standard format like CSV or a common database format?
What happens to my data if I cancel, and for how long is it kept?
Are there fees for taking my data out?
How much notice do you give before price changes?
What is the minimum contract length, and what does early exit cost?
Do you have an API, so other systems can connect to yours?
Fatuma, who manages operations for a group of clinics in Mombasa, asked these questions when choosing a booking system. One vendor could not explain how she would get her patient records back if she left. She thanked them politely and moved on. It was the best breakup she never had.
Keep your options open
You do not have to avoid commitment entirely. You just want to make sure that if things go wrong, leaving is painful but possible. Some practical habits:
Export your key data regularly and store a copy somewhere you control
Prefer widely used, standard technologies over obscure ones where the choice is roughly equal
Document how your systems are set up, including integrations and settings
Keep the admin passwords and account ownership in the company's name, not one employee's
Review contracts before they auto-renew
Ownership matters more than you think
One sneaky kind of lock-in has nothing to do with technology. It happens when the cloud account belongs to a former employee or a developer you no longer work with. Njoroge, who runs a tour company, discovered his website and email were registered under his old web designer's personal account. The designer had moved abroad and stopped replying. Getting control back took months of polite emails and one very impolite one.
Make sure your business is the legal owner of every account, domain and subscription. Developers and IT staff should have access, not ownership.
So, should you commit?
Absolutely, when the relationship is healthy. Staying with a good provider for years is a perfectly fine outcome. The goal is not to leave. The goal is to stay because you want to, not because you are trapped.
Date with your eyes open, keep a copy of your data at your own place, and never let anyone else hold the keys to your house. If it works out, wonderful. If it does not, you can pack your bags in a weekend instead of a year.
A practical step for this week: pick your most important cloud system and try exporting your data. If it takes more than an afternoon, you have learned something valuable. And whenever you evaluate new business software, from anyone, make the export test part of the demo.