Overview: Move to iLogitix · WhatsApp move help
Step-by-step move plan
- Export data from your current systemBranch list, parties, rates, users — whatever Excel or CSV you can get.
- Match columns to iLogitix sample ExcelDownload our sample files. Put your data in the same columns. WhatsApp us a sample — we help match.
- Import masters, then open LRsFirst parties and rates. Then open bookings (in transit, at hub, OFD pending) so live work is not blank.
- Try one branch for 1–2 weeksMake real LRs. Check PAID/TO_PAY/TBB, carton scan, OFD, POD, billing, and who can see what.
- Move other branches one by oneWhen one branch is fine, shift the next. Keep old software only for old history if needed.
- Optional: link client or parent softwareClient can create booking and track LR + POD. iLogitix runs daily transport; accounts can stay elsewhere.
Bring data with Excel bulk import (masters + open LRs). For big company move, we can help mapping and training — ask on WhatsApp or demo.
What Excel import can bring
Masters
- Users
- Branches
- Stations
- Consignor / Consignee
- Billing customers
- Customer rates
- Customer TAT
- Bank / UPI accounts
- Packages
- Items
Open work
- Bookings (open LRs)
- Outward
- Unload
- OFD
- Delivery
Keep other software for accounts if you want
If accounts or a big client system must stay, use iLogitix for transport day work. Turn on Client Access so partners can create booking and pull track + POD — see Client booking & tracking. Booking and tracking for clients can be turned on per client after we enable Utilities in onboarding (ask us — not a self-buy button). Then you manage Client Access yourself.
Extra help for big companies
Bigger moves can include help matching columns, test import, final import, branch training, phone app rollout and client access setup. Ask on demo or WhatsApp if you need more than self-serve Excel samples.
Common questions
What should we import first?
Masters first — branches, stations, parties, billing customers, rates and users. Then open bookings and related outward/unload/OFD/delivery so live work is not blank.
How long to try one branch?
Most teams need 1–2 weeks: make real LRs, check freight types, carton scan, OFD, POD, billing and permissions before moving other branches.
Can we keep accounts software?
Yes. Run iLogitix for transport. Turn on Client Access so clients or parent software can create booking and get track + POD (we enable Utilities in onboarding if you ask).
Related guides
- LR software vs Excel — Compare LR software vs Excel for multi-branch transporters — branches, LR numbering, PAID/TO_PAY/TBB, POD, GST billing and controls before you switch.
- What to look for in a TMS — A buyer checklist for multi-branch transporters evaluating cloud TMS and LR software — freight types, OFD, POD, GST billing, and branch controls.
- Digital POD explained — How proof of delivery closes disputes, OFD loops, and billing — photo/signature POD linked to the LR instead of paper slips.
- PAID, TO_PAY & TBB — What TBB means on an LR/bilty, how it differs from PAID and TO_PAY, and how freight type connects to outstanding and GST billing.
- GST billing overview — Raise GST invoices from TBB LRs after POD — SGST/CGST or IGST from the same booking. Practical workflow, not tax advice.
- E-way bill extension — Why e-way bills expire on open LRs and how auto-extend, consolidated e-way bills and transfer to partner transporters save daily portal work.
- HRMS for transport — Attendance, leave and payroll for drivers, delivery staff and office teams — why it belongs in the same system as LR and e-way bill work.
- Own software vs old TMS vs iLogitix — Simple comparison — carton scan, label print, crossing, phone app, client track, and when to switch.