GATE 01
Scope approved
The project owner, included workflows, suppliers and target cutover window are recorded.
Free checklist · 2026
Booking-system migration checklist.
Plan the move from legacy accommodation software without losing future bookings, balances or the operating context your team needs at check-in.
62 working actionsSix migration phasesEight printable A4 pages
Keydesk operator tool
Migration checklist
01Scope the move
02Inventory and protect data
03Configure the new system
04Map integrations and channels
05Import, test and reconcile
06Train, cut over and stabilise
Plan · Test · Reconcile8 pages
What is inside
Six phases, from first decision to final sign-off.
The checklist turns a vague software change into owned, testable work. Use it with your current supplier, shortlisted vendor, finance lead and frontline team.
- 01
Scope the move
Name the decision-makers, define what is in scope and agree what success looks like before anyone touches live data.
- 02
Inventory and protect data
List the records that must transfer, preserve untouched exports and agree secure handling for working files.
- 03
Configure the new system
Build inventory, prices, restrictions, payments, messages, permissions and reports from written decisions.
- 04
Map integrations and channels
Give every connection an owner, test case, support route and place in the cutover sequence.
- 05
Import, test and reconcile
Compare record counts and values, sample difficult bookings and prove that the operation can run.
- 06
Train, cut over and stabilise
Write the runbook, train real roles, verify the first live booking and monitor day-one exceptions.
The non-negotiable
An import is not the finish line.
A migration is ready only when the numbers and the working day agree. Reconcile these three views before the new system becomes the source of truth.
Future bookings
Compare counts, values and sampled records across the next 7, 30, 90 and 365 days.
Money
Reconcile booking values, deposits received, refunds and outstanding balances to the source totals.
Live operation
Prove arrivals, amendments, payments, messages, reports and exception handling with real tasks.
A milestone plan
Do not promise a date before you know the work.
Data quality, pricing complexity, integrations and team availability change the timeline. Use evidence-based gates instead of an arbitrary number of weeks.
GATE 02
Test import signed off
Counts, values, sampled bookings and priority workflows have passed agreed checks.
GATE 03
Cutover ready
The final sequence, booking freeze, channel changes, contacts and contingency are current.
GATE 04
New system primary
Live booking routes work, balances reconcile and the operating owner gives written sign-off.
Move or archive?
Move what the operation needs. Preserve what the business must retain.
Copying every historic field can add risk without improving day one. Agree the purpose, source and owner of each dataset before mapping it.
Usually needed live
- Future bookings and status
- Guest details needed to serve the stay
- Deposits, balances and payment references
- Accommodation, pricing and restrictions
- Operational notes and requirements
May remain archived
- Completed historic stays
- Old message and audit history
- Superseded prices and configuration
- Records held for finance or service needs
- Material with an agreed retention period
This is an operational distinction, not legal or accounting advice. Confirm your retention, access and deletion obligations before deciding what to archive.
Cutover runbook
Write the exact sequence before the busy window starts.
Your cutover plan should be clear enough for a trained team member to follow under pressure, including who can pause the move.
- Step 01
Freeze
Record the last booking or transaction included in the source export.
- Step 02
Import
Load the final file and repeat the approved count, value and spot checks.
- Step 03
Switch
Update the Book Now route, reconnect live channels and verify availability.
- Step 04
Prove
Complete a mobile booking and confirm the payment, message and operating view.
- Step 05
Monitor
Run scheduled day-one checks and keep the contingency route available.
Questions before you move
Migration checklist FAQ
What should a booking-system migration checklist include?
It should cover scope and ownership, source-data exports, configuration, integrations, test imports, booking and balance reconciliation, staff training, cutover steps, contingency and post-launch sign-off. Each action needs an owner and a measurable result.
What data should move to a new accommodation booking system?
Most operators need future bookings, guest details needed to serve those stays, deposits, balances, accommodation, pricing and essential operational notes. Historical records may be migrated or retained in an accessible archive depending on operational, accounting and legal needs.
How do you avoid losing bookings during a PMS migration?
Keep an untouched source export, use stable booking identifiers, run a test import and compare record counts and values. Before go-live, spot-check future arrivals across several time windows and confirm which final booking or transaction was included in the cutover export.
Should the old and new booking systems run in parallel?
A controlled overlap or read-only archive can be useful, but two editable sources create ambiguity. Define which system is the source of truth at every stage, how new bookings are handled during the cutover window and when the old system becomes read-only.
How long does a booking-software migration take?
There is no reliable fixed duration. The timeline depends on data quality, future-booking volume, inventory and pricing complexity, integrations, supplier availability and the time your team can give to testing and training.
How should personal data be transferred?
Use an approved secure method, restrict access to the smallest practical project team, retain an untouched backup and agree when working files will be deleted. Confirm the legal and information-security controls appropriate to your own business.
Can Keydesk help with a migration?
Keydesk offers hands-on early-access setup for suitable independent accommodation operators. We review the files and processes you use today before agreeing what can move and how it should be checked. Online travel agency connections are not yet available.
A second pair of eyes
Planning to replace your booking system?
Tell us what you use today. For suitable early-access operators, Keydesk can help map the setup, future bookings and checks needed for a workable move.
Download the checklist first Migration consultation
Early access is hands-on and case by case. Joining the list does not commit you to a contract.
Be first to hear when beta opens. No spam. Just occasional updates as we build.