> ## Documentation Index
> Fetch the complete documentation index at: https://docs.glidepathcpm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MS Project XML Import

> Importing projects from Microsoft Project

# MS Project XML Import

Import projects from Microsoft Project by exporting as .xml format and using GlidePath's MS Project importer.

## Feature Spec Reference

**Module 1.9 — Import from MS Project XML**

## Exporting from MS Project

### Step 1: Export from MS Project

1. In MS Project, open your project
2. File → **Save As**
3. Select **Microsoft Project 2010 XML** (.xml) format
4. Save the file

### Step 2: Import into GlidePath

1. Open GlidePath Import dialog
2. Select **MS Project XML** format
3. Upload the .xml file
4. Column mapping happens automatically
5. Review import results

## Field Mapping

GlidePath automatically maps these MS Project fields:

| MS Project Field | GlidePath Field                         |
| ---------------- | --------------------------------------- |
| Name             | Task Name                               |
| ID               | Activity ID                             |
| WBS Code         | WBS                                     |
| Duration         | Duration (converted from hours to days) |
| Start            | Start Date                              |
| Finish           | Finish Date                             |
| % Complete       | Progress %                              |
| Constraint Type  | Constraint Type                         |
| Constraint Date  | Constraint Date                         |
| Notes            | Notes                                   |
| Resource Names   | Resource Assignment                     |

## What Gets Imported

✓ Task names and WBS structure\
✓ Durations (converted from hours based on project calendar)\
✓ Start and finish dates\
✓ Dependencies (FS, SS, FF, SF relationships)\
✓ Constraints (ASAP, ALAP, date constraints)\
✓ Progress % (if captured in MS Project)\
✓ Notes\
✓ Resource names (basic association)

## What Doesn't Get Imported

✗ Resource calendars (availability)\
✗ Cost data (budgets, rates)\
✗ Custom fields\
✗ Baselines (you can re-capture baseline in GlidePath)\
✗ Attachments or linked documents

## Lag Conversion

MS Project stores lag in minutes; GlidePath converts to days:

* **480 minutes lag = 1 day lag** (8-hour working day)
* Conversion respects your project's Hours Per Day setting

## Screenshot

<img src="https://mintlify.s3.us-west-1.amazonaws.com/glide-path/assets/screenshots/07-03-import-results-dialog-after.png" alt="Import Results Dialog" />

*Import results dialog showing task count, warnings, and any errors.*

## Tips

* **Verify calendar:** GlidePath assumes 8 hours/day; adjust if MS Project uses different hours/day
* **Check dependencies:** Review the Gantt chart after import to verify dependencies are correct
* **Test first:** Import a small project first to verify field mapping

***

## Next Steps

* [Primavera P6 Import](/import-export/04-primavera-import)
* [Exporting Projects](/import-export/05-exporting-projects)