SPM Integration with MS Project recommendations and limitations

Luis Ataide · 2 hours ago

DISCLAIMER: This article describes the import and export capabilities between ServiceNow Strategic Portfolio Management (SPM) and Microsoft Project. While both directions are supported, important limitations apply to the transfer of project structure, constraints, and calendar elements. Planning and field mapping are required for successful integrations.

The recommendation is to utilise MS Project integration for the migration process to bring in-flight projects into ServiceNow and continue managing them within ServiceNow. Although the import/export functionality is available, there are some limitations outlined below.

What problem does this solve?

Organizations often manage in-flight projects in Microsoft Project while gradually transitioning to ServiceNow for unified project governance and portfolio visibility. Rather than manually re-entering project data, SPM provides built-in import and export capabilities to facilitate this migration.

By leveraging the MS Project integration, you can import existing project structures into ServiceNow, continue managing them within SPM, and export updated schedules back to Project when needed — minimizing data re-entry and keeping both systems aligned during the transition period.

Import and Export Overview

SPM supports bidirectional data exchange with Microsoft Project:

Import: Bring Microsoft Project files into ServiceNow, creating projects and tasks mapped to the SPM structure
Export: Send ServiceNow project schedules back to Microsoft Project for stakeholder review or collaborative scheduling

For detailed procedural documentation, see:

Supported Constraints and Lag Rules

SPM supports a subset of Microsoft Project task constraints. When mapping constraints during import/export, note which are available:

Supported Task Constraints

Constraint Type	Description	Export Mapping
Start on Specific Date	Task must start on an exact date	Mapped to `Must Start On` when exported to Microsoft Project
As Soon As Possible	Task should start at the earliest available time	Supported
Start No Later Than	Task must start on or before a specified date	Supported
Start No Earlier Than	Task must start on or after a specified date	Supported

Lag and Lead Time Rules

Note: Lag units in SPM are limited compared to Microsoft Project. Plan your predecessor relationships accordingly.

Supported lag units: Days, hours, or minutes only
Lead time (negative lag): Only negative lag in days is supported; negative lag in hours or minutes is not supported
Plan relationships with these constraints in mind to avoid unexpected results during import/export

Calendar and Schedule Limitations

Certain calendar elements from Microsoft Project do not transfer into ServiceNow:

Calendar Element	Import Status
Project Calendars	Not imported
User Calendars	Not imported
Schedules	Not imported

Important: Since project and user calendars are not imported, recalculate task schedules after import to ensure SPM dates align with your organization's working calendar. You may need to manually adjust start/end dates or add calendar configurations within SPM.

Other Unsupported Elements

The following Microsoft Project elements are not supported during import or export:

Shadow tasks: Not exported when you export project data from SPM
External dependencies (inter-project links): Not exported; shadow tasks from inter-project dependencies are not imported when bringing a Microsoft Project file into SPM
Custom fields: Custom fields are not automatically mapped; they must be created in ServiceNow first and mapped before import

Workaround for Custom Fields: If you have custom fields in your Microsoft Project that must be imported, create those custom fields in your ServiceNow instance first, then establish a field mapping between the applications before initiating the import.

Field Mapping

Not all Microsoft Project fields transfer directly to ServiceNow. Refer to the official field mapping documentation to understand how fields are translated during import and export:

Project Field Mapping Reference — Maps all standard fields between Microsoft Project and SPM
Mapping Custom Fields from Microsoft Project — Step-by-step guidance for custom field configuration

Note: Only standard fields and pre-configured custom fields are imported. Plan your custom field strategy before the first import to avoid data loss.

Resource Mapping (Resource vs Assignee)

Microsoft Project and ServiceNow handle resources differently. Understanding this distinction is critical for maintaining resource assignments during import, refer to Project field mapping for details.

Unique ID and Parent Task Unique ID

Unique identifiers (UIDs) in Microsoft Project are the foundation for task matching and hierarchy during import. Understanding their role is essential for successful reimports and data consistency:

