4 August 2026

How to Move Your Shortlet Off Spreadsheets and Google Calendar in One Weekend

A practical migration plan for Nigerian hosts still running bookings in Google Sheets, a WhatsApp thread and a notebook: what to move, in what order, what to keep, and how to switch without losing a booking.

The short answer: migrate in this order — units, then confirmed forward bookings, then cleaning blocks, then payments already received, then your channel calendars. Run the old spreadsheet alongside for one week without deleting it. The whole thing takes a weekend for a portfolio under ten units, and the single rule that makes it work is that you stop writing new bookings into the spreadsheet the moment you start. Two systems accepting new bookings is how you create the double booking you were trying to prevent.

First, the honest part: a spreadsheet is a perfectly good system for one unit run by one attentive person. If that is you, and nothing is going wrong, you do not need to read further. This is for the point where it stops working — and that point is more identifiable than most hosts realise.

The five failures that mean you have outgrown it

Not "spreadsheets are unprofessional". These are the specific, recurring ways they cost Nigerian hosts money:

  • The calendar lives in more than one place. Airbnb has a calendar. Booking.com has a calendar. Your sheet has a tab. Your agent has dates in their head. Nobody is wrong; they just disagree. The moment your sources of truth exceed one, double bookings are a matter of time rather than luck.
  • Payments are a colour, not a record. A yellow cell means part-paid. Part-paid how much, on what date, into which account, and was that the caution fee or the balance? Six weeks later, during a refund argument, the colour tells you nothing.
  • Cleaning is not on the calendar. Turnovers live in a WhatsApp thread with the cleaner, so the sheet says a unit is free when it is actually dirty until 3pm. You sell a night you cannot deliver.
  • Everyone sees everything, or nobody sees anything. You cannot give a cleaner tomorrow's schedule without also giving them guest phone numbers and revenue. So you do not share it, and you become the bottleneck for every question.
  • There is no history. Someone overwrote a cell. An agent insists the rate agreed was different. Without an audit trail, the loudest version wins.

If two or more of those are familiar, the spreadsheet is now costing more than it saves.

What migration actually involves

Most hosts imagine this as a data-entry marathon. It is not, because you do not migrate history. You migrate the future, and you archive the past.

Migrate Do not migrate
Your units and their real nightly rates Completed stays from previous years
Every confirmed forward booking Enquiries that never converted
Deposits already collected against those bookings Historical payments already reconciled
Scheduled cleaning and maintenance blocks Old cleaning rotas
Channel calendar connections Screenshots and notes you will never open again

Keep the old spreadsheet as a read-only archive. You will want last year's December rates when you set this year's, and export files have a way of not being there when you need them.

The weekend plan

Friday evening: set up the shape (about an hour)

  1. Create your organisation and add your properties.
  2. Add every unit — including the single-apartment ones. A one-apartment property still has one unit, because bookings attach to units, not buildings. Getting this right now prevents a restructure later.
  3. Set the real nightly rate per unit, plus any weekend or seasonal variation you actually apply.
  4. Add your cleaner and any agent, with their own access, so they see their work and not your revenue.

Saturday morning: forward bookings (one to two hours)

Work through every confirmed booking from today forward, in date order. For each one: guest name and phone, unit, check-in and check-out, agreed rate, and what has already been paid.

Two things to get right while you are here, because doing them now is free and doing them later is archaeology:

  • Record deposits as payments with their real dates, not as a note. A booking with ₦150,000 received on 3 August and ₦150,000 outstanding is a different object from a booking marked "part paid".
  • Where an agent sourced the booking, record the guest-facing price and your host rate separately. If a guest was quoted ₦140,000 on a unit you rent at ₦115,000, collapsing those into one number permanently corrupts your revenue reporting. Nookpal keeps agent price and host revenue as distinct fields for exactly this reason.

Saturday afternoon: cleaning and blocks (thirty minutes)

Add cleaning blocks between your existing bookings, plus any maintenance, owner stays or personal use. This is the step hosts skip and then wonder why the calendar still lies to them. A cleaning block is not an administrative note — it is a period the unit genuinely cannot be sold, and it belongs on the calendar with the same status as a booking.

Sunday: connect your channels (an hour, plus waiting)

Connect Airbnb, Booking.com and any other platform calendars. Then — and this matters — verify the sync in both directions before trusting it. Block a test date, confirm it appears on the platform, then remove it. Sync frequency is not instant on any platform, so understand the lag you are working with rather than assuming real time. Our guide to avoiding double bookings covers how iCal sync actually behaves and where it fails.

Monday onward: one week of parallel running

Keep the spreadsheet open but read-only. Every new booking goes into the new system only. At the end of the week, compare the two: anything in the spreadsheet that is not in the system is either a gap you need to fix or a habit you need to drop.

