Save and reuse a mapping profile
If you import from the same system regularly, save how its columns match the platform's fields once, and apply that profile to every later file — the matching step is then done for you.
Before you start#
- Who can do it. Users who can import; see Import vehicles, drivers, stores or staff from a spreadsheet. The Data Exchange menu, with Mapping Profiles, is shown to Tenant Owner, Tenant Admin, Merchant Owner and Merchant Admin.
- What a profile is. It remembers which of your file's columns matched which field, for one record type. Profiles belong to your organisation, so colleagues can apply them too; see Import templates and mapping profiles.
Steps#
Save a profile#
- Import a file as usual and commit it; see Import vehicles, drivers, stores or staff from a spreadsheet.
- On the completed import's page, under "Save this column mapping as a profile for future imports?", type a name of up to 100 characters, for example the name of the system the file came from.
- Select Save Profile. The page confirms: Mapping profile "…" saved successfully..
Apply a profile#
- Start a new import of the same record type and upload the file.
- On Map Columns, choose the profile under Apply saved profile: and select Apply.
- If every column matches, you go straight to the preview ("Profile applied — all columns matched. Skipped to preview."); if the rows then fail to validate, you see "Validation failed. Please check the file and try again." instead. Otherwise the screen says how many columns still need matching and lists any profile columns missing from the file; match those, then select Confirm Mapping & Validate.
Download an import template#
On the Vehicles or Drivers list (fleet companies), or the Stores or Users list (merchants), select Export Template. You get a CSV file with the import's column headers and no rows.
Delete a profile#
- Open Mapping Profiles in the Data Exchange section of the sidebar; the screen is titled Saved Mapping Profiles.
- On the profile's row, select the delete icon (Delete) and confirm "Delete this profile?". The page confirms "Profile '…' deleted.".
What happens next#
- A saved profile is offered on Map Columns for every later import of the same record type in your organisation.
- An import that used a profile does not offer to save another one.
- Deleting a profile does not change imports that already used it.
Rules and limits#
- Profiles cannot be renamed or edited. To replace one, run the next import without applying a profile, save the new mapping, then delete the old profile.
- A file of more than 10,000 rows is checked in the background after the profile is applied ("Profile applied. Validation is processing in the background.").
If something goes wrong#
| Message | Cause | Fix |
|---|---|---|
| "Profile name is required." | The name was left empty | Type a name and select Save Profile again |
| "Profile partially matched. … column(s) need manual or AI mapping." | The file has columns the profile does not know | Match the remaining columns by hand |
| "The following required fields are not mapped: …" after applying | The file lacks a column for a required field | Add the column to the file and upload it again, or map the field by hand |
| "Profile not found." when deleting | A colleague already deleted the profile | Nothing to do; refresh the list |
| No save prompt after the import | The import used a profile, or it did not complete | Run an import without a profile and commit it |