Import and export

Settings → Import brings in time entries (and lists of clients or projects) from Harvest, Toggl Track, Clockify or any other CSV. Settings → Export downloads everything as a ZIP: one CSV and one JSON file per kind of record, every uploaded file, and every invoice as a PDF.

	Who can do it
Import, and undo an import	Owners and admins
Export everything	Owners
Export one client's records	Owners and admins

Import

Export the file from your old tool

Files can be up to 20 MB and 50,000 rows. For more, export a shorter date range and import the files one after another.

How to import

1. Open Settings → Import

   You need to be an owner or admin.

2. Choose the file and click Read file

   Nothing is imported yet. The preview shows which tool the file came from and whether it holds time entries, projects or clients; change either if it guessed wrong.

3. Check the columns

   Open Columns to see which column each value is read from. For a Harvest, Toggl Track or Clockify export they're filled in for you; for any other CSV, pick them. Time entries need at least Date, Hours (or Duration, or Start time and End time) and Project.

4. Match people

   Under People, everyone in the file is matched to a member of your organization by email, then by name (a by email or by name badge shows how). Pick a member for anyone unmatched, or leave Skip these rows. Assign everyone unmatched to sets them all at once. If the file has no person column and you're the only member, everything is yours.

5. Update the preview

   After changing anything, click Update preview to see the new counts.

6. Import

   Click Import N time entries (or Import N clients and N projects).

Check it worked: the page says Imported N time entries (… h), N new projects and N new clients, and the import is listed under Past imports. Open Time → Team for those weeks to see the entries.

What gets created

