The hardest part of digitising an Indian transport office is not the software. It's the change. Your munshi has been doing things a particular way for ten years. Your accountant has a workflow. Your dispatcher has muscle memory. Drop a "modern TMS" onto that ecosystem on a Monday morning and by Friday everyone is back on WhatsApp because the new thing is harder than the old thing.
This article is a four-week migration plan that we've run, in various forms, with 1,200+ Indian fleets. It works because it doesn't ask anyone to change everything at once.
Before you start: an audit of what's actually there
Most fleet owners think they know what their office does. They don't. Spend half a day sitting at the dispatch desk and write down every workflow you see. The typical list looks something like:
- Driver WhatsApp group: trip status updates, fuel slip photos, complaints
- Customer WhatsApp groups (one per major consignor): truck location queries, dispatch confirmations
- Munshi's bilty register: handwritten LR numbers, freight, party names
- Accountant's Excel: party-wise outstanding, freight collection
- Operations Excel: daily trip plan, driver assignment
- Owner's notebook: rate negotiations, advance approvals, "do not load" list
- Tally / BUSY: GST invoices, party ledgers (often a separate accountant's job)
- Random folder on a laptop: scanned RC books, DLs, insurance certificates
If your audit looks like this, you're normal. Now you have a baseline.
Week 1: the dispatch desk only
Do not try to migrate everything at once. Start with one thing: the dispatch desk. Move the daily trip plan from Excel/notebook into SkyRocket. Train one person (your dispatcher) on one workflow (creating a trip, assigning a driver, generating a bilty). That's it.
Leave the WhatsApp groups running. Leave the accountant on Excel. Leave the munshi's bilty register active as a backup. The goal in week 1 is not transformation. It's to get one workflow, owned by one person, working reliably on the new system.
Most failures we see come from owners who try to migrate everything in one weekend. Don't.
Week 2: bilty / LR generation goes digital
Once the dispatcher is comfortable, the munshi shifts from handwritten bilty to system-generated bilty. The system pulls party data, vehicle data, and trip data automatically. The bilty prints on the same letterhead the munshi has been using for ten years. Nothing changes about the physical workflow — the driver still gets a printed bilty as he leaves the gate. Only the source changes.
The munshi keeps his handwritten register for the first two weeks of this transition. By the end of week 2, he'll find he hasn't opened the register in days. That's the moment to retire it. Don't retire it before then.
"My munshi had a register going back to 1994. He cried a little when we stopped using it. Two weeks later he told me he never wants to write a bilty by hand again."— Deepak Mehta, MD, Mehta Logistics · Indore
Week 3: the customer side
This is the high-value week. You replace customer WhatsApp queries with a tracking link. When a consignor asks "where's my truck?", instead of your dispatcher calling the driver and reporting back, you send a one-line WhatsApp: "Live tracking: bharatfleet.in/t/4471". The customer clicks. Sees the truck. Stops asking.
This single change saves a dispatcher 1–2 hours a day at a 30-truck fleet, and dramatically improves your relationship with customers because they stop feeling stonewalled.
Some customers (especially older ones, especially those over 60) will resist. Send them the link anyway, then call them. By the third or fourth trip, they'll start using it themselves.
Week 4: accounting integration
This is the most technical week and the one where you might want SkyRocket's onboarding team in your office for a day. Connect the system to your Tally / Zoho / BUSY. The two-way sync pushes bilties and freight collections to your accountant's ledger automatically. Party ledgers, outstanding ageing, and GST data flow without anyone typing.
The first week of the sync, your accountant will double-check every entry. By week two of the sync (so week 5 of your migration), he'll stop checking. By week 4 of the sync, he'll wonder how he ever did the job without it.
What the office looks like at the end
By the end of month one, the typical SkyRocket migration produces this end state:
- Driver WhatsApp group still exists but is used for non-trip chat only
- Customer WhatsApp groups: removed (replaced by tracking links + auto status updates)
- Munshi's bilty register: retired
- Accountant's Excel: replaced by SkyRocket → Tally sync
- Operations Excel: replaced by SkyRocket dispatch board
- Owner's notebook: still exists, because some habits are sacred
- Tally / BUSY: still exists, now fed by SkyRocket
- Random folder: replaced by SkyRocket's document vault, DigiLocker-integrated
The munshi is still the munshi. The dispatcher is still the dispatcher. The owner is still the owner. The roles haven't changed. The tools have.
What not to do
Do not buy a TMS, hand the login to your munshi, and walk away. Adoption requires hand-holding for the first 4–6 weeks. If your vendor doesn't have a dedicated onboarding team that comes to your office, sits with your staff, and runs the first 100 trips with them — pick a different vendor.
Do not migrate during your busiest month. Pick a slower month. The 10–15% extra time the dispatcher needs in week 1 will hurt if you're already at peak.
Do not fire your munshi after migration. He becomes the most valuable person in the office because he now has time to chase outstanding, follow up customers, and actually manage the business. The fleets that fire post-migration regret it within sixty days.
If your fleet is between 10 and 80 trucks and you commit to following this four-week plan with our onboarding team, we'll have your office running fully on SkyRocket within 30 days — without losing a single trip, missing a single bilty, or upsetting a single long-time employee. If we don't, we refund month one. That offer has been on the table for two years and we've honoured it three times. All three were our fault, all three got refunds, all three are still customers today.
To start your migration, book an onboarding call ↗. We'll send a team to your office within a week.