Skip to main content
How to import projects in Gryzzly

Do you need to import data in Gryzzly? Let’s find out what you can import and how.

Angel avatar
Written by Angel
Updated over 6 months ago

Import feature

You must have admin privileges to access this section.

Import projects

You can then import your data with a .csv or .xslx format file!

👉 Important: The accepted column delimiter is [ , ] and the character format it UTF8. For decimals, use the [.]

Prerequisites

Before creating your import file, we recommend that you define the structure of the projects and the tags that you want to put in place well in advance.

If any tags must be associated to the projects due to be imported, you must create your space’s tag structure on the Administration > Tags page.

How to structure your import file?

Depending on your offer, budget or time, you will find at the bottom of this article a template excel file that you can fill in to import your projects! Use the structure given and replace the lines with your own data.

How to structure your projects and resources (tasks, expenses, discounts)?

Each line in your file must be filled in so that it facilitates successful project creation:

  1. [project]: your project

    1. [purchase]: a expense in your project

    2. [discount]: a discount in your project

    3. [task]: a task or task group in your project

      1. [purchase]: a expense in your task group

      2. [discount]: a discount in your task group

      3. [subtask]: a task or task group in your task group

Note:

  • Each project resource must have the name of the project it’s attached to in the corresponding column [Project Name]

  • Items [purchase] and [discount] are optional

  • Items [purchase] and [discount] must come after the [projet] item to be linked to it

  • Items [purchase] et [discount] must be placed after a [task] item to be linked to a task group

  • A [subtask] item must be preceded by a [task] item

Accepted column headings and data formats

Below you will find all the accepted column headers, as well as the data formats and values expected by our import system: Headers

Business rules: information to be filled in according to project type and resource type

Project

Mandatory fields :

  • project name: the name of your project

  • resource name: must be identical to the project name

Purchase

Mandatory fields :

  • project name: the name of the project to which the purchase should be attached

  • resource name: the name of your purchase

  • purchase paid cost: the cost of your purchase, can be set to zero

  • purchase resale price: the resale price of your purchase, can be set to zero

  • purchase paid date: the effective date of purchase (yyyy-mm-dd)

Discount

Mandatory fields :

  • project name: the name of the project to which your discount should be attached

  • resource name : the name of your discount

  • discount amount: the amount of your discount

Task - placed at the root of the project

Mandatory fields :

  • project name: the name of the project to which your task should be attached

  • resource name: the name of your task

  • task budget type : the billing method (optional if you don't have the Budget package)

Depending on the type of billing chosen, other fields will need to be filled in:

Task budget type = None

Mandatory fields: none

Task budget type = Detailed (fixed fees mode)

Mandatory fields: (2 of the 3)

  • task time planned: time sold / planned

  • budget amount

  • task hourly rate

Task Budget Type = Global (package fee mode)

Mandatory fields :

  • budget amount

  • task hourly rate mode: hourly rate definition mode

  • task hourly rate: hourly rate (only if hourly rate mode = task)

Task Budget Type = Time (time ans materials mode)

Mandatory fields:

  • task hourly rate mode: hourly rate definition mode

  • task hourly rate: hourly rate (if hourly rate mode = task)

Task group creation: Task and Subtask objects

When you create a [Task] object to make a task group, you will need to create subtask objects within that group.

This section details the mandatory fields for [Task] and [subtask] objects.

Note: the [subtask] object must have the same billing type as the [task] object to which it belongs.

Mandatory fields :

  • project name: the name of the project to which your task or sub-task should be attached

  • resource name: the name of your task

  • task budget type : the billing method (optional if you don't have the Budget package)

Depending on the type of billing chosen, other fields will need to be filled in:

Task group None (non billable)

Task object - mandatory fields

  • none

Subtask object - mandatory fields

  • none

Task group Detailed (Fixed Fees)

Task - mandatory fields

  • Do not fill in the fields Time planned, Budget amount, hourly rate

Subtask - mandatory fields (2 of 3)

  • task time planned: time sold / planned

  • budget amount

  • task hourly rate

Task Group Global (Package Fees)

Task - mandatory fields

  • budget amount

  • task hourly rate mode: hourly rate definition mode

  • task hourly rate: hourly rate (if defined if the project and only if hourly rate mode = task)

Subtask - mandatory fields

  • task hourly rate mode: hourly rate definition mode

  • task hourly rate: hourly rate (if defined if the project and only if hourly rate mode = task)

Task group (Time and Materials)

Task - mandatory fields

  • task hourly rate mode: hourly rate definition mode

  • task hourly rate: hourly rate (if defined if the project and only if hourly rate mode = task

Subtask - mandatory fields

  • task hourly rate mode: hourly rate definition mode

  • task hourly rate: hourly rate (if defined if the project and only if hourly rate mode = task

Did this answer your question?