PMS Overview
LIKE MAGIC sits on top of your Property Management System (PMS). It does not replace it. Reservations, folios, room state and guest profiles live in the PMS; LIKE MAGIC reads from and writes to it through an integration. Because reservation, folio and room data come from the PMS, some guest-facing behaviour can differ between properties on different PMSs. This article explains the PMS landscape so an administrator can tell why a capability behaves differently across two properties.
1. The Supported PMS Systems
The three PMSs this documentation covers are:
- Apaleo
- Mews
- Oracle OPERA Cloud (via OHIP)
ℹ️ Note: In data exports and API payloads, Oracle OPERA Cloud reservations and profiles appear under the
OHIPorigin. There is no separate "Opera" origin.
2. What Depends on Your PMS
Most of what your team and your guests use works the same on every supported PMS. Where a capability draws on PMS data (folio and billing details, check-in and checkout steps, key issuing, the events a property emits), its exact behaviour follows the connected PMS, and a few capabilities are only available on some PMSs. Wherever that is the case, the article for that capability says so; this overview does not repeat those details.
ℹ️ Note: Because the PMS follows from the PMS connection and is not something you toggle, moving a property to another PMS is a migration, not a setting change. Treat "which PMS" as a fixed property attribute when you plan a rollout.