• Clients are matched by name, ignoring case; a client that doesn't exist yet is created. Rows with no client go to a client called No client.
• Projects are matched by name under their client. New projects are hourly and not confidential.
• People on projects: everyone with time on a project is put on its team (if they aren't already), at the rate they used most in the file, or their usual bill rate if the file has none.
• Time entries get the row's date, hours (rounded to 0.01), notes, billable flag and rate, plus its start and end time when the file has them (Toggl and Clockify Start time/End time, Harvest Started At/ Ended At). The file's hours are kept even when they differ from the times. A client set to require start and end times skips rows without them, listed as rows with problems.
  • The task goes in front of the notes: Design: Homepage wireframes.
  • Billable reads yes/no, true/false or 1/0; with no billable column, every entry is billable.
  • The rate is set on the entry itself (like an owner's rate override), so it's what the entry is invoiced at. With no rate, the project's rate for that person applies as usual.
  • If timesheet approval is on, imported entries count as approved.
• A projects file creates the clients and projects only. Its rates are used only when you're the only member (you're put on each new project at that rate); otherwise set rates on each project's team.
• A clients file creates clients, with their email, address and phone if the file has them.

Rows the old tool had already invoiced (Harvest's Invoiced? column) are imported as non-billable by default, so they're never billed twice. Under Rows already invoiced in the old tool you can skip them or import them as they are instead.

Amounts are imported as numbers. If the file is in another currency than your organization's, the preview says so; nothing is converted.

Dates

Dates are read as calendar days, never shifted by time zone: a row dated March 2 is logged on March 2. 2026-03-31, 03/31/2026, 31/03/2026 and 31.03.2026 all work. Whether the file is day-first or month-first is worked out from the whole column; if every date would read either way, the preview says Every date in the file would read either way and assumes month-first (day-first for dotted dates). Change Dates in the file are if that's wrong.

Importing again

Importing the same file again only adds rows that aren't in yet: each row is remembered, so the preview counts them under Already imported (skipped). Two identical rows in one file are both imported. If you delete an imported entry, importing the file again brings that row back.

A row that changed in the old tool since the last import (a different date, hours, notes, person, client, project, billable flag or rate) counts as a new row, and the earlier version stays. To replace an earlier import with a fresh export, undo the earlier import first.

Undo an import

Under Past imports, click Undo on an import. It deletes the time entries that import created, then the people it put on projects, and the projects and clients it created, unless something else uses them now (later time entries, invoices, documents, contacts and so on). Undoing doesn't touch clients, projects or entries that were already there.

An import can't be undone once any of its entries is on an invoice: void or delete that invoice first.

Check it worked: the import shows Undone, and the message says what was removed and what was kept.

Troubleshooting

Message	What to do
That file is over 20 MB. / That file has more than 50,000 rows.	Export a shorter date range and import it in parts.
That's not a CSV file. Export the report as CSV, not Excel or PDF.	Export again and choose CSV.
That doesn't look like a CSV with a header row.	The first line must hold the column names.
Pick the column that holds each entry's date. (or the project, or hours)	Open Columns and choose it.
Everything in this file has already been imported.	Nothing to do: every row is already in.
Nothing in this file can be imported. Check the rows with problems and the people mapping.	Every row has a problem or belongs to a skipped person.
N of this import's time entries is on an invoice. Void or delete that invoice first, then undo.	Void or delete the invoice, then undo.

Rows with problems are listed under N rows can't be imported with their line number, for example No project. Every time entry here needs one., "2026-02-30" isn't a date in the chosen format., "abc" isn't a number of hours., Zero hours (a running or empty timer). or … hours in one entry — more than a day. Fix them in the file and import it again; rows already in are skipped.

Export

Everything

1. Open Settings → Export

   You need to be the owner.

2. Click Download everything

   The ZIP is built as it downloads, so a large organization takes a while.

One client

Useful when handing a client's records over.

1. Open Settings → Export

   Owners and admins.

2. Choose the client and click Download ZIP

It holds that client and its contacts, links, projects, project teams, milestones, tasks, comments, time entries, expenses, invoices (with lines, events, payments and credit), estimates, agreements, documents, retainer schedule and billing cycle, and the people who worked on it: their name, email, role, employment type and title, but not their cost or default bill rate, bio or résumé.

What's in the ZIP

Path	What
README.txt	What the export is and when it was made.
data/<name>.csv, data/<name>.json	One pair per kind of record: organization, clients, contacts, links, projects, members, project-members, milestones, tasks, task-comments, time-entries, time-entry-attachments, timesheets, expenses, invoices, invoice-line-items, invoice-events, payments, credit-notes, credit-applications, estimates, estimate-line-items, agreements, scheduling-connections, scheduling-event-types, bookings, vault-links, documents, recurring-invoices, billing-cycles, payment-methods, imports, calendar-subscriptions, audit-log.
files/documents/, files/receipts/, files/milestones/, files/time-evidence/, files/agreements/, files/resumes/	The uploaded files themselves. Each CSV's exportedFile column gives the path.
invoices/<number>.pdf	Every invoice, rendered as it looks today.
manifest.json	Row counts, and anything that couldn't be exported (problems).

Records point at each other by id (clientId, projectId, userId, …). Time entries also carry project.name and user.name, and members their user.name and user.email. Money and hours are exact decimals, calendar dates are YYYY-MM-DD, and times are UTC. A time entry's startMinute and endMinute are its local start and end as minutes after midnight on its date (570 is 09:30; an end before the start ran past midnight), blank when only hours were logged. The JSON files hold exact values; in the CSV files, text that starts with =, +, - or @ gets a leading ' so a spreadsheet doesn't run it as a formula.

The timesheets, payment methods, imports, calendar subscriptions (who has one and when it was last read), audit log, résumés and credential links are in the whole-organization export only. Credential links hold no secrets (just the label, note, provider and link to the vault item), but the links reveal how your vault is organized, so a client handover leaves them out. A client's export includes only the time entry evidence marked Client can see it.

Never included: passwords, two-factor secrets and recovery codes, API keys, share, invoice and estimate links, staffing-review links, integration tokens and credentials (QuickBooks, Mercury, Linear, file services, e-signature, SSO), calendar links, calendar subscription addresses and the Slack webhook. Values like these are also blanked inside the audit log's recorded changes.

Every export is recorded in the audit log: exported all of the organization's data or exported a client's records. Imports show as imported data and undid an import.

Check it worked: open the ZIP. manifest.json lists the row counts, and problems is empty.

Troubleshooting

• The download stops part-way: the archive is built while it streams; a timeout in a proxy in front of the app can cut a large one off. Raise the proxy's read timeout, or export one client at a time.
• A file is missing from files/: manifest.json → problems says which and why (for example, it couldn't be read from S3-compatible storage).
• Only owners can export the whole organization. Ask an owner, or export one client at a time as an admin.