Clients & drivers
Names, contact details and source references. Check people with similar names before linking their records.
Moving your chauffeur operation
Bring the information your team relies on into 4fleet. Start with a clean export, review what maps across, and check a working day before making the switch.
See the moving plan36 sample records
One reviewed source file.
| Your file | 4fleet field |
|---|---|
| Customer | Client name |
| Email address | |
| Telephone | Phone number |
| Internal note | Ignore column |
Import coverage depends on the source profile and the fields in your export. These are the main data areas supported by the generic CSV / Excel workflow.
Names, contact details and source references. Check people with similar names before linking their records.
Registrations and vehicle details, reviewed against the way your fleet is organised.
Journey details with careful checks on dates, timezones and links to clients, drivers and vehicles.
Supported rate-card and distance data. Recheck the result with a familiar quote.
Partner records and contact details, ready to review before you hand over work.
Historical invoices, attachments and other records need a separate coverage check. Do not assume every field transfers.
A sequence you can follow
The import workspace is an owner action. Give one person responsibility for the source files, the review and the final decision.
Keep an untouched copy of your export. Agree which records you need and which system remains the reference during the move.
Choose the matching source profile. Review columns, required fields, date order and timezone before running the preview.
Read the create, update, duplicate and error counts. Resolve uncertain names, amounts and links while the data is still a preview.
Commit the reviewed import, inspect the final report and open a selection of records in their working screens.
Confirm date order.
Then confirm the timezone.
The details worth slowing down for
A file can look tidy and still describe the wrong journey. Review a client with several bookings, a partner job, an overnight pickup and a price you know.
Your mailbox connection, team access, payment setup and working preferences need their own checks. Walk through an enquiry, a dispatch and an invoice before choosing your changeover date.
Find your fit
The generic import workflow accepts CSV and XLSX files in the supported data slots. The required columns and coverage depend on the selected profile. Review the mapping and preview report before committing.
Export a small representative CSV or Excel file first. Choose the matching source profile, review the column mapping and resolve preview issues before importing. Keep the original export so you can check the result. Migration assistance is included with Operations and Scale.
The import preview is a dry run. It reports the proposed result before you choose to commit. A workspace owner reviews and performs the import.
Choose the scope your operation needs, then verify support for each record type. Keep your original exports and existing records available while you check the result.
It depends on the quality of your export, the data areas involved and the setup your team needs. A sample export and a typical working day are useful starting points for a demo discussion.
Put 4fleet to work
Use your trial to understand the workflow, then plan the move around your operation.