Before switching hotel management software, a small hotel should check five things: that every record can be exported in a usable file, what happens to bookings and payments during cut-over, which integrations must be rebuilt, when support answers the phone, and how you leave the new contract. Score each vendor on one page.
Most comparison pages for this keyword are lists of products. This is a list of questions, because the switch usually goes wrong on the boring items: a deposit that did not carry across, a channel that stayed connected to the old system and double-booked a room, a vendor who answers emails only on weekdays. Work through the sections in order and you will have a scored sheet at the end.
Decide whether you really need to switch
Switching hotel software is a project, not an upgrade. Before you start, write one sentence naming the problem the new system must fix. "Our channel manager drops availability twice a month" is a problem. "The interface looks old" is not usually enough to justify the risk.
Then check whether your current vendor can solve it. Ask for a call with their support lead, describe the issue, and note whether a fix or a workaround comes with a date. Many small hotels discover that a setting, an add-on or a higher plan resolves the complaint. The guide to what software hotels use explains which job belongs to the PMS, which to the channel manager and which to an AI add-on, so you blame the right component.
Three reasons that justify the effort
- A repeat failure with a cost. Double bookings, rate mismatches or failed payments that cost money more than once.
- A missing feature you cannot bolt on. For example, no way to take deposits, or no link to your accounting package.
- A contract change. A price rise, a forced plan upgrade or notice that the product is being retired.
Data export and migration: the questions that decide everything
Your guest and booking history is the most valuable thing the old system holds, and it is the thing vendors least like to hand over. Check this before anything else, because a vendor that cannot export cleanly can hold you hostage.
What you need out of the old system
- Future reservations with arrival and departure dates, room type, rate, guest count and notes.
- Deposits and payments taken, linked to each reservation, so the new system does not ask guests to pay twice.
- Guest profiles, with marketing consent recorded as given or not given, not simply copied.
- Rate plans, restrictions and room types, including seasonal rules and minimum stays.
- Historical folios and reports for the current accounting period.
- Housekeeping and maintenance records if you keep them there.
Ask the old vendor for a sample export of 20 reservations in a spreadsheet-friendly file before you give notice. Open it. Check that dates are real dates, that names with accents survive, that notes are not cut at 255 characters, and that the deposit column is not empty.
A filled-in export test
Say a nine-room guesthouse exports its data and finds this when it opens the file in a spreadsheet. The figures are illustrative.
Check Result Verdict
Future bookings count 142 in system, 142 rows Pass
Deposits column Filled for 96 of 142 Ask why 46 are blank
Guest notes Cut off after 255 chars Ask for full export
Rate plans Not included in export Need manual rebuild
Marketing consent flag Missing Do not import contacts
Special characters in names Shown as ?? for 11 rows Ask for UTF-8 fileHere the guesthouse learns three things it would otherwise find out on the first arrival day: forty-six deposits that may be recorded elsewhere, truncated notes and no consent flag. Each one becomes a question for both vendors.
An AI assistant can help here without touching guest personal data. Paste only the column headings from the old export and the new vendor's import template, and ask it to propose a field mapping and list the headings with no match. Keep the real records out of the chat unless your plan and settings allow business data.
I'm moving a small hotel from one reservation system to another.
Here are the column headings of the old export: [paste headings only]
Here are the fields the new system's import template expects: [paste]
Map old to new in a table. Mark any new field with no source, and any old
column with no destination. Do not guess where the meaning is unclear.An illustrative reply, and what to do with it:
Old column New field Note
ArrDate arrival_date Direct match
Nights (none) New system calculates from dates
RoomCat room_type_code Codes differ: DBL vs D-STD, build a lookup
DepAmt deposit_paid Direct match
GuestNote internal_notes Check length limit on import
(none) source_channel No source column: fill by hand or default
MktOptIn (none) No destination: ask vendor before importTwo lines in that table are the real work: the room-type codes need a lookup list you write yourself, and the consent column has nowhere to go, which is a question for the new vendor before a single contact is imported. Check every "direct match" against five real rows too; an assistant matching headings cannot see that one system stores deposits including tax and the other without.
Downtime and cut-over: plan the week, not the day
Vendors talk about "go-live day". Small hotels live through a week. Ask each vendor to describe, in writing, what happens to three things during switchover: new bookings arriving from channels, guests already in house, and payments in flight.
A sensible cut-over shape
- Freeze changes. Two days before, stop editing rates and room types in the old system.
- Import and verify. Load future reservations into the new system and check ten of them by hand against the old one.
- Run in parallel. For a few days, enter any new booking in both, or have the front desk check arrivals against the old list.
- Move channels last. Reconnect each booking channel to the new system only when you have disconnected it from the old one, to avoid duplicate inventory.
- Keep the old system read-only for at least the length of your longest advance booking, or until the first accounting period closes.
Pick the date carefully. A quiet week reduces damage but does not remove it, because bookings for your peak season still have to arrive intact. Avoid cut-over around a public holiday weekend, a big local event or your financial year-end.
A realistic mistake and how it showed up
A twelve-room hotel switched on a Monday and reconnected one booking channel before disconnecting it from the old system. For two days both systems pushed availability to that channel; the last one to update won. On Wednesday the channel showed a room as free that was already sold, and the hotel had to walk a guest. The fix is the order in step 4: disconnect, then connect, and check the channel extranet after each change.
Integrations: list what is plugged in today
Write down every system that talks to your current software. Small hotels are often surprised by the length of this list: channel manager, payment terminal or gateway, accounting package, door locks, guest messaging, review requests, check-in app, website booking engine, revenue tool, and sometimes a spreadsheet someone built.
| Integration | Who maintains it today | Ask the new vendor | Cost to rebuild |
|---|---|---|---|
| Channel manager | Channel provider | Is there a certified connection, and who sets it up? | Ask |
| Payment gateway | Payment provider | Can stored cards or tokens move across? | Ask |
| Accounting package | You or your accountant | Which export format, and how often? | Ask |
| Door locks | Lock supplier | Is the lock system supported out of the box? | Ask |
| Guest messaging and check-in | Add-on vendor | Does the add-on connect to this PMS? | Ask |
Stored payment cards deserve their own question. Whether card tokens can move between systems depends on the payment provider and the rules around card data, and many small hotels find they cannot. Ask both vendors in writing and plan how guests with future bookings will re-supply their card details if needed.
If AI features are part of the reason you are switching, check that they work with the integrations you depend on. A messaging add-on that only connects to the vendor's own booking engine is no use to a hotel that takes half its bookings through channels. The comparison of hotel AI guest messaging tools shows what to look for, and the check-in app tutorial lists what those apps need from the PMS.
Support hours: test them before you sign
A reservation system fails on Saturday evenings, not Tuesday mornings. Ask which hours support covers, in which time zone, through which channels, and what the response target is for an urgent fault. Then test it: during the trial, send one genuine question by email and one by phone or chat at an awkward hour, and note how long each takes and whether the answer was right.
What to ask about onboarding
- Is migration done by the vendor, a partner or you? Is it included in the price?
- How many hours of onboarding or training are included, and are they live or recorded?
- Is there a named contact during the first month?
- What is the process and target time for a "system down" report on a weekend?
For a framework on what support and uptime promises should contain, the tutorial on uptime and support promises applies equally to hotel software.
Contract exit: read it as if you were already leaving
The most useful contract question is not "what do I get" but "how do I get out". Read the new vendor's terms for these points and write down the answers in the scoring sheet.
- Minimum term and renewal. Does it renew automatically? How much notice is needed, and in what form?
- Price changes. Can the vendor raise the price mid-term, and by how much?
- Data on exit. Can you export everything in a standard format on request, and is there a fee? How long is your data kept after you leave?
- Per-room or per-booking fees. Do fees scale with your volume, and do third-party channel connections carry their own charges?
- Add-on lock-in. If you buy AI features as add-ons, do they cancel separately?
The deeper reading is in the tutorial on keeping your data and prompts portable, and the one on what to do if a vendor shuts down is worth five minutes before you commit. A vendor that is confident in its product has no reason to make leaving hard.
A one-page scoring sheet
Print this and fill one in per vendor, including your current one. Score each line from 0 (fails or unknown) to 3 (clear written answer that meets your need). Weights reflect what hurts a small hotel most; change them if your priorities differ.
Criterion Weight Score(0-3) Weighted
Sample export opened and checked x3 ___ ___
Deposits and payments migrate x3 ___ ___
Written cut-over plan and timeline x2 ___ ___
Channel manager connection certified x3 ___ ___
Other integrations supported (list) x2 ___ ___
Support hours cover weekends/evenings x2 ___ ___
Support tested during trial x2 ___ ___
Onboarding hours included x1 ___ ___
Notice period and renewal terms clear x2 ___ ___
Data export on exit, no fee x3 ___ ___
Price changes capped or notified x1 ___ ___
Maximum 72 Total: ___Read the total with some judgement. A vendor scoring 60 with a zero on channel connection should lose to one scoring 52 with all threes in the "critical" rows. Mark any row where the answer was verbal only; unwritten promises count as a 1 at best.
A scored example
An illustrative case: a fourteen-room hotel compares its current system, Vendor A, with Vendor B. Vendor A scores 48: good support, but the export test failed on rate plans. Vendor B scores 55: certified channel connection, one included onboarding day, but a twelve-month term with 90 days' notice and a fee for full export. The hotel does not simply pick B. It asks B to waive the export fee in writing, and asks A whether the missing rate-plan export can be fixed. Only then does it decide. The sheet turned a vague preference into two specific negotiations.
The real cost of switching, beyond the subscription
Vendors quote a monthly fee. Your cost of switching is larger, and a small hotel should add it up before deciding. Include the old system's notice period (paying for two systems during overlap), any migration or set-up charge, staff hours for testing and training, the channel reconnection fees if any, and the revenue risk of a bad week.
A quick sum for a twelve-room hotel
An illustrative calculation. Suppose the new system costs $60 a month more than the old one, and the owner expects it to save two hours a week of manual work. Overlap with the old system adds one extra month at, say, $120. Set-up is $0 if the vendor migrates for free, or a few hundred if not. Staff testing and training takes about 16 hours across three people, at an internal cost of $20 an hour, so $320. The switch costs roughly $440 plus any set-up charge before the first benefit appears. Two hours a week saved is about eight hours a month, or $160 at the same rate, minus the $60 extra fee, a net gain of $100 a month. The payback is therefore a little over four months. If the hotel does not value the saved time, or the savings are doubtful, the sum says wait. Replace every figure with your own.
Staff, training and the first fortnight
The software is only as good as the front desk's confidence with it. Before cut-over, give each person who uses the system a short list of tasks to complete in the trial: make a booking, take a deposit, move a guest between rooms, check someone in and out, print or send a folio, mark a room clean. Anyone who struggles with a task tells you something about the vendor's design or your training.
A message to staff before go-live avoids the usual confusion about which system to trust. Here is an illustrative note you can adapt:
From Monday, the new system is the master record. The old system becomes
read-only; do not enter new bookings in it. If a guest quotes a booking you
cannot find in the new system, check the old one and tell [manager name]
straight away so we can fix the import. Any channel change goes through
[name] only until Friday. Questions: [phone] (not email) in the first week.Pick one person as the owner of the switch and give them authority to pause it. In a nine-room property that is often the owner; in a larger one, the general manager or a trusted receptionist. Without a named owner, small faults go unreported until a guest finds them.
What to check in the first fortnight
- Compare the day's arrivals list against the old system each morning for the first week.
- Check each channel's extranet once a day for rate and availability mismatches.
- Reconcile the day's payments with the gateway report, and the first week's totals against your bank.
- Ask housekeeping whether room statuses are accurate, since errors here spread quickly.
- Keep a shared list of every issue, with date reported and date fixed, and send it to the vendor.
Telling guests who have already booked
Most guests will not notice the change, but a few will if they receive a new confirmation email format, a different payment link or a changed check-in message. Decide before go-live whether to tell them. Where a guest has a pending payment or a pre-arrival form, a short note avoids a worried phone call.
Subject: A small change to how we handle your booking
Hi [first name], we've updated the system we use to manage reservations.
Your booking for [dates] is unchanged. You may receive a message from a
new sender address; it is genuinely from us. If anything looks different
from what you expect, reply here or call [phone].Send it only to guests whose experience will visibly change, and keep it free of any request for card details; tell guests plainly that you will never ask for card numbers by email.
Reports and records you must be able to reproduce
Hotels need certain records for accounting, tax and, in many places, guest registration rules. Ask both vendors which standard reports exist: daily revenue, occupancy, payments by method, cancellations, no-shows and an audit trail of who changed a booking. Confirm that you can produce last year's equivalents after migration. If the old system will be read-only for some months, note who will log in to it and how its licence is paid. Ask your accountant which reports they need, and show them the new system's samples before you sign; a sample that does not fit their workflow is a cost that appears every month. For legal or tax requirements specific to your business, take advice from a qualified adviser rather than relying on a vendor's summary.
Using the demo and trial properly
Salespeople demonstrate what works. Ask to be shown what you do. Give each vendor three scenarios from your real week and watch them done live, or do them yourself in a trial.
- A group of three rooms booked by one guest, with a partial deposit, one room later cancelled.
- A late arrival at midnight on a day when the front desk is unstaffed.
- A rate change for a local event weekend that must reach every channel within minutes.
Time each task and note how many clicks it takes. If a task you do ten times a day costs an extra minute, that adds up. Try the housekeeping view on a phone too, since cleaning staff may not use a desktop.
Where AI features fit into the decision
Many vendors now advertise AI replies, summaries or pricing suggestions. Treat these as a tiebreaker, not a reason to switch. Ask three things: which plan includes the feature, what limits apply, and whether guest data leaves the vendor's systems. Then test it on five real guest messages in the trial. If the AI add-on is the only thing tipping the decision, decide which AI job matters most to you first and test that one alone.
Finally, write the decision down: what you chose, the date, the notice you must give the old vendor and the date by which you must give it. If you would like help mapping your current set-up before you switch, that is what my AI implementation consultation covers.
Questions hoteliers ask before changing system
How long does a hotel software switch usually take?
It varies by vendor and by how clean your data is, so ask for a written timeline rather than trusting a sales estimate. Plan a parallel-running period of at least a week, and avoid cut-over in your busiest fortnight. Allow extra time for payment, channel and door-lock integrations, which are the usual causes of delay.
What data must I be able to export from my old system?
At minimum: future reservations with deposits taken, guest profiles with consent status, rate plans and room types, folio and payment history, and your reports for the last accounting period. Ask for a sample export before you cancel, and open it in a spreadsheet to check nothing is truncated.
Should I switch in the low season?
Usually yes, with one caution. A quiet month limits the damage if something fails, but future bookings for the busy season still have to move across correctly. Pick a week with few arrivals, and check that channel connections and deposits for later months have arrived intact.
Can AI help with the switch itself?
Yes, for the dull parts. A general AI assistant can compare field names between two exports, draft your cut-over communication to staff, and turn vendor answers into a scoring table. Keep guest personal data out of consumer chat tools unless your plan and settings allow it.
Further reads
- Channel Manager for a Small Hotel: Cost and What AI Adds — Cost of the channel connection you will need to move.
- Where Should a Small Hotel Start With AI? — A first AI step once the new software has settled.
- Hotel Maintenance Software or AI? Log, Prioritise and Chase Requests — Maintenance logging, another feature to test during a demo.
- Hotel Housekeeping Schedules: Allocate Rooms by Arrival Time With AI — Housekeeping scheduling to rebuild on the new system.
- What Does an AI Chatbot for Hotels Cost? Fees and Extras to Check — Fees and extras to check if the new PMS sells a chatbot.
- Is AI Dynamic Pricing Worth It for a Small Hotel? — Whether a pricing add-on is worth it after the switch.
- Reputation Management System for Hotels: Review Tools Compared — A buyer's comparison for hotels: review sources, reply workflow, alerts, survey tools, per-property pricing and the contract terms to settle first.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: no vendor-specific figures are used; verify every answer against the vendor's current contract, documentation and a sample export.