Decide which platform will own reservations, availability, guest records, payments, tasks, accounting context, and operational evidence after the transition.
System transition
Moving from an existing PMS into the HOS operating model.
A PMS transition touches more than reservations. Property records, guest data, future stays, financial references, channel relationships, housekeeping context, and historical evidence can all have different ownership and migration requirements.
This page describes the HOS transition model rather than a guaranteed migration service. Supported source systems, connectors, imports, implementation assistance, and migration depth depend on the deployed release.
Implementation principle
A successful PMS switch is a controlled systems transition.
The goal is not to copy every field from the old system. The goal is to preserve the records and relationships the operation still needs while making system ownership explicit.
Transition model
A controlled sequence before cutover.
The exact implementation may vary, but each stage should make assumptions, ownership, and validation more explicit.
Separate active operational records from historical information, configuration, reporting-only fields, and vendor-specific metadata.
Preserve the links between properties, reservations, guests, financial references, tasks, and evidence where those relationships are operationally necessary.
Validate future reservations, current stays, readiness tasks, and relevant financial context before changing the team's working system.
Move operating responsibility only after the new state has been reviewed and the team knows which legacy system remains authoritative for retained history.
Control points
What should remain protected during a PMS transition.
Active and upcoming stay information needs explicit reconciliation before operational responsibility moves.
Distribution connections and availability should not be assumed to transfer simply because reservation data has moved.
Balances, payouts, owner references, and accounting records may have retention or reconciliation needs outside HOS.
The outgoing system may need to remain accessible for historical evidence, reporting, or records that are intentionally not migrated.
Readiness
A PMS transition is ready when the new system boundary is understood, not merely imported.
01
The team knows which system owns each critical record after cutover.
02
Future reservations and property relationships reconcile against the source.
03
Channel and integration dependencies have been reviewed separately from data migration.
04
Historical records that are not migrating have a documented retention path.
Boundary
Keep the implementation promise narrower than the evidence.
HOS should not be presented as a universal replacement for every PMS function. Some operators may retain an existing PMS or specialist system and use HOS as the connected operating layer around it.
Compare PMS and HOS operating roles →