WorkGuru supports the bulk creation of projects via a csv import template. The import template can be uploaded on the imports dashboard (Administration -> Imports). Warning: Please ensure the accuracy of your import Csv prior to upload, imports can not be undone by you or the WorkGuru team. If this document does not explicitly state that you can add something to your import, it is not supported.
This import allows the update of non consequential Project information (Things that when changed do not affect other aspects of the program). If a field can be updated, It will say 'Yes' in the Updating Allowed column on the table below. We do not recommend the import being used as an updating tool as there is a higher chance of incorrect information being passed in this way in comparison to updating Projects on the platform.
Note: This import only creates the project details, in effect just creates an empty project. To populate the project after creation, either import the project line items (tasks/costs), or edit the project and apply a project template.
Project Import Field Descriptions
Updating Allowed | |||
ProjectNo | Project number (ideally outside of the WorkGuru sequence). This field is used when mapping to existing Projects. It must match exactly in order to update allowed fields. If a match is not found, the import line will be marked as a new Project. You cannot update already Completed or Cancelled Projects through this import. | Required | |
ProjectName | Project name | Required | Yes |
Description | Project description | Yes | |
StartDate | Project end date DD/MM/YYYY | Required | |
DueDate | Project end date DD/MM/YYYY | Required | Yes |
CompletedDate | Project completed date DD/MM/YYYY. If present, make sure the import project has a status of Completed OR Cancelled | ||
Client | Project client - Must match an existing client exactly | Required | |
TaskAmount | Task invoiced total (optional - for historical balances only) - Delete column if not using - otherwise a numerical value is required | ||
CostAmount | Cost invoiced total (optional - for historical balances only) - Delete column if not using - otherwise a numerical value is required | ||
ProjectGroup | Assigned project group if required. (Make sure the group exists prior to upload) | ||
Asset | Assigned asset if required - Referenced Asset must match an existing Assets name exactly | ||
Note | Project notes - These will appear in the notes tab of your Project | Yes | |
ClientPurchaseOrder | Client PO or reference. | ||
ProjectManager | Project manager name (Matches up to their username) - defaults to tenant admin or current user if omitted | ||
ProjectTemplate | Project template name - applies template to project. This is matched off your Project Template name via templates you have previously set up. The Project Template Name must match exactly | ||
Status | Project status. String must match an existing statusname exactly. Default statuses are:
| Yes - If being marked as completed or cancelled, the completion date is required You cannot update Completed OR Cancelled Projects | |
LineType | Must say 'Project'. This is so the import can be further extended in the future | Required | |
ReportingCategory1 | To import your reporting category please follow this format. CategoryName::Option. These must already be synced over from accounting and match exactly | ||
ReportingCategory2 | To import your reporting category please follow this format. CategoryName::Option. These must already be synced over from accounting and match exactly |
If you have project custom fields, these can also be populated on import by adding a column to the import data with the custom field name (not label). Note: Custom field name is case sensitive, has to match exactly.