A forty-eight room hotel in Harrogate switches property management system over a weekend in January because the new one is £180 a month cheaper. On the Monday morning the reception team can see every reservation for the next six months. What they cannot see is any reservation from the previous four years, because the migration brought across forward bookings and guest names and nothing else.
In March the owner tries to build a corporate rate proposal for the engineering firm that has stayed with them since 2019 and discovers he cannot prove how many nights they booked. He knows it was a lot.
The PMS is the spine, and everything else plugs into it
A property management system holds the room inventory, the rate plans, the reservations, the guest profiles, the folios and the night audit. Everything else in a hotel is an accessory to that.
The functions it has to perform are unglamorous and non-negotiable. It has to know how many of each room type exist and how many are sellable tonight, allowing for rooms out of order. It has to hold a rate calendar that runs at least a year forward, with different rates for different room types, different lengths of stay and different market segments. It has to open and close availability by channel. It has to post charges to a folio, split a bill three ways at eight in the morning and produce a VAT invoice that is correct. It has to run the night audit that rolls the day over and produces the numbers you manage on: occupancy, average daily rate and revenue per available room.
Then it has to talk to other things. The booking engine on your own website. The channel manager. The payment gateway. The accounts package. Possibly the door locks, the point of sale in the restaurant, the phone system, the guest wifi and the revenue management tool.
The dividing line between a system you will grow into and one you will fight is how it handles those connections. A two-way integration means the PMS and the other system both update each other automatically. A one-way integration means somebody in reception is retyping. A CSV export means somebody in reception is retyping badly, once a week, on a Friday.
Channel management is where the money leaks
The booking platforms each hold an allocation of your rooms and each sell independently of the others. Without a channel manager sitting between them and your PMS, availability updates are manual, which means they are late, which means you either sell the same room twice or protect yourself by holding rooms back and finishing the week with empty ones.
Some property management systems include a channel manager. Most integrate with one. What you are looking for is the direction and speed of the flow: availability and rates pushed out to the channels within seconds of a change, and reservations pulled back in automatically with the rate, the channel, the cancellation policy and the commission attached.
Two specifics are worth checking before you sign anything. First, whether the connection supports the rate plans you actually want to sell, including non-refundable rates, length of stay restrictions and closed to arrival. A connection that only carries a single flat rate quietly removes half of your pricing options. Second, how it handles the platforms' payment models, because a booking where the platform collects the money is a different accounting entry from one where you take the card, and a system that treats them identically will misstate your revenue every month.
If your restaurant runs a separate point of sale, the interface that posts a dinner to a room account is the one your guests notice. When it breaks, somebody writes it on a docket, and then somebody forgets.
The data you lose in a migration is the data you do not miss until later
Changing systems is the most dangerous thing you will do to a hotel that is not a refurbishment, and the danger is not the weekend. It is what you failed to bring across.
Work out in advance what you need and get it in writing from both vendors. Forward reservations with rates, deposits taken and cancellation terms intact. Guest profiles with stay history, preferences and the notes that tell you this guest always wants a quiet room. Company and agent accounts with their negotiated rates. Group blocks and function bookings, which sit in a different part of the database and are frequently missed. Historic statistics, because your pricing decisions for next October depend on what happened last October, and a year with no history is a year you are guessing at. Financial records for closed periods, which you have to keep anyway.
Two obligations sit on top of that. You must keep VAT records for six years, and if your PMS feeds your VAT return you are also inside Making Tax Digital, where the link between your records and your return has to be a digital link rather than a copy and paste. Since April 2022 that applies to all VAT-registered businesses. A migration that breaks the digital link is a compliance problem, not just an inconvenience.
The other is UK GDPR. Your guest data is personal data and you are the controller. Article 20 gives data subjects portability rights, but more practically, your contract with the outgoing vendor governs whether you can extract your own data in a usable format and how long they hold it afterwards. Read that clause before you need it. A vendor who supplies your data as a PDF report has technically complied and given you nothing.
Card data brings its own rules. The Payment Card Industry Data Security Standard governs how card details are stored, and a PMS that keeps card numbers in a free-text notes field is a breach waiting to be reported. Tokenisation, where the system holds a reference rather than the number, is the answer, and it is another thing that does not migrate cleanly.
The real cost is not the monthly fee
Price comparison between systems is almost always wrong, because the licence fee is the smallest component.
Add the implementation and data migration charge. Add training, including the training you will do again in six months when three of the people you trained have left. Add integration fees, which are frequently charged by both parties, and per-transaction fees on the booking engine. Add the productivity cost of a team that is slower for six weeks, which in a hotel shows up as longer check-ins at the worst possible hour.
Then look at the contract term and the exit. Multi-year terms with automatic renewal are common. So are notice periods that have to be served months before the renewal date. The clause that matters most is the one about what happens to your data when you leave, and whether there is a charge for getting it out.
Against that, the argument for changing is real when the current system is stopping you selling. If you cannot set a different rate for a Tuesday than a Saturday, cannot restrict length of stay over a festival weekend, or cannot see a booking curve, you are pricing blind and the system is costing you more than it charges.
Where this shows up in the game
Hotels arrive in Business Baron with the Hotels & Leisure Track, an add-on to the full game. The game gives you real financial statements, a profit and loss account, a balance sheet and a cash flow statement, and the history they build up is what makes next year's pricing a decision rather than a guess. That is the job a good system does for a real hotel.