Trip Import

Import trip records from external sources into TransportechAI -- upload CSV files, map columns, validate data, and reconcile imported trips with your dispatch records.

The Trip Import page allows you to bring trip data from external sources into your TransportechAI dispatch system. Whether you need to import historical records from a previous system, upload platform trip data that cannot be synced via API, or reconcile trip logs from a third-party provider, this tool handles the process.

Navigation: Dispatch > Trip Import

Purpose

Not all trip data originates within TransportechAI. You may have drivers working on platforms without direct API integration, or you may be migrating from another dispatch system. The Trip Import feature allows you to:

Upload trip records via CSV or Excel files
Map external data columns to TransportechAI fields
Validate imported data before committing it to the system
Review and correct errors during the import process
Track import history for audit purposes

Import History

The main page displays a table of all previous import operations.

Table Columns

Column	Description
Import ID	System-generated unique identifier for the import batch
Date	When the import was performed
Source	The file name or platform the data came from
Total Records	The total number of trip records in the file
Imported	The number of records successfully imported
Skipped	The number of records that were skipped (duplicates or already existing)
Errors	The number of records that failed validation
Status	Completed, Partially Completed, or Failed
Imported By	The user who performed the import

Importing Trips

Click the Import Trips button to start a new import. The process follows a step-by-step wizard.

Step 1: Upload File

Field	Type	Required	Description
Source Platform	Dropdown	No	Select the platform the data comes from (Uber, Careem, Bolt, Other, or Manual)
File	File Upload	Yes	Upload a CSV or Excel (.xlsx) file containing trip records

Supported file formats:

Format	Extension	Notes
CSV	.csv	Comma-separated values, UTF-8 encoding recommended
Excel	.xlsx	Microsoft Excel format

If you select a known platform (e.g., Uber) as the source, the system will attempt to auto-detect the column mapping based on the platform's standard export format. This saves time on the mapping step.

Step 2: Column Mapping

After uploading the file, the system displays a preview of the first few rows and asks you to map each column in your file to the corresponding TransportechAI field.

Required Mappings

TransportechAI Field	Description	Example Source Column
Trip Date	The date of the trip	"Date", "Trip Date", "Pickup Date"
Pickup Time	The time the trip started	"Start Time", "Pickup Time"
Pickup Location	The pickup address or coordinates	"From", "Pickup Address"
Dropoff Location	The dropoff address or coordinates	"To", "Dropoff Address"
Driver	The driver who performed the trip	"Driver Name", "Driver ID"
Fare	The trip fare amount	"Total Fare", "Amount", "Earnings"

Optional Mappings

TransportechAI Field	Description	Example Source Column
Dropoff Time	The time the trip ended	"End Time", "Dropoff Time"
Distance	Trip distance	"Distance (km)", "Miles"
Duration	Trip duration	"Duration", "Trip Time"
Vehicle	The vehicle used	"Vehicle", "Plate Number"
Client	The client or passenger	"Rider", "Passenger Name"
Payment Method	How the fare was collected	"Payment Type", "Payment Method"
Platform Commission	Commission taken by the platform	"Service Fee", "Commission"
Tips	Tip amount	"Tip", "Tips"
Trip Type	Category of the trip	"Trip Type", "Category"
External Trip ID	The trip ID from the external system	"Trip ID", "Reference"
Notes	Any additional notes	"Notes", "Comments"

Step 3: Data Validation

After mapping columns, the system validates all records against business rules:

Validation	Description
Required Fields	Ensures all required fields have values
Date Format	Validates that dates and times are in a parseable format
Numeric Values	Confirms that fares, distances, and durations are valid numbers
Driver Matching	Attempts to match driver names or IDs to existing drivers in the system
Duplicate Detection	Checks for trips that already exist in the system (based on date, driver, and time)
Vehicle Matching	Attempts to match vehicles to existing fleet records

Records that fail validation are flagged and displayed in an error summary:

Error Type	Description	Resolution
Missing Required Field	A required value is empty	Edit the record to add the missing value, or skip the record
Invalid Date	The date format could not be parsed	Correct the date format in the source file and re-upload, or edit inline
Driver Not Found	The driver name or ID does not match any driver in the system	Map to an existing driver or create a new driver record
Duplicate Trip	A trip with the same driver, date, and time already exists	Skip the record or force import (creates a duplicate)
Invalid Fare	The fare amount is not a valid number	Correct the value

Always review the validation results carefully before proceeding. Importing invalid data can lead to incorrect financial reports and driver compensation calculations.

Step 4: Review and Confirm

A summary screen shows:

Section	Description
Records to Import	Total number of valid records ready for import
Records to Skip	Number of records that will be skipped (duplicates, errors)
Unresolved Errors	Number of records with unresolved validation issues
Estimated Revenue	Sum of fares from the records to be imported

Click Confirm Import to finalize. The system imports the records and displays a completion summary.

Post-Import Review

After an import completes, you can:

View Imported Trips

Click on an import batch in the Import History table to see all trips that were imported in that batch. From here you can:

Open any individual trip to verify details
Edit trip records if corrections are needed
Delete incorrectly imported records

Error Report

For batches with errors, download the Error Report to see which records failed and why. This report includes the original row data alongside the specific validation errors, making it easy to correct the source file and re-import.

Driver Matching

One of the most critical steps in the import process is matching drivers from the external data to your TransportechAI driver records. The system uses the following matching logic:

Priority	Match By	Example
1	Driver ID	If the external system's driver ID has been mapped in Platform Integration
2	Full Name (exact)	"Ahmed Al Rashid" matches "Ahmed Al Rashid"
3	Full Name (fuzzy)	"Ahmed Rashid" may match "Ahmed Al Rashid" with a confidence score
4	Phone Number	If the external data includes driver phone numbers

For the best results, use the Platform Integration driver mapping feature to link external platform IDs to your drivers before importing. This ensures accurate and automatic matching.

Import Templates

To simplify repeated imports, you can download pre-formatted templates:

Template	Description
Generic Template	A blank CSV with all supported columns and example data
Uber Export Template	Column layout matching Uber's standard trip export
Careem Export Template	Column layout matching Careem's standard trip export
Custom Template	Based on a previous successful import's column mapping

Best Practices

Before performing a large import, test with a small sample file (10--20 records) to verify that your column mapping and driver matching are correct. This prevents having to clean up large batches of incorrectly imported data.

Schedule regular imports (e.g., weekly) for platforms that do not support real-time API sync. Consistent import schedules ensure your dispatch data stays current without large catch-up batches.

Imported trip data affects financial calculations, including driver commissions and revenue reports. Always verify import accuracy with your finance team, especially for the first few batches from a new data source.

On this page