Changing a Hotel PMS: Which Migration Costs Should Be Clarified Before Signing?

Changing a Hotel PMS: Which Migration Costs Should Be Clarified Before Signing?

Suppose a hotel receives two quotes for a new property management system. One has lower software fees; the other includes more implementation services. If the scope of data migration, third-party interfaces and cutover support is not aligned, comparing totals can mistake work left out of a quote for a saving.

Before signing, owners and general managers need to establish whether the budget covers moving the hotel's business to the new system. Software subscriptions are one component. The hotel also needs to identify the supplier's work, staff time and resources required during the transition. Each item should have an owner, a pricing basis and a verifiable completion condition.

Define what a completed migration means

A property management system, or PMS, supports reservations, check-in, room status and accounting processes. Procurement scope should start with the business activities the hotel needs to continue performing.

In its analysis of hotel PMS migration published on 30 September 2026, Shiji highlights the operational dependencies behind existing systems. This is a supplier's industry observation. It identifies matters to investigate; it does not establish what a particular hotel's migration should cost.

The hotel can first specify minimum operational requirements: which in-house and future reservations must remain usable, which accounts need reconciliation, which interfaces must continue working, and how historical records will be accessed. Suppliers should then map those requirements to their deliverables. A commitment simply to bring the system live is insufficient as a shared basis for budgeting and acceptance.

Allow for data preparation and reconciliation

An offer to support data import needs further definition. Who exports data from the old system? Who handles formats and field mapping? Which records enter the new system and which remain accessible in an archive? Who corrects exceptions? These choices can affect workload.

Oracle's OPERA Cloud 26.2 data import documentation includes validation of the property's system configuration and relationships between records. This product example shows that transferring files is only part of migration. Specific rules must be checked against the hotel's chosen system and version.

The quote should specify the data scope, processing rounds and each party's responsibilities. If the quality of historical records is unclear, an appropriately prepared sample can be checked before the full workload is agreed. A requirement for the hotel to provide suitable data should not be treated as requiring no hotel resources. Front office may need to reconcile reservations, finance may need to explain balance differences, and departments may need to confirm what old and new fields mean.

Finance should distinguish supplier payments from internal staff time. Project participation may not immediately increase payroll, but it uses time otherwise available for regular duties. Where cover or overtime is needed, record the incremental expenditure separately. Explain the treatment of internal hours, existing salaries and additional labor costs to avoid double counting.

Check both ends of an interface and the complete transaction

Existing restaurant, payment, distribution, membership and finance systems may involve other suppliers. Establish whether each interface is applicable, who activates and configures it, who supports testing, and what the initial and recurring fees cover.

Consider a hypothetical restaurant charge posted to a guest's room account. The required checks include whether the charge reaches the correct folio, whether its amount and description are correct, whether front office can retrieve it, and whether finance can reconcile it. This is a test scenario, not a claim that any system has failed. It translates interface completion into an operational result the hotel can inspect.

If the restaurant system supplier's participation is excluded from the PMS quote, obtain a separate basis for its cost. If it is included, clarify who pays and coordinates the work. For reports requiring changes, establish whether the work involves standard configuration or separate development, and who will maintain it. These checks can reduce disagreements about scope after signing.

Make time available for training

Supplier-provided training does not mean the hotel has allocated staff time to learn. Front office, reservations, housekeeping and finance perform different tasks. Training should cover the relevant roles and shifts rather than only a demonstration for a few supervisors.

Check whether the scope includes the training format, participants, practice environment, initial live support and later refresher training. The hotel should decide who can step away from duties, who covers their work and how practical competence will be assessed.

Checks can follow actual role requirements, such as modifying a reservation, moving a guest to another room or correcting an account in a practice environment. If staff can only follow a demonstration and cannot handle exceptions, further support time is needed. Course completion and the ability to work independently should be recorded separately.

Budget for the transition and define when the old system can close

Check whether existing terminals, networks and related equipment suit the new solution. Obtain specific evidence for necessary changes and include them in the budget. Replacing the PMS should not automatically entail replacing all equipment.

Transition arrangements may include a short extension of the old system, historical record access, extra on-site support and staff time for reconciling records. The implementation plan should establish which resources are needed and for how long. Neither universal provision nor free provision should be assumed.

If parallel operation is planned, define which system holds the official operational record, what the other is checking and how duplicate processing will be prevented. If a single cutover is planned, specify which failed checks would delay go-live and the known costs of postponement.

Retaining the old system does not guarantee that the hotel can return to it at any point. Once new reservations, payments and operational records have been created after cutover, the project team must have established whether and how a return and reconciliation would work. A promise to switch back if problems arise does not replace a practical plan.

Check the actual contract for the old system's payment end date, read-only access, export assistance and subsequent support. Record retention and usage rights require confirmation against applicable requirements; a supplier's general description is insufficient.

Compare complete quotes using one worksheet

The general manager can ask finance to coordinate with front office, relevant departments and the system lead, recording each work item on a separate row. Use these fields: work and delivery scope, supplier charges, internal staff hours, transition resources, responsible party, completion and acceptance conditions, supporting documents, and unresolved matters. Mark unconfirmed costs as awaiting a quote rather than entering zero.

For data migration, specify the categories and period of records to be moved. State whether charges cover cleansing, testing and exception correction. Identify which departments must reconcile the data, and who will check it against which records. If a supplier says an item is included, ask for the corresponding quote or contract provision.

When comparing solutions, align the required operational results and cost review period before comparing initial expenditure, recurring fees and hotel resources. A quote including first-year support cannot be compared directly with one covering initial implementation alone. Align tax treatment and check charging units, renewal terms and payment milestones. List unresolved differences separately so the total does not conceal them.

The worksheet should also record changes: what scope has been added, why, the basis for the charge and who approved it. Work already included should not be charged again under a different description. Where requirements genuinely expand, the impact should be explained before work proceeds.

Decide what needs clarification before signing

Before signing, relevant business owners should confirm the deliverables, finance should confirm cost definitions, and suppliers should confirm their responsibilities. Where unresolved matters affect normal reception, accounting or core interfaces, complete necessary sample checks and obtain written scope or quotations before committing to a go-live date that depends on those conditions.

Small hotels do not all need a large migration project. A property with few system connections and a clear historical data scope may use a simpler plan. Complex operations, numerous interfaces or simultaneous migrations across several hotels need more detailed preparation. If the current system still meets business needs and expected improvements lack evidence, continued use and targeted adjustments should also be compared.

Clarifying migration costs before signing helps the hotel understand which operational results it is buying and what it must contribute to achieve them. Start the next procurement discussion with an existing quote. Identify work, costs and responsibilities that remain unspecified, then decide whether signing is justified.

Source: Shiji, Hotel PMS Migration Is Really an Exercise in Operational Discovery, 30 September 2026. https://insights.shijigroup.com/hotel-pms-migration-operational-readiness/

Source: Oracle OPERA Cloud 26.2, About Data Import. https://docs.oracle.com/en/industries/hospitality/opera-cloud/26.2/ocsuh/c_system_setup-importing_data.htm