Resources

Please review the Migration Tool Resource Import Template Sample.csv sample file attached to this article.

Minimum Data

Both resource Display Name and email address could be mapped, but at least one of those fields will be required. If the resource is flagged as generic, then the Display Name must be provided.

Finding Resources

If the resource is generic, the Display Name field is used to locate the resource. If the resource is not generic, then the email field is used to locate the resource. If the resource can be found then it will be updated, otherwise it will be added.

Source Data Format

Entering Boolean (Yes/No) Values

To populate or update any desired resource yes/no fields, the only acceptable values are currently “true” or “false”. Variations in punctuation do not matter.

Entering Date Values

To populate or update any desired resource date fields, the approved date format is 2022-05-22T00:00:01 (YYYY-MM-DDTHH:MM:SS).

Entering Numerical Values

To populate or update any desired resource number fields, ensure that values are up to 2 decimal places.

Entering (Multi-)Choice Values

To populate or update any desired resource choice fields, ensure that the GUID Id is entered for that choice. For multi-choice values, please ensure that there is a semicolon + number sign (;#) between the GUID Ids without spaces (i.e., value1;#value2). Please review the steps on how to find the GUID.

Assigning Resources to Teams

The resource import can associate resources with teams.

The team must already exist for this to work. The allocation will be set to 100%.

The source data must be in a field in the csv file that is mapped to the resource field called "Team Membership".

Enterprise Security Groups

To set the Enterprise Security Group, the Global Permissions field will still be used to set the group access for the resource. However, to set the Enterprise Security Group for new resources going forward the front-end name of the security group will now be used. For example, if the security group has the name of “Timesheet Users Type 2”, then that is the value that should be entered within the Global Permissions column in the CSV file.  

If no value is entered within the Global Permissions column, then the default value set within the OnePlan Configuration page will be set automatically. Please note that to update a resource's Enterprise Security Group, a value must be entered in the CSV file, otherwise the previously set value will stay the same.

Plans

Please review the Migration Tool Plan Import Template Sample.csv sample file attached to this article.

Minimum Data

The following fields must be in the source file and must be mapped:

• Name
• Owner
• Portfolio Plan Type
• Plan External Id

Source Data Format

SharePoint Integration Link

If the source data contains a "SharePoint Url", column and the SharePoint App is installed in OnePlan, the tool will setup the SharePoint integration for each plan where the SharePoint url is provided.

Entering Boolean (Yes/No) Values

To populate any desired yes/no fields, the only acceptable values are currently “TRUE” or “FALSE”.

Entering Date Values

To populate any desired date fields, the approved date format is 2022-05-22T00:00:01 (YYYY-MM-DDTHH:MM:SS).

Entering (Multi-)Choice Values

To populate any desired choice fields, you can use the text value of the choice. If that does not work due to the type of value of the choice, you can also use the GUID Id. Please review the steps on how to find the GUID.

For multi-choice values, please ensure that there is a semicolon + number sign (;#) between the values without spaces (i.e. Option A;#OptionB;#GUID1;#GUID2). 

Work Plans

Please review the Migration Tool Work Plan Import Template Sample.csv sample file attached to this article.

Minimum Data

The following fields must be in the source file and must be mapped:

• First column in data file is used as Unique ID field for the items
• Item Name
• Work Item Type
• Plan External Id

These fields may be required in certain scenarios:

• Task Dependencies (required only if you want to setup task dependencies)
• Parent ID (required only for hierarchy)
• Effort, Start, Due and Assigned To (required only if auto import resource plan is used)
• Duration (set to 0 if you want to import milestones)

Work Item Types

The Work Item Type (Schedule, Risks, Issues, etc.) determines where imported records will appear in the Work Plan. 

Each CSV file can contain only one Work Item Type. If you need to import items into multiple areas of the Work Plan, you must create a separate CSV file for each Work Item Type. 

CSV Requirements

• Work Item Type must be included as a column in your CSV FIle. 
  • This field is not mappable during the import process and is hardcoded based on the column name and value provided in the CSV. 
• The value provided must exactly match the front-end Work Type name (such as Backlog, Risks, Issues, etc.). 

Important Behavior to Know

If the Work Item Type column is not included in your CSV:

• All imported items will default to the Schedule, regardless of intent. 

To Import these items into other areas, you must

1. Include the Work Item Type column in the CSV
2. Use a separate CSV file for each Work Item Type. 

Finding Plans

In order to import any work plan data, the plan must exist in OnePlan. Plans are located using the Plan External Id field. The “Plan External Id” column must exist in the source data. If the plan cannot be found in OnePlan, no data will be imported.

Work Plan Items

The column name “Task Id” will be used to identify unique tasks within the source data. This is required, so any references like a parent or a dependency can use this ID.

If “Task Id” column doesn’t exist, then the first column in the source data will be used.

The data in "Task Id" must be unique for each plan and each task, otherwise the process will stop with a "For each plan, each record in the file must have a unique ID for the process to work." error.

Tip: use the unique identifier for your work plan items from the source system (like Task Id, Risk ID etc.) for this column.

Built-in Fields

The following built-in task fields can be mapped:

• Name
• Assigned To
• Assigned To Unit
• Scheduling Mode
• Ignore Resource Calendar
• Effort Driven
• Dependencies
• Dependency Lag
• Dependency Type
• Rollup
• Inactive
• Manually Scheduled
• Show in Timeline
• Note
• Constraint Type
• Constraint Date
• Duration
• Owner
• Calendar
   

The Successor field can be created in the CSV, however this field is not available as a field mapping. The integration will process the Successor field name automatically. 

Source data format 

Assigned To

Use the resource email address when assigning resources. Use the full name of a generic resource. 

If the Assigned To field in OnePlan is mapped, the Work Plan item will be assigned to that resource. To assign multiple resources to an item, use comma separated values. 

Resource Assignments and Resource Units

Each work item can have a resource assigned using the Assigned To field. The type of resource assigned determines which value the Migration Tool expects to import.

Resource assignments are based on the assigned resource's Resource Type:

When importing work plan data, the Migration Tool evaluates the resource assigned in the Assigned To field and imports the corresponding value from the appropriate CSV column:

• Assigned To Units – Used when the assigned resource is a Work resource.
• Assigned To Quantity – Used when the assigned resource is a Material resource.
• Assigned To Cost – Used when the assigned resource is a Cost resource.

Note: Only the column that matches the assigned resource's Resource Type is used during import. Values provided in other resource assignment columns are ignored for that assignment. 

Assigned To Units, Assigned To Quantity, and Assigned To Cost Behavior

If both the fields exist within the CSV or are mapped:

• The Assigned To {Units/Quantity/Cost} value (if provided) is used as entered.

• There is no maximum limit enforced on Quantity or Cost. Units are capped at 100. 

• If no Quantity value is provided, OnePlan assigns a default value of 0.1.

  • Note: When viewing this value through OData, it may appear as 0 due to rounding.

Quantity Column Present but Not Mapped

If:

• Assigned To Units is mapped, and

• Quantity exists as a column in the CSV but is not mapped,

then:

• Non-Labor resources will not receive the Quantity value from the CSV.

To ensure Quantity values are applied to Non-Labor resources, the Assigned To Quantity field must be explicitly mapped during import.

Dependencies

• If the Successor flag field is included in your CSV file and set to TRUE, the task will be created as a successor, and the specified dependency will be applied accordingly.

  • If the field is not included or is set to FALSE, the task will automatically be created as a predecessor.

  • Accepted values for this field are TRUE or FALSE (not case sensitive).

  • Note: The Successor flag is not available as a field mapping option and must be included directly in the CSV file to be recognized during import.

• Dependency Lag is a value in days and it will default to 0 if not mapped, or if it does not have a value.
• Dependency Type will default to Finish to Start, if it is not mapped or empty. 
• Dependency Type accepted values:
  • Finish To Start
  • Finish to Start
  • FinishToStart
  • FS
  • Finish To Finish
  • Finish to Finish
  • FinishToFinish
  • FF
  • Start to Start
  • Start To Start
  • StartToStart
  • SS
  • Start to Finish
  • Start To Finish
  • StartToFinish
  • SF
• For multiple dependencies use comma separated values.
• Successor, Dependency Lag, Dependence Type will all follow this logic:
  • Each field could be comma separated for multiple dependencies.
  • If the number of values in a field for that row matches the number of dependencies, each value will be applied to a dependency in the same order.
  • If only one value is provided for multiple dependencies, the same value will be used for each dependency in that row.
  • If the number of values does not match the number of dependencies, only the first value will be applied to each dependency in that row.

Constraints

• The following Constraint Types are supported: 
  "As Soon As Possible"
  "As Late As Possible" 
  "Must Start On"
  "Must Finish On"
  "Start No Earlier Than"
  "Start No Later Than"
  "Finish No Earlier Than"
  "Finish No Earlier Than"
• "As Soon As Possible" and "As Late As Possible" do not require a Constraint Date, however all others do. 

Parent tasks do not have the same Constraint Types as child tasks

Child tasks will take any of the constraints listed above, however for parent tasks, constraint types that are supported are:

• As Soon As Possible
• As Late As Possible
• Start No Earlier Than
• Finish No Later Than

All other constraint types will appear as None in the OnePlan UI. 

Scheduling Mode

The valid options for the Scheduling Mode field are: Normal, Fixed Effort, FixedEffort, Fixed Duration, FixedDuration, Fixed Units, FixedUnits. 

Everything else will be converted to Normal.

Calendar

To populate the calendar field ensure that the GUID Id is entered. The GUID can be found in the configuration on the Calendar page.

Entering Boolean (Yes/No) Values

To populate any desired yes/no fields, the only acceptable values are currently “TRUE” or “FALSE”.

Entering Date Values

To populate any desired resource date fields, the approved date format is 2022-05-22T00:00:01 (YYYY-MM-DDTHH:MM:SS).

Entering Choice Values

To populate any desired choice field, use the GUID or the choice value. Please review the steps on how to find the GUID if you want to use that.

Entering (Multi-)Choice Values

To populate any desired choice fields, you can use the text value of the choice. If that does not work due to the type of value of the choice, you can also use the GUID Id. Please review the steps on how to find the GUID.

For multi-choice values, please ensure that there is a semicolon + number sign (;#) between the values without spaces (i.e. Option A;#OptionB;#GUID1;#GUID2). 

Resource Plans

Please review the Migration Tool Resource Plan Import Template Sample.csv sample file attached to this article.

Minimum Data

The following fields must be in the source file and must be mapped:

• Plan External Id
• Resource
• Cost Type Name
• Cost Date
• Hours

Finding Plans

In order to migrate any resource plan data, the parent plan must exist in OnePlan first. Plans are located using the Plan External ID field. If the plan cannot be found, no data will be updated.

Finding Resources

All resources within the CSV file must exist in OnePlan for the Resource Planner to allocate time in the resource planner. The Resource field is used to locate the resources by email address.

Source Data Format

Resource

 The resource’s email address is expected in this field.

Boolean (Yes/No) Values

To populate Yes/No fields in your Resource Plan:

• Enter true (lowercase) in the CSV cell to mark the checkbox as checked.
• Leave the cell blank to leave the checkbox unchecked.

Choice Values

To populate choice fields, you’ll need the GUID ID for each choice from OnePlan. Please review the steps on how to find the GUID.

Financial Plans

Please review the Migration Tool Financial Plan Import Template Sample.csv sample file attached to this article.

Minimum Data

The following fields must be in the source file and must be mapped:

Finding Existing Plans

In order to migrate any resource plan data, the parent plan must exist in OnePlan first. Plans are located using the Plan External ID field. If the plan cannot be found, no data will be updated.

Source Data Format

Cost Date

The cost date values should be in the format of 2026-05-01T00:00:01 (YYYY-MM-DDTHH:MM:SS).

Use the first of the month for monthly time phasing.

Cost External Id

The cost category must be located for each record in the source file. The Cost External Id field is used for that.

If global cost categories are used and the cost category is not part of the cost type that is specified in the file, then the parent cost category will display the data. If there is no parent, then no data will be imported.

Cost Type Name

The cost type name must be located for each record in the source file.

In OnePlan, there are default cost type names like Budget, Forecast, Actuals. You can add, edit, or delete these cost types based on the requirements.

Cost Name

The cost name is the cost category name that will be created from the source file if it does not exist already in OnePlan and the custom cost categories are used.

Cost Value

The expected cost value can be a positive or negative number, and can take up to two decimal places.

Parent Cost External Id

This field will provide guidance to determine the placement or insertion of a cost category within your financial planner if it does not currently exist. When adding a new cost category, it should be linked as a child to an existing parent cost category. If no parent cost category is specified, the system will create the cost category at the root level. 

Plan External Id

This field is used to locate the plan that the data should be imported into.

Detail Row External ID

This field is used to locate the detail row. If the detail row can be found by ID, then the data will be updated.

Use Detail Row

This is the only field that must be named exactly as "Use Detail Row". If it is missing from the source file, then it is assumed that the record is not using a detail row. 

If the value in this field is "Yes", then the detail row will be updated with the data, otherwise the data will be written to the cost category.

Detail rows roll up to cost categories. You cannot set the value of a parent cost category directly if you decide to use detail rows.

How To

Locating GUIDs for Choice and Multi-Choice Fields

To use a choice field, first you need to locate the GUID. The method is the same for the different types of fields like plan, resource, etc.

The GUID for a choice value is exposed in the UI in the ID field.

As an example, the steps for resource fields:

1. Open the OnePlan Configuration page by clicking on the Settings (gear) icon.
2. Go to Fields in the Admin Navigation, expand Resource Fields.
3. Locate the choice field desired and click on the Edit icon. 
4. The Edit Choices form will open.
5. In the column title, click on the dropdown arrow to expand the options available, select Columns, and select Id. These values are the GUIDs for the specific choice options.

Note: If the GUIDs do not match, no value will populate.

• Migration Tool Financial Plan Import Template Sample.csv338 Bytes
• Migration Tool Resource Plan Import Template Sample.csv420 Bytes
• Migration Tool Plan Import Template Sample.csv452 Bytes
• Migration Tool Resource Import Template Sample.csv308 Bytes
• Migration Tool Work Plan Import Template Sample.csv1 KB