Data import
The import wizard loads data from Excel or CSV spreadsheets: vehicles, geofences, cameras, cargo and the records they relate to. It is built for real working spreadsheets rather than strict templates: the system finds the tables on your sheets itself and proposes a column mapping.
Open it from Manage → Import or at /import. The subtitle reads: "Upload a
spreadsheet, map it to your data, and import."
Five steps
The wizard runs Upload → Tables → Columns → Resolve → Review. You can move between steps freely with Back and Next; Start over resets everything.
Step 1. Upload
Press Choose file and pick the workbook. .xlsx, .xls and .csv are
supported.
While parsing you see "Reading workbook…". When it finishes the system reports how many tables it found: "3 table(s) detected".
Every distinct rectangular block of data on a sheet counts as its own table. One sheet can hold several tables separated by blank rows — each becomes an independent import.
If nothing was found: "No tables found in this file." Check that your data starts with a header row and is not broken up by merged cells. Replace file lets you load a different one.
Step 2. Tables
"Which entity is each table?" — for every table found, choose the system entity it loads into.
The table card shows Sheet: Vehicles, the row count ("128 rows"), the column count ("9 columns") and a preview.
- The Select entity… dropdown assigns the table.
- Skip this table excludes it. Unassigned tables are skipped automatically.
Step 3. Columns
"Map columns to attributes". For each table ("Table 1 · Vehicle") its columns are listed:
| Column | Meaning |
|---|---|
| Column | The header from the file |
| Sample | A value from the first rows — helps you see what it holds |
| Attribute | Where it loads; Not imported if you do not need it |
- Pick attribute opens a tree of available attributes. Related objects expand in the tree: on a vehicle, for instance, you can target not only its own fields but those of its owner or device.
- Match by name tries to map columns to attributes automatically by matching their names.
- Clear removes a mapping.
If required attributes are unmapped the wizard warns: "Required attribute not mapped: License plate".
Step 4. Resolve
"Resolve relations". Where a table refers to other objects (owner, type, zone), the system looks them up among existing records — "Matching against existing records…".
The match is fuzzy: similarly spelled names are proposed, and doubtful ones are flagged Needs review.
For each value you see:
- Your value — as written in the file;
- Matched — the proposed existing record;
- Decision — what to do.
The decisions available:
| Decision | What happens |
|---|---|
| Use existing | Link to the matched record |
| Create new | A new record with this name is created |
| Leave empty | The field stays blank |
A counter shows how many values still need a decision: "4 value(s) still need a decision". With no relations at all: "No relation values to resolve."
Step 5. Review
"Check the summary, then import — this creates records in your system."
The summary lists the entities, the row count for each ("128 rows") and what will be created (Will create). Preview shows exactly how the data will land.
Press Import 128 rows. While it runs you see "Importing…".
When it finishes the system reports:
- "Imported 126 of 128 rows" — how many succeeded;
- "2 rows failed" — how many did not, and why.
Done and Import another file close out the process.
Import creates records in the system. Before loading a large file it is worth running a trial batch of a few rows to confirm the column mapping is right.
Preparing the file
Practical advice:
- The first row of each table holds the column headers.
- Avoid merged cells inside the data area.
- One entity per table; do not mix vehicles and geofences in one block.
- Convert units to the system's: distances in kilometres, speed in km/h.
- Write related object names consistently — this improves automatic matching at the Resolve step.
Typical workflows
Populate the fleet for the first time. Prepare a sheet with "Plate", "Brand", "Model", "Owner" and "Device ID" columns → upload → assign the table to the Vehicle entity → map the columns → create the missing owners at the Resolve step → import.
Add new vehicles later. The same file with new rows. At the Resolve step choose Use existing for owners already on file so you do not create duplicates.