From Spreadsheets to One System
Most UAE rental companies run on the same three things: a spreadsheet for the fleet, WhatsApp for bookings, and an accountant who receives a shoebox once a quarter. It works, right up to the point where it silently stops working — usually somewhere around car number fifteen, when nobody can say which car is free on the 14th without opening three chats.
The short answer: moving onto one system takes about four weeks of part-time work for a fleet of 10 to 40 cars, and it fails on data and sequence, not on software. Do the fleet and rates first, the booking routine second, the books third on a clean opening date, and measurement last. Switch during the summer trough, never in peak season.
Before day one: what to gather
The single best predictor of how this goes is whether you spend two hours collecting data before you touch anything. Assemble five things:
- The fleet list — every car with plate, Mulkiya (registration) expiry, insurance expiry and current odometer.
- One rate per car. Not three. Most fleets discover their daily rate exists in a spreadsheet, a WhatsApp broadcast and a printed sheet at the desk, and that the three disagree.
- Open and future bookings only — who has which car, from when, to when, at what price.
- Active customers with their documents, especially anyone on a monthly hire.
- An opening balance date for the accounts, agreed with whoever does your books.
Notice what is missing: historic bookings. You will be tempted to bring years of closed rentals across. Do not. They are consulted a handful of times a year, almost always for a dispute, and importing them is where the fortnight disappears.
Week 1 — the fleet, and one correct rate per car
Everything downstream reads from the fleet: availability, quotes, invoices, utilisation. So week one is not about learning software, it is about settling arguments over your own numbers.
Put every car in with its plate and its two expiry dates. The expiries matter more than operators expect — the point of holding them is that a system can tell you a Mulkiya lapses in eleven days, which a spreadsheet only does if somebody remembers to look. A car whose registration expires mid-hire is a genuinely expensive mistake, and it is entirely preventable.
Then set one rate per car per period. This is the week's real work. Expect to find cars quoted differently by different staff, monthly rates that were never updated after last season, and at least one car nobody can price at all because it has always been quoted "depending on the customer". Settle each one. If you want an outside reference while you do it, our Dubai rate guide gives median daily and monthly figures by segment from live listings.
By the end of week one you should be able to answer, without opening a chat: which cars do I own, what does each cost to hire, and what expires this month?
Week 2 — bookings and the handover routine
This is the week staff actually feel, so it is the week to run in parallel. Keep taking bookings however you take them now, and enter each one in the new system as well. Yes, it is double work for ten days. It is also the only way to find out what your process does that the software does not, while you still have a fallback.
Three habits to establish, in this order:
- Every enquiry gets recorded, including walk-ins and the ones that do not convert. Fleets that only log confirmed bookings never learn their conversion rate, and so never learn which cars are being asked for and refused.
- One handover routine. Photos, odometer, fuel, documents, signature — the same sequence every time, done on a phone at the car rather than retyped at the desk afterwards. Retyping is where the errors come from.
- Availability is checked in one place. The moment two people can promise the same car for the same weekend, the migration has failed.
Cut the old process only when a full week has passed with nothing appearing in it that did not also appear in the new one.
Week 3 — the books
Money moves last, and it moves from a clean date — the start of a month or, better, a quarter. Trying to migrate live bookings and historic ledgers in the same fortnight is the most reliable way to stall the whole project, because when something looks wrong you cannot tell which half caused it.
What changes here is less the bookkeeping than what you can see. A revenue total tells you money arrived. Proper double-entry books tell you which cars earned it, what they cost to keep on the road, and what you are owed — three questions a rental business has to answer and a spreadsheet answers badly.
The UAE-specific parts
- VAT. Registration is mandatory once taxable supplies pass AED 375,000 in a 12-month period, and voluntary from AED 187,500. The rate is 5%. Most fleets file quarterly — monthly filing starts above AED 150 million of turnover — and returns are due within 28 days of the period ending, through the FTA's EmaraTax portal. Tax invoices need your own sequential numbering, which is worth setting up before you issue the first one rather than after.
- Traffic fines. Fines follow the plate, so they arrive addressed to you and belong to whoever was driving. The workable routine is: check plates on a schedule, match each fine to the hire dates, and bill it on. Doing this monthly rather than quarterly is the difference between recovering fines and absorbing them.
- Salik. Tolls run at AED 6 per crossing at peak (06:00–10:00 and 16:00–20:00) and AED 4 off-peak, with 01:00–06:00 free and Sundays charged at the off-peak rate. Variable pricing has been in force since 31 January 2025, and 5% VAT was added to crossings during 2026 — confirm the current figures with Salik before you rebill, because this is the charge most likely to have moved since you last checked.
The recurring theme is that all three are per-car, per-hire costs that only become recoverable if they are attached to a booking while anyone still remembers who had the car. Our guide to the admin that eats a Dubai fleet goes into this in detail.
Week 4 — what to measure
By now the data is in and the routine holds. The last week is about deciding which numbers you will actually look at, because a dashboard nobody reads is decoration.
Four are enough to run a fleet on:
| Number | What it tells you | Act when |
|---|---|---|
| Utilisation per car | Days on hire ÷ days available | Any car below 60% for two months |
| Idle days | Revenue you cannot sell back | A car sits 14 days — reprice it |
| Enquiry conversion | Whether your price or your response time is the problem | Conversion falls while enquiries hold steady |
| Recovered vs absorbed fines | Whether the rebilling routine is real | Anything below 80% recovered |
Utilisation is the one that changes behaviour. Most operators can name their best car and their worst car; very few can rank the middle of the fleet, and that is exactly where the money quietly leaks.
What usually goes wrong
In rough order of how often it happens:
- Switching in peak season. October to April is when you need every hand on the desk. Move in the June-to-September trough, when a slow afternoon is an asset rather than a crisis.
- Nobody owns it. If the migration is everyone's side task it becomes nobody's. One person, a named finish date.
- Half-migrated rates. The worst failure mode, because nothing breaks visibly — you simply start quoting wrong numbers and only notice at month end.
- Staff never shown the new routine. People revert to WhatsApp under pressure. Ten minutes of walking through a handover on a real car is worth more than any written guide.
What it costs, and what it does not do
Every Drivaza partner starts on a 12-month free run of the starter plan, so the first year of running your fleet on it carries no subscription. Bookings we send you are charged on the margin between the net rate you set and the price the customer paid — you are never billed for a booking you found yourself.
Being straight about the limits, because they matter more than the feature list when you are choosing:
- It does not file your VAT return for you. It produces the figures; a human still submits them.
- It does not pay your fines. It finds them, matches them to a hire and bills them on.
- It does not replace your accountant, and you should not want it to.
- It will not fix a pricing problem. A car nobody wants at AED 3,000 is still a car nobody wants once it is in a database.
If you want the module-by-module view of what the portal actually covers, that lives on the rental software page. If you are still weighing software generally, what "free" actually gets you is the more useful read before this one.
Frequently asked questions
How long does it take to move a car rental fleet onto new software?
For a fleet of 10 to 40 cars, about four weeks of part-time work, and the constraint is your data rather than the software. Fleet and rates take a few days, the booking routine takes a fortnight of running old and new side by side, and the books take longest because they need an opening balance date. Fleets that try to switch in a single weekend usually end up running both systems for months.
What should I migrate first?
The fleet list, with plate, Mulkiya expiry, insurance expiry and one correct rate per car. Nothing else works until the cars and their rates are right, because bookings, invoices and availability all read from them. Resist starting with historic bookings — they are the least useful data you own.
Should I move my accounts over at the same time?
No. Move operations first and the books a fortnight later, on a clean opening balance date such as the start of a month or quarter. Migrating live bookings and historic ledgers at once is the single most common way these projects stall, because a mistake in either one is then impossible to isolate.
Do I need to import historic bookings?
Almost never. Import open and future bookings, and keep the closed ones in whatever you have now. Historic bookings are read a handful of times a year, usually for a dispute, and importing them is where weeks disappear for very little return.
What does it cost to run a UAE rental fleet on Drivaza?
Every partner starts on a 12-month free run of the starter plan, so the first year carries no subscription. Separately, bookings we send you are charged on the margin between your net rate and the price the customer paid — you are never billed for a booking you found yourself. See what the software covers.
What usually goes wrong?
Four things, in order of frequency: cutting over during peak season instead of the summer trough; nobody owning the migration, so it becomes everyone’s side task; half-migrated rates, which quietly produce wrong quotes; and staff who were never shown the new handover routine and keep using WhatsApp. All four are planning failures rather than software failures.