What Harvest's help page says
Harvest imports only accept commas (,) as delimiters. Semicolons (;), slashes (/), and other delimiters will result in import errors.
To include commas, the fields containing them need to be enclosed in double quotes to ensure that they import properly (for example, "First I did this, then I did that" in a Notes cell).
Quoted word for word from Harvest's help page, listed under Sources.
Why it happens
- The CSV was saved from a spreadsheet that uses semicolons as the list separator.
- A note holds a comma and is not in double quotes, so its words land in the wrong columns.
How to fix it
- Open the CSV in a plain text editor and check the character between values. It must be a comma.
- Check that every value holding a comma is wrapped in double quotes.
- Or make a new file: on the ClientHours Harvest page, enter the first and last name and a task, click "Harvest import (CSV)", and upload that file as it is.
- In Harvest: Settings, Import/Export, Import time, then drop the file and click Import timesheets.
Calendar to Harvest CSV time import
What the ClientHours file does
- Values are separated by commas, in Harvest's 8-column order: Date, Client, Project, Task, Notes, Hours, First name, Last name.
- A value that holds a comma, a double quote or a line break is put in double quotes, with inner quotes doubled.
- Hours are decimal with two places (1.75), and Date is YYYY-MM-DD.
- The file is UTF-8 without a byte order mark.
Limits
- Opening the file in Excel and saving it again can switch it to semicolons, depending on your region settings.
- Harvest's page names no encoding. The file is UTF-8.
- Importing the same file twice gives duplicate entries. Harvest's page says time entries cannot be updated by import.
- No ClientHours file has been tested by importing into a real Harvest account. What the file contains is checked by tests. How Harvest reads it comes only from the help pages under Sources.
Questions
- Which delimiter does Harvest accept?
- Commas only. Harvest's page says semicolons, slashes and other delimiters result in import errors.
- My notes have commas in them. Is that a problem?
- Not if the note is in double quotes. Harvest's page asks for that, and the ClientHours file quotes every value that holds a comma.
- Does Harvest show which row failed?
- Harvest's page does not describe the error screen. Check the delimiter and the quotes first, then the names: First name and Last name must match a person in your account.
Sources
Other import problems
- Clockify: "Date, time, and duration formats don't match Clockify settings"
- Clockify: "The file is not comma-delimited"
- Clockify: "Missing or incomplete field values"
- Toggl Track: "Adding new users increases your workspace fee"
- Toggl Track: "Not allowed as header: Project;task;client"
- Google Calendar: "Processed zero events"
- Google Calendar: "Processed x of y events"
- "Google Calendar is temporarily unavailable" when importing
- Google Calendar: "Feed processing error"
- Calendar and time tracker import problems
ClientHours is free, with no account and no payment. The calendar file never leaves your browser.