When you export Time Data from Harvest your data is formatted in such a way that it cannot be directly imported into Intervals. A couple of extra steps need to be taken. Before we describe the steps please have a look at the following.
Harvest's hierarchy follows Project > Task > Time while the Intervals workflow hierarchy flows as (Project > Module > Tasks (To-dos) > Time) resulting in missing Modules.
There are two ways of importing Time Data from Harvest into Intervals. Have a look at each of the scenarios and follow the one that best describes your data:
Scenario one: Your Task column describes time entries as categories
Out of Scope
... and any time entries that could be treated like categories and are not necessarily a to-do or work type
If your data falls in that category (the task is vague enough to be considered a category) we suggest creating those tasks as modules (what are modules?) in Intervals under the Settings & defaults section. Once you've done that don't forget to assign them to the projects that you have created (you should get an option to do so after creating each individual module). Once you've created the modules rename the task column in your CSV to "Module".
The last step is to add a Work Type column. You will need to associate all time entries with a Work Type. The easiest would be to create one named "General", "Harvest" or use an already existing work type from Intervals (that you may create before importing).
Scenario two: Your Task column describes time entries as action items or to-do's
... (and any time entries that could be treated as work types (to-do's)
If your data falls into this scenario we suggest entering all time as general time (project time not associated with a task). Do this by renaming the Task column in your CSV to "Work Type". Then add all the unique work types in your CSV to the Settings & Defaults > Default work types section. Don't forget to assign those work types to the projects you've created.
The last step is to add a "Module" column. You will need to associate all time entries with a Module. The easiest would be to create one named "General", "Harvest" or use an already existing Module from Intervals (that you may create before importing).
Once you followed one of the above scenarios your data should be compatible with Intervals. For more information about time imports there is also more information on this post. If you are having any trouble importing your time from Harvest or if you have any questions on importing data please contact our support team direct at email@example.com.
Comments are closed.
For more Intervals help documentation, please visit help.myintervals.com