Vendor lock-in in network operations: the hidden cost
Lock-in is not only contracts—it is data, workflows, and tribal knowledge. A buyer’s framework for staying free enough to change.
Three layers of lock-in
- Contractual — terms, hardware ties, minimums
- Data — exports missing, IDs unstable, history trapped
- Workflow — playbooks and muscle memory that only work in one UI
Teams often negotiate (1) and ignore (2) and (3).
Questions to ask before you buy
- Can we export inventory, alerts, and usage with stable identifiers?
- Can two tools coexist during migration?
- Are severities and site IDs ours—or the vendor’s opaque keys?
- What happens to audit history at cancel?
Practical anti-lock-in habits
- Keep a system of record you own for customer ↔ site ↔ device
- Prefer vendors who document APIs and exit
- Avoid encoding business logic only inside one vendor’s proprietary rules language without export
- Rehearse a small migration while you still like the vendor