How do I switch hotel PMS without losing bookings or deposits?
Protect future reservations, guests already staying and money already paid. Use a trial import and a signed-off handover before your new system takes control.
To switch hotel PMS without losing bookings, agree what will transfer, rehearse the import and reconcile every reservation and deposit against a dated export. Choose one system to control live inventory at a time. Log changes during the handover, check balances before enabling payment requests, and keep the old system accessible. Proceed only when reception, finance and the connection owner have signed off; retain a documented fallback if checks fail.
Define exactly what must move
Build a migration register covering every future booking and in-house stay. Record the old PMS ID, channel reference, status, dates, room type, allocation, guests, nightly rates, extras, cancellation terms, payments and outstanding balance. Map old IDs to new IDs so amendments can reach the right reservation.
For current guests, separate charges already posted from remaining nights and extras. Agree how these become opening balances without duplicating revenue. Include room blocks, out-of-order rooms and group allocations when checking available inventory.
Assign one import route per booking source: supplier import, channel retrieval or controlled manual entry. Confirm how each route handles subsequent changes. Booking.com’s reservation retrieval documentation describes limits on information available for earlier bookings; do not assume reconnecting a channel restores every field or payment detail.
Prove that a paid deposit stays paid
A reservation, a recorded payment and a reusable payment method are separate items. Importing a deposit balance should record money already received, without charging the guest again. Retain the payment date, transaction reference, original processor and any refund history.
| Control | Old PMS record | New PMS acceptance check |
|---|---|---|
| Reservation | EX-1042; 18–21 November 2026; one double room | One linked booking; same dates, room type and status |
| Agreed stay total | 3 nights × £180 = £540 | £540; original nightly prices retained |
| Deposit received | £162 paid on 1 November; reference PAY-1042 | £162 linked to the booking as already paid |
| Still to collect | £540 − £162 = £378 | £378 outstanding; no repeated deposit request |
Fictional GBP guest totals, including any applicable VAT. No extras, refunds or tax calculation are assumed. These are accommodation amounts, not a RoomRaccoon quote.
Compare the gross guest payment with the processor record; a bank payout may be lower after fees. Saved cards need separate confirmation: Stripe’s payment-data migration process, for example, requires a coordinated transfer and ID mapping. It does not establish what your RoomRaccoon payment setup can import. Keep card numbers out of the reservation spreadsheet.
Rehearse the import and reconcile exceptions
Run a trial in an environment agreed with the supplier, with live messages, payment collection and channel updates disabled. Include direct and OTA bookings, a deposit, a partial refund, an amended stay, a group booking and an in-house guest.
- Compare booking counts by status and source, then room nights and occupancy by date and room type.
- Match individual deposits and outstanding balances as well as totals, separately by currency. Two errors can cancel each other out in a grand total.
- Test amendments, cancellations and payment reminders against imported records. Check group payment allocation and split bills where needed.
- Record each mismatch, its owner and its resolution. Re-run failed cases before approving the final import.
Keep historical invoice access and staff training on separate workstreams. They matter, but neither replaces proof that live reservations and balances reconcile.
Use this cutover-day runbook
Choose a quieter handover window with supplier support available. Record the cutover time and UK time zone. Replace each role below with a named person; one person may cover several roles in a small property.
| Stage | Accountable owner | Acceptance check |
|---|---|---|
| 1. Snapshot | Reception lead | Save final exports and arrivals lists. Freeze routine edits; log every new booking, amendment, cancellation and payment during handover. |
| 2. Import | Migration lead | Import the agreed sources once. Apply logged changes using booking IDs; retain rejected rows and the old-to-new ID map. |
| 3. Check stays | Reception lead | All expected bookings accounted for; dates, statuses, current guests, room blocks and nightly availability match. |
| 4. Check money | Finance lead | Future deposits, in-house balances and refunds reconcile per booking and currency. No duplicate collection or accounting export. |
| 5. Switch connections | Channel lead with suppliers | One authorised inventory writer. Validate room/rate mapping, restrictions, website booking and a channel booking, amendment and cancellation. |
| 6. Release and monitor | General manager | All gates signed; enable agreed automations. Reconcile the change log, arrival list and first payments again at shift-end. |
During the switch, monitor channel extranets and reservation notifications. Keep the change log running until delivery to the new PMS is confirmed. Do not let both systems send guest messages or independently update the same inventory.
Stop if a gate fails. Missing bookings, unexplained balances or incorrect sellable inventory block release. Before switching, continue in the old PMS and reschedule. After switching, pause affected sales or automations with the suppliers; reconcile new activity before any coordinated return to the old PMS. A fallback must include new bookings and payments, not simply restore yesterday’s export.
Make your RoomRaccoon migration testable
RoomRaccoon onboarding describes managed setup, reservation import, setup checks and training. Its advertised two-week programme is supplier guidance, not a guaranteed deadline for your migration or proof that all historical data transfers.
The UK hotel property management system page describes reservation management, payment status, split invoices and automated guest communication. Ask the team to demonstrate those workflows with an imported deposit and an in-house balance. Confirm the supported fields, package, payment arrangements and partner connections in writing.
Bring an anonymised booking like EX-1042 and your cutover checklist. Ask: “How will you preserve this £162 deposit, show £378 outstanding and prevent another deposit request?”
Discuss your PMS migrationQuestions before you approve the switch
Should I refund deposits and collect them again?
Do not make this the default migration method. Agree how existing payments will be represented and where later refunds must be processed. Confirm continued access to the original processor before closing accounts.
Can I run both systems during the change?
Keep the old system available for reference after cutover, with access restricted appropriately. Nominate one live operational record and one authorised inventory writer; avoid independent updates in both systems.
What if a guest changes their booking during import?
Log the source, booking reference, time and change. The migration owner must confirm it reaches the correct new record once, then recheck its price, balance and availability.
Sources and checks
Checked on 10 November 2026. The runbook and example are practical acceptance criteria, not a promise of automatic migration.












