Part of successfully importing items/objects into PSA is the PSA Microsoft Excel Import template (in .xlsx), which contains the necessary predefined tabs which allow you to specify the item/object properties to import.
Click here to view the article detailing how to import items/objects using Excel.
PSA Microsoft Excel Import Template: Projects sheet
This article is designed to facilitate the smooth import of projects into PSA using the Excel Import Template (.xlsx). It outlines the available fields, offering administrators concise descriptions to populate their Excel templates effectively. This resource aims to simplify the process, ensuring seamless project imports.
Let us delve into the key fields and empower you to efficiently transfer your project data into PSA.
Caution: Please be advised that it is recommended to fill all fields, even if no changes are intended. Leaving fields blank may result in some values reverting to their default settings.
| Project Property Import Fields | Definitions |
|---|---|
| Tenrox_Excel_Process_Status | Import status (populated by the system after the project import is processed) |
| UniqueId | - Upon Creation: The Unique ID of a new Project is automatically populated by the system once the creation process is completed. - Upon Update: The Unique ID of Projects being updated must be entered by you, ensuring it matches the one initially generated by the system during the initial import. For further details on how to extract this Unique ID refer to Create a Report to View Unique Ids. Note: Do not edit this column if you are creating a new Task using Excel Import. |
| Name * | Defines the Name of the project (required field) |
| Alias * | Defines the Project Code used identify the project (required field) |
| Project_Parent_Name | Defines the Name of the Project under which a new project is created/Project being modified or moved |
| Start_Date | Project start date Note: Set column format to Date ( MM/DD/YYYY). For Open Ended enter 11/27/2737 |
| End_Date | Project end data Note: Set column format to Date (MM/DD/YYYY). For Open Ended enter 11/27/2737 |
| Id | Project ID |
| Description | Description of the project |
| Phase_Name | Defines the Name of the phase associated to the project |
| Client_Name | Defines the Name of the client associated to the project |
| Manager_Logon_Name | Defines the Logon name of the Manager associated to the project |
| Manager_Last_Name | Defines the Last name of the Manager associated to the project |
| Manager_First_Name | Defines the First name of the Manager associated to the project |
| Alternate_Manager_Logon_Name | Defines the Logon name of the Alternate Manager associated to the project |
| Alternate_Manager_Last_Name | Defines the Last name of the Alternate Project Manager associated to the project |
| Alternate_Manager_First_Name | Defines the First name of the Alternate Project Manager associated to the project |
| Is_Placeholder | Defines whether or not the project is a placeholder Note: Enter 1/0 for Yes/No. |
| Is_Suspended | Defines whether or not the project is suspended Note: Enter 1/0 for Yes/No. |
| Override_Funded | Defines whether or not the Funded attribute is overridden at the project level Note: Enter 1/0 for Yes/No. |
| Funded | Defines whether or not the Funded attribute is set at the project level Note: Enter 1/0 for Yes/No. |
| Override_RandD | Defines whether or not the R&D attribute is overridden at the project level Note: Enter 1/0 for Yes/No. |
| RandD | Defines whether or not the R&D attribute is set at the project level Note: Enter 1/0 for Yes/No. |
| Override_Capitalized | Defines whether or not the Capitalized attribute is overridden at the project level Note: Enter 1/0 for Yes/No. |
| Capitalized | Defines whether or not the Capitalized attribute is set at the project level Note: Enter 1/0 for Yes/No. |
| Payable | Defines whether or not the Payable attribute is set at the project level Note: Enter 1/0 for Yes/No. |
| Override_Billable | Defines whether or not the Billable attribute is overridden at the project level Note: Enter1/0 for Yes/No. |
| Billable | Defines whether or not the Billable attribute is set at the project level Note: Enter 1/0 for Yes/No. |
| Priority | Priority level of the project Note: (Enter 1 for Low, 2 for Medium, 3 for High, 4 for Important and 5 for Urgent) |
| Portfolio_Name | Name of the portfolio associated to the project; set to the system default portfolio on import if field is left empty |
| Project_Workflow_Name | Name of the Project Workflow associated to the project; set to the selected portfolio's project workflow if field is left empty |
| Booking_Type | Defines the default project Booking Type: 1-Hard Booking 2-Soft Booking |
| Disable_Financial_Planner | Defines whether or not the Financial Planner is disabled for this Project. Note: 1/0 for Yes/No. |
| Time_Entry_Notes_Option | Defines the Projects Entry Notes option. Note: Enter TEMPLATESETTINGS, REQUIRED or NOTALLOWED or OPTIONAL. |
| Project_Health | Defines the Project Health. Note: Enter GREEN, YELLOW or RED. |
| Manager_Auto_Approved | Defines whether or not the Auto Approval is on. Note: Enter 1/0 for Yes/No. |
| Can_Be_Invoiced | Defines whether or not the Project is used for Invoice. Note: Enter 1/0 for Yes/No. |
| Allow_User_To_Edit_ETC | Defines whether or not users can edit the ETC. Note: Enter 1/0 for Yes/No. |
| Program_Name | Associated Program name. |
| Used_By_Time | Defines whether or not the Project is used by Time. Note: Enter 1/0 for Yes/No. |
| Used_By_Expense | Defines whether or not the Project is used by Expense. Note: Enter 1/0 for Yes/No. |
| Used_By_Charge | Defines whether or not the Project is used by Charge. Note: Enter 1/0 for Yes/No. |
| Used_By_Product | Defines whether or not the Project is used by Product. Note: Enter 1/0 for Yes/No. |
| Used_By_Resource_Planning | Defines whether or not the Project is used by Resource Planning. Note: Enter 1/0 for Yes/No. |
| Override_Payable | Defines whether or not the Payable attribute is overridden at the project level. Note: Enter 1/0 for Yes/No. |