How to Import Old Bookings to Channel Manager
If you already have existing reservations, you can import them into NOBEDS to correctly block availability and prevent overbookings.
Step 1 — Open Import Tool
Go to: Features → Import. This section allows you to upload previous bookings using an Excel file.
Step 2 — Select Room or Property
Before uploading your file, you must select the room or property where bookings will be imported. Choose the correct apartment, room, or rental unit from the dropdown list.
Important: bookings will be added only to the selected room. If the wrong room is selected, availability may be blocked incorrectly.
Step 3 — Download Excel Sample File
Click Import.xlsx to download the official import template. The system accepts only Excel files that follow the required column structure, naming, and order.
Step 4 — Prepare Your Booking Excel File
Your Excel file must contain specific fields like checkin, checkout, nights, guests, price, total, paid, name, address, email, phone, comment, referral, and referral_id.
Important rules:
- Use date format YYYY-MM-DD
- Do not rename columns
- Do not change column order
- Numbers must contain only numeric values
- Leave optional fields empty if data is unavailable
Step 5 — Upload Excel File
After preparing the file: Click Browse, select your Excel file, and press Import. The system will automatically create bookings and block availability.
Step 6 — Verify Imported Bookings
After successful import, bookings will appear in your Calendar and availability dates will be blocked automatically. Channel Manager will update across connected OTAs.
Best Practice Recommendation
Before connecting Booking.com, Airbnb, or other OTAs: Import all existing future reservations first, check calendar availability, and only then activate OTA synchronization.
Common Import Issues
- File does not import — usually caused by incorrect column order or date format.
- Bookings do not block dates — most commonly the wrong room was selected before import.
- Duplicate bookings appear — happens when the same referral_id already exists in the system.