# Import a plan from Primavera P6

Teamhood imports a Primavera P6 project from the XML file that P6 exports. It cannot read an XER file, so export the project as XML.

## Export the project as XML

1. In P6 Professional, open the project. Teamhood reads only the first project in a file.
2. Choose **File** → **Export**.
3. Choose **Primavera P6 - (XML)**, then **Next**.
4. Clear **Export XML file to a compressed file**. Teamhood reads an `.xml` file, not a zip file.
5. Select **Finish**.

## Import the XML file

1. Select **+** at the top of the sidebar, then **Import**.
2. Drop the `.xml` file, or select the drop area to pick the file. The file can be up to 10 MB.
3. On **Placement**, check **Create an item for the project**. The project then becomes one item, with its WBS elements and activities under it. The option is on by default while **Place under** is **No parent**, and off when you choose an item there.
4. On **Map fields**, keep the **Primavera ID** column mapped. A first import maps it to a new text field named Primavera ID, when your role may create fields. A later import can match items by it.
5. On **Review**, select the import button, such as **Import 672 items**.

A P6 layout saved as a CSV file also imports. A CSV file with two or more P6 column titles, such as **Activity ID** and **Activity Name**, is read as a P6 table.

## What is left out

- Every project in the file after the first one.
- Baselines, calendars and holidays.
- Constraints.
- Costs, and nonlabor and material resources.
- User-defined fields, activity codes and notebooks.
- Total float and free float. Teamhood works out float from its own plan.

## What works differently from P6

- An activity becomes an item, and a WBS element becomes a parent item. The import gives a WBS element no dates of its own, so the parent shows the span of the items under it.
- All four relationship types carry over. P6 counts lag in hours, and Teamhood counts it in whole working days. The import divides the lag by the hours per day of the predecessor's calendar and rounds it.
- In an XML file, Start and Finish are the activity's current dates. The planned dates come as the **Planned start** and **Planned finish** columns.
- A Start Milestone and a Finish Milestone both become a milestone, an item with a **Duration (d)** of 0. Teamhood has one kind of milestone, at the end of its day.
- Labor resources are matched to people and teams by name.
- Only the status Completed marks an item completed. Any other status is imported as not completed.
- A WBS category becomes a tag, when your organization has a **Tags** field.
- Teamhood has one kind of constraint, the pin. A **Start** you set becomes a pin, the earliest start the item may have.
- Scheduling uses one calendar for the whole organization: Monday to Friday, minus the organization's holidays. Add the holidays in Teamhood.
- Capture a new baseline on a Gantt after the import.

> **The import keeps the dates that P6 calculated.** It does not reschedule them, and a first import sets no pins. When an activity changes later, the items that depend on it move to the earliest date their dependencies allow.

## Importing again

> **Importing the plan again without matching creates its WBS elements and activities a second time.** To update them instead, select **Update matching items** on **Map fields**.

A re-import that changes the **Start** of an existing item pins that item.

## Next

- [How re-importing a plan works](../re-importing-a-plan/)
- [How dependency scheduling works](../../how-it-works/dependency-scheduling/)
- [Set your organization's holidays](../../get-started/set-holidays/)