FLEET OVERWATCH User manualVersion 4.9.2

Copy from other platforms

Version 4.9.2Updated 2026-10-22Who: Admin

Maintenance › Copy from other platforms (also in the Admin and Overwatch menus, next to Import data; in Basic view it is under Advanced) copies your company's data from the platforms you use into this server, with their API keys. Administrators connect platforms and start copies; managers can look through and download what was copied.

What is copied #

PlatformKeysBecomes records hereKept as it came (searchable, downloadable)
FleetioAPI key and account token (Fleetio: Account › Integrations › API keys)vehicles, contacts, vendors, work orders with tasks and parts, issues, service history, reminders, renewals, parts, purchase orders, fuel, meter readings, expenses, inspections, vehicle assignments, comments, documents and photos (downloaded and attached)inventory locations, stock by location, inspection forms, service programs, groups, labels
SamsaraAPI token (Samsara: Settings › API tokens)vehicles and drivers (matched or added)trailers, equipment, addresses, users, tags, hours of service logs, daily logs, violations, DVIRs, defects, safety events, driver documents, trips, driver-vehicle assignments, routes, fuel and energy; GPS and engine history if you tick them
MotiveAPI key (Motive: Admin › API keys), or an OAuth access tokenvehicles, drivers, fuel purchases (as fuel entries, with the receipt)assets, groups, geofences, HOS logs and violations, inspection reports, safety events, IFTA trips, driving periods, idle events, fault codes, documents, dispatches
Geotabserver (usually my.geotab.com), database, user name and password of a MyGeotab user with read accessvehicles (devices), drivers, fill-ups (as fuel entries)groups, zones, rules, trips, exception events, faults, DVIRs, duty status logs, driver changes, fuel used; GPS and engine data if you tick them

Mixing with file imports. Records brought in from Fleetio's export files (Import data, Fleetio work orders) keep their Fleetio id, so a Fleetio copy afterwards updates them instead of adding copies, and replaces the plain tasks of imported work orders with Fleetio's full lines (labor, technician, parts). Fuel entries voided in Fleetio are left out either way.

Matching, never duplicating. A vehicle that is already here is found by the platform's id, the Samsara id, the VIN, then the name; a driver by the Samsara driver id, the email, then the full name. Only empty fields are filled in: nothing you typed is overwritten. Copying again updates the same records. Turn off Add vehicles and drivers that are not here yet to only link to the ones you have.

Copy #

  1. Open the platform's card, enter the keys and press Save keys. The keys are checked at once (Test checks again later).
  2. Under What to copy, untick anything you do not want. GPS history and Engine history / data are off by default: they can be millions of rows.
  3. Choose How far back (30 days to 10 years) and How:
    • Copy once: one complete copy, then it stops. For moving over.
    • Copy, then keep in sync: after the first copy it checks every 15 minutes to once a day and copies only what changed (plus a day of overlap).
  4. Press Start copying. You can leave the page: the copy runs in the background and continues after a restart. All platforms copy side by side; the card shows what it is copying and how many kinds are done.

The first copy of a large account can take a while (hours for years of Fleetio work orders or Samsara logs): each platform limits how fast its data can be read, and the copy keeps to those limits.

Look through and download #

Copied data, at the bottom of the page: choose the platform and the kind of data, search, and click a row to see the complete record. Download CSV (one column per field; nested values as JSON) or JSON gives the whole dataset.

Keys and privacy #

Keys are saved in config/config.json on this server (sections fleetio, samsara, motive, geotab) and are never sent back to a browser: the page only shows whether one is saved. Leave a key box empty to keep the saved key. Each company account copies into its own data with its own keys. Copies are listed in the audit log (xfer.keys, xfer.start, xfer.stop, xfer.export).

If this does not work #

  • "refused the key (HTTP 401)": the key is wrong, expired or revoked. Enter a new one and start again.
  • "not allowed for this key (HTTP 403)" next to a kind of data: the key may not read it. Give the key read access to it on the platform (Samsara: the token's scopes), or untick it.
  • "not offered for this account": the platform does not offer that data on your plan. It is skipped; everything else is copied.
  • "asked to slow down": the platform's request limit was reached; the copy waits a minute and continues by itself.
  • "The background worker part that copies data is not running": it starts by itself within a minute after an update. If it does not: sudo -u www-data php /opt/fleet-overwatch/worker.php start.
  • A document or photo that is not an accepted file type (images, PDF, Office documents, text and CSV) or is larger than the attachment limit (Admin › System settings) is not attached; the card counts it under files not accepted.

Something here out of date or unclear? Tell your administrator and mention “data-transfer” and version 4.9.2.