Switching
The reason operators stay on a system they dislike is the week of retyping they imagine. There is an importer for that, it already reads the exports the systems you are most likely on produce, and every import can be reversed in one action.
Where you are coming from
A named profile knows the shape of that system's export, so the columns land in the right places without you explaining them. When there is no profile, the mapper reads your file and proposes one.
The systems operators most often move off have a purpose-built profile here: their booking lists, reservations, contacts, invoices, drivers, vehicles and pricing exports are read as they come out, with an iCal file for work already in the diary. Reservations arrive as bookings with the client already attached, not as a flat list to re-link by hand. Tell us what you are on and we will say plainly whether yours is one of them.
The generic profile takes clients, drivers, vehicles, rate cards, distance tiers, partners and bookings. Only the client file is required - bring the rest when you are ready, or never.
If the columns match nothing on this page, hand the file over as it is and let the AI mapper propose the column mapping. You review what it suggests before a single row is written.
What comes across
Past bookings matter more than people expect - they are what makes a client's history, their usual routes and their rates worth anything on day one.
The safety net
Drop the files in. Nothing is written to your account at this point - the upload is a staging area, not a commit.
Columns are matched automatically and you correct whatever it got wrong. The preview tells you what would be created before anything is.
Rows are written, tagged with the job that created them. Bookings go last, so the clients, drivers and vehicles they point at already exist.
One action deletes every row that import created, in a single transaction, in the right order for the foreign keys. Not a restore from a backup - an undo.
The honest part
There is no button that reads your old vendor's database directly - every route in starts with a file they let you export, and a system that will not export your data is a problem no software can solve for you. We do not migrate email archives, attachments or documents. And a switch is not free of effort: the importer removes the typing, not the decisions about how you price.
Questions
The upload and the mapping are the work, and both are measured in minutes rather than days. Most of a switch is not the import at all - it is deciding your vehicle classes and your rates, which you can do with one class and one rate on day one.
Roll it back and try again. Every row an import creates is tagged with that job, and the rollback removes exactly those rows and nothing else. You can get it wrong twice and still be where you started.
Yes, and most operators should. Connect the mailbox, quote the enquiries that arrive from that day forward in 4fleet, and let the old system finish the work already in it. Nothing forces a cutover date.
Then export whatever it gives you and use the AI mapper - it is built for exactly that case. If your export is a common one we will add a named profile for it, because the next operator leaving that system will need it too.
The account owner, and only through the app. It is not exposed to API keys, and the company it writes into is taken from your session rather than from anything in the file.
Your email history stays where it is - though once the mailbox is connected, the thread of any client who writes to you again is picked up from your own inbox. Documents and photos attached in another system are not read, and neither is anything the old vendor will not export.
Import your client list, look at what came across, and roll it back if you do not like it. The trial is seven days and asks for no card.