Vendor Lock-In: Cloud and Software Licenses

A Baton Rouge law firm spent three years on a legal SaaS platform. When they wanted to switch, the vendor quoted $40,000 to export their data in a usable format. Their data was structured in the vendor's proprietary schema. Migration wasn't just expensive—it was architecturally difficult.

This is vendor lock-in. It's not always avoidable. But it should always be intentional.

What lock-in actually means

Lock-in means leaving costs more than staying. It can mean:

• Data that's hard to export
• Applications built on proprietary APIs
• Contracts with steep exit fees
• Custom integrations that only work with one provider
• Staff trained on one platform who can't easily transition to another

The lock-in spectrum

No lock-in:

• Standard software with standard data formats
• PostgreSQL, MySQL, WordPress
• Data you can export in standard formats (CSV, JSON, SQL dumps)
• Open-source software you control

Moderate lock-in:

• Cloud infrastructure using standard tools (PostgreSQL, Docker, Kubernetes)
• Data is portable but migration takes time and money
• Exit costs are real but manageable

Heavy lock-in:

• Platform-specific managed services (AWS Lambda, Azure Functions, GCP Cloud Run beyond basic)
• Proprietary databases (AWS DynamoDB, Azure Cosmos DB)
• SaaS with poor export capabilities
• Complex integrations that only work with one vendor

Extreme lock-in:

• Custom hardware or network configurations
• Software that requires vendor approval to modify or extend
• Contracts that penalize switching financially
• Data stored in formats only one vendor can read

Why lock-in is sometimes fine

You're buying capability, not just infrastructure. Salesforce is expensive and proprietary. But if your sales team closes deals with it, the lock-in is worth it. You bought outcomes, not infrastructure.

Managed services reduce operational risk. AWS RDS is more expensive than self-hosted PostgreSQL. But AWS handles backups, failovers, and upgrades. If your team can't manage PostgreSQL effectively, the lock-in is worth the cost.

Switching has costs too. Every migration risks downtime, data loss, and business interruption. Sometimes the cost of staying is lower than the cost of switching.

When lock-in becomes a problem

You're locked into a vendor who's raising prices. You built your entire infrastructure on AWS. AWS raises prices 10%. You're still on AWS because migration costs more than the price increase.

Your vendor is struggling financially. A SaaS vendor goes out of business. Your application goes down. Your data may or may not be recoverable. This happens more than people expect.

You need features that your vendor won't build. Your platform doesn't support the integration you need. You can't build it yourself. You're stuck waiting for a roadmap item that may never arrive.

Exit costs are higher than expected. You want to leave. The migration will take 6 months and cost $80,000 in engineering time. You're trapped by the cost of freedom.

What can go wrong

A vendor acquisition changes everything. Your SaaS vendor gets acquired by a competitor. Prices go up. Features disappear. Support degrades. You're now on a platform you didn't choose.

Proprietary data formats become liabilities. Your CRM has 10 years of customer data in a custom schema. The export is technically possible but requires a consultant to parse. Every year you stay, the data becomes harder to use elsewhere.

Long-term contracts become millstones. You signed a 3-year contract for a platform that seemed great at signing. Two years in, a better option exists. You're paying for a platform you're not using.

Feature freezes leave you stranded. A niche vendor stops investing in their product. Security updates stop. New integrations don't appear. You're on a platform that's slowly dying.

How to assess lock-in risk

1. Ask "what does exit look like?" Before you sign, ask the vendor: "If I wanted to leave in 18 months, what would that cost? What would I get to take with me?"

2. Check data portability. Can you export your data in a standard format? CSV, JSON, SQL? Or do you need a custom extraction process? If the vendor can't answer this quickly, that's a red flag.

3. Evaluate integration depth. How deeply is the platform integrated into your workflows? If it touches every part of your business, exit is harder. If it's a single tool, switching is easier.

4. Consider vendor financials. How long has the vendor been in business? Have they raised funding recently? Are they profitable? A struggling vendor is a risk to your operations.

5. Look for open standards compliance. Does the vendor use open standards for data exchange? Do they support common APIs? Or is everything proprietary?

What it costs to switch (2025-2026)

Simple SaaS (CRM, project management):

• Data export: Free (usually)
• Migration to new platform: $2,000-10,000 in consulting or internal time
• Productivity loss during transition: 2-4 weeks of reduced efficiency
• Total: $5,000-20,000 depending on complexity

Complex infrastructure migration (AWS to Azure or GCP):

• Migration planning: $5,000-20,000
• Engineering to execute migration: $20,000-100,000+ depending on complexity
• Testing and validation: $10,000-30,000
• Egress fees: $1,000-10,000 depending on data volume
• Total: $40,000-150,000 for enterprise-grade migrations

Self-hosted migration (one platform to another):

• Data migration: $2,000-15,000 depending on data volume and complexity
• Application migration: $10,000-50,000 if custom code is involved
• Testing: $5,000-20,000
• Total: $20,000-85,000

Vendor questions (copy/paste)

• What does it cost to export all my data if I leave? What format is it in?
• Do you support standard data formats (CSV, JSON, SQL)? Can I get a full data export?
• Have other customers successfully migrated away? Can you connect me with one?
• What happens to my data if you go out of business or get acquired?
• Do you have multi-year contracts with penalties for early termination?
• What integrations do you support? Are they standard APIs or proprietary?

Minimum viable implementation

1. Before signing any contract, understand your exit. Ask about data export, migration support, and termination costs.
2. Maintain a data export quarterly. If your vendor provides a data export, use it. Store it somewhere independent. This gives you an up-to-date backup if things go wrong.
3. Document your integrations. Know which systems talk to which. If one vendor goes down, what breaks?
4. Review your contracts annually. Are the terms still favorable? Are there vendors you're paying for but not using?
5. Budget for potential migrations. If you're on a platform, put aside money for exit. If you need to leave, you're not caught flat-footed.

When to hire help

• You're evaluating a major SaaS platform and want someone to review the contract terms before you sign.
• You're already locked into a platform and want to understand your actual exit costs.
• You're planning a migration and need someone to manage the process.
• You discovered your vendor doesn't support standard data exports and need a strategy for managing the risk.
• A vendor is raising prices significantly and you need an objective assessment of your alternatives.

Lock-in isn't always bad. Sometimes you're paying a premium for convenience, capability, or reduced risk. The problem is when you're locked in without knowing it, or when the lock-in costs more than you expected.