Import a Microsoft Project file with the Import module
-
- UpdatedJan 30, 2025
- 3 minutes to read
- Yokohama
- Project Portfolio Management
Use the Import module to import a Microsoft project file as a new project into the Project Management application.
Before you begin
Role required: it_project_manager
About this task
Before importing a Microsoft Project file into the ServiceNow instance, consider the following information.
- Microsoft Project project imported into a teamspace is only available to users who can access the teamspace.
- To import custom fields in your Microsoft project,
create those custom fields in your ServiceNow instance
first, and then create mapping between these fields before importing the
project. For more information, see Create custom field mapping for Microsoft Project file import.Note: You can also use the Scripted Extension Points for importing custom fields without creating and mapping the custom fields manually. Use the MSProjectImportTaskFormatter Extension Point to create a script include and map custom fields in Microsoft Project and ServiceNow. You can also use this Extension Point to modify the data while importing a project.
- If the calculation type is set as Manual, recalculation does not happen on project tasks when they are imported from the Microsoft Project file. Once the project is in the ServiceNow system, it would be treated as a manual project.
- Importing a Microsoft Project project with inter-project dependencies, does not import the shadow tasks.
- Only the subprojects (header and parent task) get imported into the ServiceNow instance, the child tasks are not imported.
- While importing a Microsoft Project
file into ServiceNow,
the import fails:
- If the project with tasks was created in ServiceNow instance before the import.
- If you reimport a project that was imported from Microsoft Project file earlier and you create and add
tasks in ServiceNow instance.Note: To retain the project tasks that were created in the ServiceNow instance, you must export that project first into the Microsoft Project file. Then, reimport the file back into ServiceNow instance.
- If the task being deleted due to import has any of the related entities: Cost plan, Benefit plan, Resource plan, Time card, or Expense lines.
- If the values for lag or lead time dependencies are not in the
supported format.
- Positive lag time dependency values for days, hours, and minutes are allowed. Negative lag time dependencies are allowed only for days.
- All other elapsed duration types from Microsoft Project such as emin, eday, eweek, emon, eyr, or % are not allowed for import.
Procedure
Result
- A project task that was imported in ServiceNow instance earlier and has associated time cards, resource plans, cost plan, benefit plan, or expense lines is retained on reimport even if it is deleted from Microsoft Project.
- Dates in the ServiceNow project remain same as the dates in the Microsoft Project file.
- In a ServiceNow project
with subprojects, the following details change:
- The WBS order of imported tasks is regenerated after import.
- The Planned Start Date and Planned End Date of the parent project are rolled up.
- The State of the parent project and tasks are rolled up.
- The % Complete on the top task is rolled up.