Data Import

Migrating from one tool to another can be quite a task. To make it a bit easier for you, import resources, projects, tasks, and custom data fields. You can import all of them together or each one separately. 

Must-Know About This Feature

To import tasks, you must have at least one resource. If a project or a resource already exists in Ganttic with the title you enter to the import, the data will be overwritten. I.E. the data in Ganttic will be replaced with the data from the import. However, that rule does not apply to tasks. If you import a task with a title that already exists in Ganttic, a new task with the same title will simply be added to your timeline.

The first row of each column is the row you really need to pay attention to. That's the row that will determine the type of the data that is being imported. You can enter the data to the columns in a random order since the columns are defined by the first row. You can use "," as well as ";" to separate the columns. All the column titles are case-sensitive, including custom data fields’ titles. If there isn’t a match for the column title, the import is aborted. The data that you enter can be in quotes. 

RESOURCE DATA

To import resources, you must have a column with resource titles. The column must be titled with Res_Title_N. You can add custom data fields to resources using the column title Res_N_Data(Title of the custom data field)

Mandatory column: Res_Title_N (resource title; N – the queue number 1…n, needed if there are tasks that are connected to multiple resources; see the examples below)

Non-mandatory column title: Res_N_Data(Title of the custom data field)

Example for exporting only resources: 

Res_Title_1;

Res_1_Data (Location);

Res_1_Data (Resource Group);

Res_1_Data (Resource Type)

Laura;

London;

Project Managers;

Senior Project Manager

James;

London;

Designers;

UI Designer

Jennifer;

Chicago;

Management;

Marketing Manager

Meeting Room 1

Tokyo;

Facilities;

Meeting Room


PROJECT DATA

To import projects, you must have a column with project titles. The column must be titled with Project_Title. As it was with resources, you can add custom data fields to projects using the column title Proj_Data(Title of the custom data field).

Mandatory column title: Project_Title

Non-mandatory column title: Proj_Data(Title of the custom data field) 

Example for exporting nothing but projects: 

Project_Title;

Proj_Data(Status);

Proj_Data(Start Time);

Proj_Data(Deadline);

Proj_Data(Manager)

#78941;

In progress;

2017-09-04;

2017-11-30;

Laura

#78942;

Delayed;

2017-08-31;

2017-10-15;

Laura


TASK DATA

To import tasks, you must have a column for the start and end date and time of the tasks (Task_Start_Date_Time; Task_End_Date_Time). You can but don't have to add a title column (Task_Title) or columns for custom data fields [Task_Data(Title of the custom data field)]. Also, it's not needed to have specific task times. You can use dates only but in this case times have to be marked as 00:00.

Mandatory column titles: Task_Start_Date_Time; Task_End_Date_Time.

Non-mandatory column titles: Task_Title; Task_Data(Title of the custom data field)

Example for importing tasks only:

Res_Title_1;

Res_Title_2;

Res_Title_3;

Project_Title;

Task_Title;

Task_Start_Date_Time;

Task_End_Date_Time;

Task_Data(Task Status)

Laura;

James;

Meeting Room 2;

#78941;

Meeting;

2017-09-11 08:00;

2017-09-11 10:00

Finished;

James;

;

;

#78941;

UI Mockup;

2017-09-11 10:00;

2017-09-15 16:00

In progress;

Jennifer;

Laura;

London;

;

Marketing plan;

2017-09-11 13:00;

2017-09-11 16:00

Finished;

NB! The mandatory date and time format is yyyy-MM-dd HH:mm. If the start and/or finish time of the task is not given with 15-minute accuracy, it will be rounded up. 

NB! If you have all-day tasks and tasks that are not all-day tasks, import them separately.

CUSTOM DATA FIELDS

When importing custom data fields, you must assign a resource, a project, or a task to it.

NB! You can only add values to custom data fields with the import function. You must create the actual custom data fields in Ganttic beforehand. 

You can only add values to custom data fields using import. You can’t add any new custom data fields. If there isn’t a custom data field in Ganttic with the title that is in the import file, the import will be aborted. If the custom data field has a value in Ganttic but you enter a new value to the import file, the value that already excited in Ganttic will be overwritten. When you add a LIST type of custom data field value to the import, that doesn't exist in Ganttic, the missing value is automatically added (i.e. you add a new value to the list of values). The mandatory format for DATE type of custom data fields is: YYYY-MM-DD

NB! You can’t import LINK or USER type of custom data fields.

Example for importing everything at once:

Task_Title;

Task_Start_Date_Time;

Task_End_Date_Time;

Task_Data(Task Status)

Project_Title;

Res_Title_1;

Res_Title_2;

Res_Title_3;

Meeting;

2017-09-11 08:00;

2017-09-11 10:00

Finished;

#78941;

Laura;

James;

Meeting Room 2;

UI Mockup;

2017-09-11 10:00;

2017-09-15 16:00

In progress;

#78941;

James;

;

;

Marketing plan;

2017-09-11 13:00;

2017-09-11 16:00

Finished;

;

Jennifer;

Laura;

London;