> ## 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.

# Primavera P6 XER Import

> Importing projects from Oracle Primavera P6

# Primavera P6 XER Import

Import projects from Primavera P6 by exporting as .xer format and using GlidePath's P6 importer.

## Feature Spec Reference

**Module 1.10 — Import from P6 XER**

## Exporting from Primavera P6

### Step 1: Export from P6

1. In Primavera P6, open your project
2. File → **Export**
3. Select **XER Format** (.xer)
4. Choose scope: single project or multiple projects
5. Save the file

### Step 2: Import into GlidePath

1. Open GlidePath Import dialog
2. Select **Primavera P6** format
3. Upload the .xer file
4. Column mapping happens automatically
5. Review import results

## Field Mapping

GlidePath automatically maps these P6 fields:

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

## What Gets Imported

✓ Task structure and WBS hierarchy\
✓ Activity IDs (P6 unique identifiers)\
✓ Durations (converted from hours)\
✓ Start and finish dates\
✓ Dependencies (FS, SS, FF, SF relationships)\
✓ Constraints (ASAP, ALAP, date constraints)\
✓ Progress % (% Complete)\
✓ Notes\
✓ Resource assignments\
✓ Project calendars (working days, holidays)

## What Doesn't Get Imported

✗ LOE (Level of Effort) tasks — imported as standard tasks\
✗ Resource curves — basic assignment only\
✗ Cost accounts — not mapped\
✗ Baselines — can be re-captured in GlidePath\
✗ Custom UDF fields\
✗ Budget assignments

## Known Considerations

### LOE Tasks

P6 "Level of Effort" tasks are simplified to standard tasks with duration = actual duration elapsed. You may need to adjust durations after import.

### Resource Calendars

Resource calendars from P6 are imported, but individual resource availability may need adjustment in GlidePath (Module 9).

### Duration Conversion

P6 stores durations in hours; GlidePath converts based on your project's Hours Per Day setting. Verify this is set correctly before import.

## Screenshot

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

*Import results showing task count and any warnings (e.g., LOE tasks converted).*

## Tips

* **Verify calendar:** Check that Hours Per Day matches your P6 project setup
* **Spot-check dependencies:** Review critical path and key dependencies after import
* **Test with subset:** Import a smaller project first to validate mapping

***

## Next Steps

* [MS Project Import](/import-export/03-ms-project-import)
* [Exporting Projects](/import-export/05-exporting-projects)