Why owners switch, and when not to rush
People switch a PMS when the current tool no longer fits the work. Typical signs: the calendar lives in one person's head, WhatsApp bookings are written on paper, Traveloka or tiket.com is still updated by hand, support is in the wrong language or time zone, or the bill is hard to predict. If you are still deciding what you need, start with how to choose a PMS for a small hotel in Indonesia (opens in new tab), not with a cutover date.
Do not rush the switch in your busiest week, or on a public holiday when OTAs and banks are slow to answer. Pick a quieter midweek window. Give yourself at least one full week to set up and test, longer if you have many room types or more than a handful of channels. The go-live date is the day the new system starts selling. Until that morning, the old system remains the source of truth.
Write down why you are leaving. That list keeps the project honest. You are not looking for a perfect tool. You are looking for a system your staff will actually open at 07:00, in the language they use, with the channels you already sell on.
What to export before you leave
Export first, while you still have access. Do not assume the old vendor will keep a login open after you cancel. Save copies in a folder that more than one person can open.
| What to export | Why you need it | Typical form |
|---|
| Future bookings (arrivals from go-live onwards) | So the new calendar is not empty on day one | CSV or spreadsheet: guest name, room, check-in, check-out |
| Guest contact details on those bookings | So you can still message arrivals | Email, phone, nationality if you have them |
| Channel and booking reference | So you can match an OTA ticket to the stay | Channel name plus the source booking id |
| Amounts, status, guest count, notes | So special requests and payments are not lost | Optional columns; keep them if the file has them |
| Room and rate list | So the new system maps rooms the same way | Room names, room types, occupancy, rates, restrictions |
| Channel list | So no OTA is forgotten | Every OTA, the direct website, and any manual channels |
| Photos of the live calendar and rate plan | Proof of what was open on export day | Screenshots, dated |
A usable booking file needs at least the guest name, the room name, the check-in date and the check-out date. Those names and contact details are personal data. Indonesia's Personal Data Protection Law (UU No. 27 of 2022) (opens in new tab) is a good reason to keep the export in a folder only the people doing the switch can open, and to delete stray copies when the new calendar is checked. If your current system can export a CSV or TSV, use that. If it can only print a PDF, copy the future stays into a spreadsheet with those four columns. Extra fields help, but those four are what you cannot invent later.
Also print, or photograph, the next two weeks of the calendar. If a row in the file looks wrong, you will want that picture. Keep a list of bookings taken after the export, in a simple log: date taken, guest, room, dates, channel. You will add those by hand before go-live.
A simple switch plan in six steps
Treat this as one sequence. Skipping a step is how rooms get sold twice.
1. Pick a go-live date and a single owner. One person (you, or a manager) owns the checklist. Tell staff the date. Do not change it twice in the same week.
2. Map rooms and channels. Write each old room name next to the new room name. They must match what guests already booked. List every channel, including Traveloka, tiket.com and Agoda (opens in new tab), Booking.com, Airbnb, Expedia, your own website, and any channel you still update by hand.
3. Export, then freeze what you can. Take the export above. After that, log every new booking in both the old system and the switch log.
4. Set up the new system while the old one still sells. Build rooms, rates and restrictions in the new system. Do not connect OTAs yet. Check the room names against the mapping. The channel manager setup checklist (opens in new tab) is the right companion for this step.
5. Import future bookings and check them one by one. Load the file into the new system. Then walk the next 14 days, booking by booking, against the old calendar and your switch log. Fix mismatches before any channel is connected.
6. Connect channels, test, then go live. Connect OTAs to the new system only when the calendar is complete. Test a last-room close if you can. On go-live morning, confirm the new calendar matches the old one, then stop selling on the old system. Do not leave both systems connected to the same OTA.
The last point matters more than any other. Two live calendars for the same rooms is how a double booking starts. If you want the background on that risk, read how to stop double bookings (opens in new tab).
A worked cutover: eight rooms in Yogyakarta
This example is made up, so you can see the hours involved. It is not a real property.
Rina runs an eight-room guesthouse in Yogyakarta. She sells on Booking.com, Agoda, Traveloka and WhatsApp. Her current system holds the calendar, but Traveloka is still opened in a separate tab. She picks Thursday 07:00 as go-live, and starts the Tuesday of the week before.
On Tuesday she exports 41 future bookings to a spreadsheet. Four columns are complete for every row. Twelve rows also have a phone number and a Booking.com reference. She photographs the calendar for the next two weeks. She writes the room mapping on one page: "Deluxe 1" stays "Deluxe 1".
On Wednesday and Thursday the new vendor sets up the eight rooms, the rates, and the four channels with her, by video call. No OTA is connected yet. They import the 41 rows. Two check-out dates were typed as the same day as check-in. They fix those before going further.
On Friday she walks the next 14 days line by line. One WhatsApp booking from Thursday afternoon is in her switch log but not in the file. She adds it by hand. She asks for a test: with one room type left at one, a test hold on the new system should close that room on the connected channels. They schedule the real connections for Wednesday afternoon.
Wednesday afternoon, after a quiet lunch service, the channels are connected. She checks that a closed date on the new calendar is also closed on each extranet. Thursday at 07:00 she compares both calendars one last time, then signs out of the old channel connections. From that morning, new WhatsApp bookings are entered only in the new system, straight away.
The work is a few focused sessions, not a month of nights. The part that takes care is the line-by-line check, not the file itself.
How to reconnect OTAs without a double booking
Reconnect means: the new system is now the place that sends availability and rates to each channel. Until you are ready, leave the old connection in place and do not add a second one.
Do this in order:
- Finish the import and the 14-day walk-through.
- Connect one channel first, usually the quietest, and watch it for a short window.
- Confirm a closed date is closed on that channel, and an open date is open, with the right rate and minimum stay.
- Then connect the remaining channels, including local ones such as Traveloka and tiket.com, which sometimes need a different setup path than Booking.com or Airbnb. For Traveloka, start from the official TERA partner page (opens in new tab) (the extranet Traveloka uses to manage rates and availability, and which can connect to a channel manager).
- Only after every channel is selling from the new system, disconnect the old one.
If a booking arrives on an OTA while you are mid-switch, enter it in the old system (still the live one) and add it to the switch log. Before go-live, copy it into the new system. Do not try to invent a period where both systems sell the same room on the same channel.
Availability should lock on all connected channels when a booking is taken in the new system. Guest details can arrive later, once payment on that channel is confirmed. The room must already be held. The only double-booking risk you should still watch is a WhatsApp, phone or walk-in booking that is not entered straight away.
Common mistakes when you switch PMS
- Connecting OTAs before the new calendar is complete. Empty dates look like open rooms.
- Leaving the old and new systems connected at the same time. Two systems cannot share one room safely.
- Importing only names, not rooms and dates. A booking without a room is not a booking on a calendar.
- Skipping WhatsApp and walk-in stays because they were never in the old export.
- Changing room names on the new system so they no longer match what guests booked.
- Going live on a Saturday of a long weekend when you cannot reach anyone for help.
- Assuming the vendor can pull data straight out of the old PMS. Many tools, including Kiyo, import a file. They do not log into the system you are leaving.
- Cancelling the old login before you have the export and the screenshots.
How Kiyo handles a switch
The switch into Kiyo is a shared setup, not a hidden transfer from the system you are leaving. A Kiyo teammate builds your rooms, rates and channels with you. In Bali, we can visit the property to show you. Outside Bali, we do it by video call. You keep taking bookings on your current system until go-live.
Booking import is a file, not a hidden pipe. You can import existing bookings from a CSV or TSV file. The required fields are guest name, room name, check-in and check-out. Optional fields include guest email, phone and nationality, channel, total amount, status, number of guests, special requests, notes, a source booking id and the date booked. The importer can recognise common export headers, including files from Airbnb, Agoda and Hostelworld. There is no direct importer that logs into another PMS and pulls the data for you. Future OTA bookings after a channel is connected arrive through the channel connection itself.
Channels, in the same setup. Kiyo connects to 75+ OTAs, including Traveloka and tiket.com. When a room is booked, it locks on all connected channels within milliseconds. Guest details may follow later, once payment is confirmed; the room stays held. After go-live, WhatsApp, phone and walk-in bookings are entered in Kiyo at the time they are taken, so they lock the same way.
Support during the week you switch. Each property gets its own WhatsApp group with the Kiyo team. Normal support runs from 07:00 to 19:00 WITA. For system failures, support is there 24 hours a day. Staff screens are available in Bahasa Indonesia. If a connection to an OTA fails, your property is told and the Kiyo team gets an alert too.
Plans start from Rp40k per room per month (opens in new tab). Free setup, pay from go-live, 14-day money-back guarantee. If you want a broader fit check first, read is Kiyo right for your property (opens in new tab).
Frequently asked questions
You can keep the old system as the live one while the new one is being set up. Do not connect the same OTA to both systems at once. On go-live day, the new system becomes the only one that sells.
Only if you import them, or if they arrive again through a connected OTA. Kiyo imports a CSV or TSV file. It does not reach into another PMS on its own. Check the next two weeks by hand after the import.
Enter it in the system that is live at that moment, and add it to the other one if you have not yet switched. After you disconnect the old channels, enter it only in the new system.
Usually you keep the same listings and change which system sends rates and availability. You still need to map each room correctly. Follow the channel manager setup checklist (opens in new tab) and the Traveloka, tiket.com and Agoda connection guide.
For a property with a handful of room types and a few channels, plan at least a week of setup and checks, with go-live on a quiet weekday. A larger room list or a messy export needs more time. The vendor can set the system up with you; the line-by-line check is still yours.
Copy future stays into a spreadsheet with guest name, room, check-in and check-out. Add phone numbers and channel references if you have them. It is slower than an export, but it is enough to build the new calendar.
Add Kiyo to your preferred sources on Google