← Guides

How to switch from TeslaFi without losing your history

Export your drives, charges and idles, import them one file at a time, and keep TeslaFi running until you are sure. Nothing you import is duplicated or overwritten.

12 November 2026 · 6 min read

Most people who stay on a logger they have outgrown stay for one reason: the years of drives and charges stored in it. This is how to move that history from TeslaFi to evlogr — what comes across, what does not, and why you can run both side by side while you check the numbers.

Before you export: connect the car and check your timezone

Imported history is attached to a vehicle, so connect your Tesla to evlogr first. Then check the timezone in Settings. TeslaFi writes local clock times with no timezone attached, and we read them in your account's timezone — so if the setting is wrong, every imported session lands shifted by the difference.

Which TeslaFi files to download

TeslaFi lets you search its lists of drives, charges and idle (parked) sessions and download each as a CSV file. Those three lists are what you want: one row per drive, one per charge, one per parked session. At the time of writing, charges are under the Charges menu as a search-and-download page, and the drives list offers a CSV download once you have picked a date range. Menu labels change between versions; look for the CSV download on each list.

Skip TeslaFi's full raw-data download. That export has a row for every time TeslaFi polled the car, one month per file. Our importer reads one row per session, so a raw file is the wrong input.

Import one file at a time

  • Open Import, reached from Settings, and choose a file. We work out from its column names whether it holds drives, charges or idles, and guess which column is which.
  • Check the columns. The preview shows the mapping and the first rows exactly as they will be written. Correct any column we guessed wrong, or the record type. Distances in miles are recognised from the column header and converted to kilometres; you can switch that too.
  • Pick the vehicle and import. The result says how many rows came in, how many were skipped for having no usable start time, and how many were skipped because evlogr had already logged that session itself.

One file takes up to 20,000 rows and 4 MB. A bigger export is refused whole rather than quietly cut short — split it, one file per year works well, and import each part. Overlapping parts are fine, for the reason in the next-but-one section.

What comes across

What evlogr's importer reads from each TeslaFi export
ExportWhat we import
DrivesStart and end time, distance, battery % at start and end, start and end address, average outside temperature, start and end odometer, top speed, kWh used
ChargesStart and end time, energy added, cost, location, battery % at start and end
IdlesStart and end time, location, range at start and end, range and kWh lost, whether Sentry was on
What evlogr's importer reads from each TeslaFi export
  • TeslaFi's separate Date and Start/End Time columns are combined. Day-first dates such as 14/10/2023 are recognised once for the whole file, and an overnight session whose end time reads earlier than its start is moved to the next day.
  • Battery levels with decimals, such as 80.07, are rounded to a whole percent.
  • A charge's price per kWh is worked out from its cost and energy when both are in the file. Costs arrive as TeslaFi recorded them; your tariff in evlogr prices the sessions we log ourselves.
  • Drive addresses become names you can turn into places on the Places page, or fold into a place you already have — “My house” into Home, for example — which relabels the imported history in one go.
  • A drive TeslaFi never closed properly — six kilometres that apparently took all night — keeps its start time and distance, and loses an end time that cannot be real.

What doesn't come across

  • Routes. The session exports carry no GPS trail, so imported drives have no map. On the lifetime map their stops are joined by dashed straight lines, not the roads driven.
  • Second-by-second detail: speed and power traces, gear changes, seat-belt events. Those exist only for drives evlogr logs itself.
  • TeslaFi's settings — tariffs, tags, geofences. Set your tariff in evlogr and it prices everything we log from then on.
  • Battery-health history. That lives in TeslaFi's raw data, which the importer does not read, so evlogr's battery charts start from the day you connect.

Run it twice, run both

Importing the same file again never duplicates a row. Each imported row is keyed on the vehicle and its start time, so a second run updates the rows the first one wrote instead of adding new ones. Imported rows are also marked as imported, so evlogr's own processing never overwrites them.

Rows that overlap a session evlogr has already logged are skipped. The match is on the time range rather than the exact timestamp, because two loggers watching the same car record the same charge a few seconds or minutes apart. That is what makes it safe to keep TeslaFi running alongside evlogr: connect, let both log for a week or a month, compare them, and import when you are ready. Sessions both of them saw keep evlogr's version, with its route and detail; everything before that comes from the export.

Importing works on every plan. The free plan shows the last 30 days of history; everything older that you import is kept, and appears on Pro.

What we checked

The importer was built against real TeslaFi exports covering October 2023 to August 2026. All 132 rows of the charges file came in. Of a 2,601-row drives file, 2,588 came in and 13 were skipped as sessions evlogr had already logged, with no duplicates left behind.

For prices and a feature-by-feature comparison, see evlogr vs TeslaFi. When you are ready, start the import.

These figures come from evlogr, which logs a Tesla’s drives and charges automatically and prices each charge against your own time-of-use tariff. Free on one car.