Hotel Technology Vendor Lock-In

The best time to design a technology exit is before the contract starts. Hotels should know what they can export, which devices remain usable, how long migration takes and what happens to guest and operational data when service ends.

Inventory the dependency

List property configuration, rooms, devices, content, knowledge base, menus, orders, analytics, users, integrations, certificates and custom branding. Mark which data belongs to the hotel, content partner or platform.

Ask the exit questions

• 1Which data can be exported, in what format and through which interface?
• 2Does export include identifiers and relationships needed to reconstruct the property?
• 3Who owns STBs, servers, licences and custom application packages?
• 4Can supported televisions be repurposed without a site visit?
• 5How long is read-only access available after termination?
• 6What deletion certificate or audit record is provided?
• 7Which fees apply to switching and professional assistance?
• 8How are open guest requests and financial records handled?

Use the EU Data Act as a baseline

The EU Data Act has applied since 12 September 2025 and includes cloud switching and interoperability obligations. The European Commission explains that SaaS providers should make open interfaces available and export customer data in a commonly used, machine-readable format, subject to the Regulation's scope and exclusions.

Hotels should still write specific deliverables into the contract. A general legal right is not a migration plan.

Protect continuity

Plan the overlap period, DNS, identity, PMS events, device re-pairing, content rights and room-by-room verification. Keep an offline copy of core property information and current device inventory. Test an export annually.

Avoid a different kind of lock-in

An open API does not help if every room contains unsupported hardware. Prefer validated industry-standard televisions, documented network design and endpoints that can be reset or reassigned. Customisation should live in configuration where possible.

COTT.TV portability approach

COTT.TV uses property, room and device records with central administration and supports standard deployment routes across hospitality televisions and Android STBs. Enterprise contracts should define data access, export and termination assistance in proportion to the deployment.

Sources and further reading

• 1European Commission: Data Act explained
• 2European Commission: study on data-processing interoperability
• 3European Commission: GDPR processing principles