Import from another system
Upload your previous system's booking file exactly as it exports it, see row by row what will go in and what will not, and only then import.
What it solves
A hotel with two hundred future bookings does not change systems if it has to type them in. And it will not dare try if the first attempt writes something that cannot be undone afterwards.
You notice it in things like these
- Changing systems means typing in by hand everything that was already sold.
- The file goes up, something breaks halfway, and a hundred bookings are left half imported.
- The same file gets uploaded again just in case, and bookings and payments end up duplicated.
How it works
First it checks, writing nothing
Each row says whether it is ready, already imported, or which field is wrong and why: a date that cannot be read, a departure before the arrival, a stay that already ended, an amount paid above the total, a room type or a rate that does not exist. Only with that list in front of you do you decide to import.
It understands your system's file
Profiles for Cloudbeds, Mews, Oracle Opera and Little Hotelier with their English headers, plus the names other systems give their columns (folio, check-in, amount, deposit). If you do not say which system it came from, it recognises it from the file's own columns.
Dates are not guessed
2027-03-14, 14/03/2027, 14-Mar-2027 or Excel's serial number; month/day only for the systems that really use it. Amounts with $ and commas. A misread file does not fail: it imports the wrong booking, and that is not discovered until the guest turns up.
The old system's status rules
Cancelled, no-show and already departed bookings are skipped with the reason written out — they are not a file error, they are history that does not need bringing over. In-house ones come in confirmed, with a note to check them in at the front desk.
They come in through the usual door
Through the same path as an agency booking: they are not re-quoted — the guest already has their price — they reduce channel allotments, and they warn about overbooking without blocking the import. Whatever the guest had already paid is recorded as collected outside the platform, with no commission. And if the file's source matches one of the hotel's channels, the booking is linked to it.
Uploading it twice does not duplicate
The ones already imported from that system are skipped. That is what lets you upload the file, look at the result, fix three rows in Excel and upload the whole thing again without fear.
Where it lives in the panel
- Reservations & stays
- Reservations
- Reservations
The "Import" button is on the reservations list. The one for rooms is separate, under Rooms & rates → Rooms → Physical inventory.
What it needs first
Room types and rates already set up: the dry run flags as an error any row naming a type or rate that does not exist.
Room types
What it does not do yet
The limits, told by us
- Up to 1,000 rows per file, and only administration and management can do it. A bigger file gets split in two.
- What was already paid is recorded as a transfer with the reference "Importación" and the booking code, because the old system does not say how it was paid.
- What comes over is future bookings and rooms, not the full history: past stays and their invoices are not migrated.
Carry on here
Shall we walk through it with your hotel on screen?
Half an hour, your rooms and your rates, and whatever questions you have. No commitment and no card.