After a clean week, close the spreadsheet for good. Hosts who leave both live for a month do not end up with a safety net; they end up with two half-accurate calendars and the exact failure mode they were escaping.

One more thing to set up while you are in there: your cleaner. Nookpal gives them their own login showing only the units they are assigned and the turnovers due, which is what stops cleaning drifting back into the WhatsApp group the migration was supposed to end.

Five mistakes that make migrations fail

  1. Migrating during December. Never switch systems in your busiest month. Do it in the trough — for Lagos, the rainy-season months are ideal.
  2. Entering bookings but not payments. You end up with an accurate calendar and useless financials, then quietly go back to the sheet to answer money questions.
  3. Skipping the cleaner. If your cleaner is not in the system, turnovers stay in WhatsApp and the calendar keeps lying about availability.
  4. Not telling your agents. An agent still quoting from an old rate list will confirm dates you have already sold. Tell them what changed and how they now check availability.
  5. Trusting sync you have not tested. Verify in both directions before you rely on it.

One thing worth doing on the Sunday, while you are already in there: turn on your Nookpal property page. It costs nothing, it gives you a bookable link for Instagram and WhatsApp that reflects the calendar you have just built, and it means the migration ends with a new channel rather than only a tidier version of the old one.

When a spreadsheet is still the right answer

Worth saying plainly, because plenty of advice on this topic is just software marketing:

  • One unit, one channel, one person. A single Airbnb listing managed by its owner does not need a system. The sync problem does not exist and the audit trail is your own memory.
  • A unit you let a few weeks a year. The overhead outweighs the benefit.
  • Before you have any bookings. Get your first guests, learn what you actually need, then choose. Buying software to feel like a business is a way of avoiding the harder work of getting demand.

The trigger is not unit count on its own. It is the arrival of a second party — a second channel, a cleaner, an agent, a co-owner. Every additional person or platform who can change availability is another way for one calendar to become two.

If you take agent-sourced bookings, add one more step: invite the agent. A Nookpal agent gets their own login scoped to the units they are linked to and quotes their own guest-facing price, so their dates land on your calendar instead of arriving as a WhatsApp message you have to transcribe.

What you should expect to gain

Concretely, and in the order hosts usually notice them: the double-booking risk drops to near zero because there is one calendar; you can answer "what did unit 3 actually earn last month" without rebuilding it from a bank statement; your cleaner sees tomorrow's turnovers without seeing your revenue; and when an agent disputes a rate, there is a dated record instead of an argument.

Whether that is worth a weekend depends on how many of the five failures at the top of this article you recognised. If it was none, keep your spreadsheet. If it was four, you have probably already lost more than a weekend to them this year.

Is a spreadsheet good enough for managing a shortlet?
For one unit, on one channel, managed by one attentive person, yes. The problems begin when a second party can change availability — a second platform, a cleaner, an agent or a co-owner. At that point your calendar exists in more than one place, and double bookings become a matter of time rather than luck. Unit count matters less than the number of people and channels involved.
How long does it take to move a shortlet off spreadsheets?
About a weekend for a portfolio under ten units, because you migrate the future rather than the past. Set up units and rates on Friday evening, enter confirmed forward bookings and their deposits on Saturday morning, add cleaning blocks on Saturday afternoon, connect and test channel calendars on Sunday, then run the spreadsheet read-only alongside for one week.
Should I migrate my old booking history?
No. Migrate confirmed forward bookings, deposits already received against them, cleaning blocks and channel connections. Leave completed stays, dead enquiries and reconciled historical payments in the old file and keep it as a read-only archive — you will want last December's rates when setting this year's, and export files have a way of vanishing when needed.
What is the most common mistake when switching shortlet systems?
Keeping both systems live for new bookings. Two systems accepting bookings produces exactly the double booking you were trying to prevent. Stop writing new bookings into the spreadsheet the moment you start, keep it read-only for one week as a check, then close it. Migrating during December is the second most common mistake — switch during the low season instead.
Do I need a separate unit for a single apartment?
Yes, and setting it up correctly at the start saves a restructure later. Bookings attach to units rather than to buildings, so even a standalone apartment is one unit inside one property. Hosts who skip this because they only have one apartment usually have to rebuild their structure the first time they add a second.
When should I not move off a spreadsheet?
When you have one unit on one channel managed by yourself, when you only let the unit a few weeks a year, or when you have not taken any bookings yet. In that last case especially, get your first guests and learn what you actually need before choosing a system — buying software early is often a way of avoiding the harder work of generating demand.

Run your shortlets on Nookpal

One calendar across Airbnb, Booking.com, Hotels.ng and Travelstart. Agent commissions kept separate from your host revenue. WhatsApp-ready guest follow-ups. Built for Nigerian hosts.