A hotel PMS migration is a controlled transfer of operational records, not simply an upload of a guest spreadsheet. The aim is to prove that room types, future reservations, balances and access rights still make sense in the new system before the team relies on it. This checklist starts after you have selected a system and agreed the supported migration scope.
Define what will move
List each data set and its owner: room types, rate plans, future bookings, in-house stays, guest records and outstanding balances. Ask the receiving provider which fields and formats it actually supports. Keep unsupported history accessible through an agreed archive. Do not assume attachments, payment tokens, notes or third-party references can be transferred just because a reservation can be imported.
- Choose a cutover date and freeze window.
- Document source and destination fields, required formats and time zones.
- Agree how cancellations and amendments during the transition will be captured.
Clean and map before importing
Remove obvious duplicates using a documented matching rule, while retaining the original export. Standardise room-type codes, date formats, currencies and reservation statuses. A code such as DLX must map to the intended destination room type, including occupancy and inventory rules. Keep a mapping register so someone else can reproduce the transformation.
- Work from a protected copy; preserve the source export.
- Separate cancelled, provisional, confirmed and in-house reservations.
- Review missing contacts and duplicate guest profiles without inventing data.
Test a representative sample
Include a normal future booking, an amended stay, a deposit, a partially paid reservation, a group and a cancellation. Check individual records as well as totals. Matching the total number of bookings will not reveal a reservation assigned to the wrong dates. Ask a front-desk colleague to run the actual arrival and checkout workflow on approved test records.
- Compare counts by room type and arrival date.
- Compare deposit and balance totals using the same cutoff.
- Check references, notes and guest links on selected records.
Reconcile, cut over and retain a rollback route
Re-export the final change set at the agreed cutoff, import it through the supported process and reconcile again. Name the person who can approve the switch and the conditions that would stop it. Preserve read access to the old system or its authorised archive for the agreed period. A rollback plan must explain how new activity will be reconciled if the team returns to the previous system.
- Record unresolved differences with owners.
- Confirm staff access and training before the first live shift.
- Keep a signed reconciliation and a post-cutover support contact.
Practical worksheet
Download editable worksheet (CSV) ↓
Open the CSV in Excel, Google Sheets or another spreadsheet editor. Use fictional sample rows as examples and review the template before operational use.
Original editable planning resource. Examples are fictional; adapt and review before operational use.
| Data set | Source count | Imported count | Source balance | Imported balance | Difference | Owner | Resolution |
|---|---|---|---|---|---|---|---|
| Future reservations | Example: 120 | Example: 120 | Check dates and room types as well as count | Migration lead | Pending record checks | ||
| Deposits | Example: 80000 | Example: 79500 | 500 unresolved | Finance lead | Trace missing deposit reference |
Fictional example: both exports contain 120 future reservations, but the deposit totals differ by ₹500. The hotel pauses approval and traces one missing payment reference. A matching booking count is useful evidence, but it is not sufficient evidence of a successful migration.
Put the guide into practice
Use the reconciliation template during your test import and final cutover. Confirm the exact import/export paths with the chosen provider; no checklist can guarantee zero downtime or a universal migration route.
Explore hotel PMS software, read the related practical guide, or book a demonstration to verify the workflows for your property.