Vendor lock-in describes dependence on a provider that makes switching or exiting uneconomical. In an ERP context, that matters a lot: orders, finances, inventory and often production all depend on the system. A company that is stuck loses room to maneuver on pricing, customization and strategic decisions.

Lock-in rarely comes from a single contract. Typical levers: per-user or per-module license models, closed extensions, proprietary data formats without export, operations tied exclusively to the vendor, and undocumented customizations.

ERP systems are especially exposed because they accumulate core data over years. Before rollout, it is worth checking:

• Can data be exported completely and in a machine-readable format?
• Can customizations continue to be supported by a different provider?
• What happens if terms change or a module is discontinued?

An exit strategy is risk management, not distrust. Test exports, review contract clauses, and document customizations.

Open platforms address lock-in through freedom of choice in operations, support and extension. What matters is whether source code, data and extensibility stay with the customer. Further reading: digital sovereignty and open source ERP.

Vendor lock-in is an economic question. Management and IT should clarify which dependencies are acceptable before signing the contract.