Help · Moving data
Import time entries
The hard part of leaving a tracker is not the features. It is years of history that is your billing memory, your tax trail, and your evidence in a dispute. So owntime is careful with it.
What it accepts
A CSV exported from Harvest, Toggl Track, Clockify or FreshBooks. The format is detected from the columns, so you do not have to tell it which one you came from. Anything else with date, project and hours columns will usually work too.
Required columns: date or start date, project, and hours or duration. Optional: client, description or notes, billable, and tag columns, which import as tags.
Dry run first
Drop the file in and owntime parses it without writing anything. You see how many rows it understood, how many it skipped and why, and a preview of the first few. Only when you confirm does anything reach your file.
Importing the same file twice
Exact duplicates are skipped. Re-importing the same export is a no-op, which means you can be relaxed about whether that first attempt worked rather than counting rows.
Two things that need your attention after
- Rates. Imported rows carry no rate, because most exports do not include one. Set rates on the projects afterwards and the history becomes billable.
- The person who did the work. If your file names the person, owntime keeps it as a tag rather than dropping it. There is no team member concept to attach it to, and losing it silently would be worse.
If it looks wrong
The skip reasons name the row and the problem, usually an unparseable date or a zero hours cell. Fix those in the CSV and re-run. Nothing partial is left behind, since duplicates are skipped anyway.