Unique ID (mpp_task_id): Every task in Microsoft Project has a unique identifier. During import, ServiceNow uses this UID to create and identify corresponding task records.
Parent Task Unique ID (mpp_parent_id): This identifies the hierarchical relationship between tasks. It ensures parent-child task structures are preserved during import.

Critical: If a Microsoft Project file is altered, recreated, or exported from a different template — even if tasks have the same name, order, and structure — the UIDs may change. When you reimport a file with changed UIDs, ServiceNow will NOT match the tasks to existing records. This can result in duplicate tasks being created rather than updating existing ones.

Integration Scenarios

Scenario 1: Import a New Project from Microsoft Project

Use case: Bringing a project into ServiceNow for the first time.

Export the project from Microsoft Project
Use the SPM Import Microsoft Project tool to load the file
A new project is created in the SPM Projects table
All compatible tasks are added to the Project Task table
Only fields that are common or mapped between the applications are imported

Note: Imported projects default to Priority = Low and Risk = Low. Update these fields in SPM after import to reflect your project's actual priority and risk profile.

Scenario 2: Reimport Changes into an Existing SPM Project

Use case: Microsoft Project remains the master, and you want to sync structural changes back into ServiceNow.

Update the project structure (add, remove, or rename tasks) in Microsoft Project
Export the updated project from Microsoft Project
Use the SPM Import tool to reimport into the existing ServiceNow project
ServiceNow treats Microsoft Project as the source of truth

Outcome:

Any task that exists in Microsoft Project but not in ServiceNow will be created
Any task that exists in ServiceNow but not in Microsoft Project will be deleted
Existing tasks are updated with current data from Microsoft Project

Important: This behavior can result in data loss if you have added tasks directly in ServiceNow that do not exist in Microsoft Project. Use this approach only when Microsoft Project is your authoritative source.

Scenario 3: Synchronize Tasks Between Systems

Use case: You have created or modified tasks in both Microsoft Project and ServiceNow, and you want to keep both systems aligned.

Start with a project in Microsoft Project that has been imported into ServiceNow
Add new tasks in ServiceNow (tasks not yet in Microsoft Project)
To keep the ServiceNow tasks and incorporate Microsoft Project changes:
- First, export the ServiceNow project to Microsoft Project
- This brings the ServiceNow-created tasks into Microsoft Project
- Update both files as needed in their respective systems
- Then, reimport to ServiceNow to pull in any Microsoft Project-side changes

Note: There is no automatic, continuous two-way sync. Use this approach for planned, periodic reconciliations rather than real-time synchronization.

Best Practice: Establish a clear handoff point and master-system authority. Avoid concurrent editing of the same tasks in both systems to minimize conflicts during sync cycles.

Data Persistence During Reimport

When reimporting a project, ServiceNow preserves certain task-level data even if the task is deleted from Microsoft Project:

Time cards associated with the task
Resource plans
Cost plans
Benefit plans
Expense lines

Note: A project task that was imported into ServiceNow earlier and has any of the above associations attached will be retained on reimport, even if the task is deleted from Microsoft Project. This protects historical data and financial records.

Key Considerations

Field mapping is required: Only fields that are common between Microsoft Project and SPM are imported automatically. Custom fields require manual creation and mapping.
Understand resource vs. assignee mapping: Resources and assignees are separate concepts. Plan your resource strategy and ensure ServiceNow users are set up before import to preserve resource assignments.
Preserve Unique IDs: Task matching depends on consistent UIDs across reimports. Always verify that your source Microsoft Project file maintains stable unique identifiers and parent task relationships.
Calendars must be reconfigured: Since project and user calendars do not import, you may need to adjust task dates or configure working calendars within SPM after import.
Choose your master system: Decide whether Microsoft Project or ServiceNow is authoritative for ongoing changes. Using one as the master minimizes sync conflicts.
Plan for lag limitations: Test predecessor relationships and lag values before importing large projects to ensure schedule calculations work as expected.
Monitor constraint mapping: Validate that task constraints map correctly, especially Start on Specific Date constraints, which map to Must Start On in Microsoft Project.
Preserve financial data: Tasks with time cards, resource plans, cost plans, benefit plans, or expense lines are retained even if deleted from the source file — plan cleanup carefully.