---
title: "Importing data"
description: "How Runima handles dates, time zones, and duplicate activities during import."
canonical_url: "https://runima.fit/docs/getting-started/importing-data"
---

> Index of every page on this site: [llms.txt](https://runima.fit/llms.txt)

Understanding a few rules makes your dashboards more accurate.

## Activities vs. daily metrics

- **Activities** (recorded runs) are stored as exact UTC instants, so pace and
duration are precise regardless of where you trained.
- **Daily metrics** (resting HR, sleep, body battery) are calendar values —
Runima anchors them to the local calendar day, not a clock time.

## Import timezone

Garmin activity CSVs and Amazfit minute files contain local clocks without UTC
offsets. Use the shared import-timezone selector to interpret them. It defaults
to your profile timezone (or your browser's, if you haven't set one) and can be
overridden without changing your profile.

Choose a named timezone for historical daylight-saving rules, or a fixed offset
such as **UTC+03:00** when that offset is known. For travel, import each period
with its original timezone. A clock time that is repeated or skipped by a
daylight-saving change keeps the offset from before the change, as a watch does
until it syncs with your phone.

Amazfit workout HR is kept only when it rises above the hour before the
session, and overnight HR uses only minutes the watch staged as sleep. If you
lived in another timezone for part of your history, the import lists the
affected dates; import its **HEARTRATE_AUTO** and **SLEEP_MINUTE** files again
with that timezone selected. HR that already passed the check is never replaced.

A Garmin data export records each day's UTC offset, so its sleep times need no
timezone choice. On a daylight-saving change day, and for nights the export has
no daily summary for, the import timezone is used.

FIT timestamps and explicit UTC offsets in TCX or Amazfit summaries are preserved.
Daily sleep and VO₂max date labels are not shifted to another calendar day.

## Duplicates

Re-importing the same export is safe. Matching uses recorded start times and
summary fields such as distance and duration. A run edited in Garmin Connect
still matches its FIT file by start time and average HR. Richer native FIT/TCX
recordings take priority over reconstructed Amazfit minute-HR streams.

You can upload a later Amazfit export, or just its HR minute files, after the
first set. Runima matches samples to previously imported Amazfit runs and sleep
windows, merges overlapping workout samples and recalculates training stress
when activity data changes.

## Future dates

Records dated in the future are skipped by a single import guard, which keeps
trend lines from being distorted by clock-skewed device data.

## Sitemap

See the full [sitemap](https://runima.fit/sitemap.md) for all pages.