Import your schedule into Owl
If you already have a schedule in Primavera P6 or Microsoft Project, you don't have to rebuild it. Import the file and Owl brings in the activities, the work breakdown, the calendars, the relationships and the progress recorded so far, then runs the schedule so you can work with it: check it against guardrails, run risk on it, chart it, or keep planning with Owl.
If you're starting from written scope instead of a schedule file, see Build a schedule from documents.
Before you start
Have your schedule file ready in one of these formats:
.xer— Primavera P6 export- P6
.xml— Primavera P6 XML - MS Project
.xml— Microsoft Project XML .mpp— Microsoft Project
Step 1 — Open the import window
In the top bar, click Transfer, then Import schedule….
1231Drop your file here, or click to browse. Owl reads XER, P6 XML, MS Project XML and MPP.2Choose what the file becomes.3The button names what will happen, here Import as Main Schedule.
Drop your file on the upload area, or click it to browse.
Tip: You can also drag a schedule file straight onto the project. Dropped on an empty project, it's imported as the main schedule; dropped on a project that already has a schedule, it opens this window with the file filled in.
Step 2 — Choose what the file becomes
Importing isn't only for starting a project. Owl asks what the file should become:
- Main schedule — import as the project's primary schedule. Use this when the project is empty or the file is the schedule of record.
- Scenario — bring it in as a separate copy you can compare with the main schedule and merge later. Give it a name. Use this to weigh a resequence or a contractor's alternative without touching your plan.
- Snapshot in the past — store it in the schedule history as of a date, without changing the live schedule. Enter the As-of date and an optional label. Use this to load earlier monthly updates so trend charts and anomaly checks have something to compare.
- Attach for the agent — add the file as reference material Owl can read, for example a schedule you want Owl to revise or borrow sequencing from.
Pick one and click the button at the bottom. It names what will happen: Import as Main Schedule, Save Snapshot, and so on.
Tip: Load a series of monthly updates as Snapshot in the past to light up the trend and anomaly views. Import each update as a snapshot rather than overwriting the main schedule.
Step 3 — Answer Owl's questions, if it has any
Some files need a decision before Owl can bring them in. When that happens, the window asks:
- This file contains 3 projects — pick the one to import. Baseline copies are listed but marked, and the most likely project is selected for you. To bring in another, run the import again.
- This project already has 437 activities — Merge into the schedule updates activities that share an ID and adds the rest; activities that aren't in the file are left alone. Cancel import stops without changing anything.
- This update is newer than your live schedule — after a snapshot import, if the file's data date is later than your live schedule's, Owl offers Make it the live schedule. Keep it in history only leaves the live schedule as it was.
Step 4 — Name the revision
When a main-schedule or snapshot import finishes, Owl offers to name the version it just created, with a suggested name built from the label and data date. An imported file is often the update you submitted to the owner, so naming it now (Rev 2, October update) puts it under Revisions in Schedule history, where you can find it and compare later versions against it. Skip it if you don't need it; you can name any version later.
If the file's import date is after its data date, the revision carries an Imported later tag, so nobody mistakes when it was really current.
Step 5 — Review what came in
Open the Schedule tab to see the imported schedule, with its work breakdown, calendars, dependency links and recorded progress in place. From here it works exactly like a schedule Owl built.
Heads up: An import brings the schedule's structure and progress — activities, WBS, calendars, relationships, actual dates. Resource assignments in the file are not imported. Check anything resource- or cost-dependent (for example risk or an EVM dashboard) against the original before you rely on it.
You can also hand Owl the file in the chat:
What to do next
- Check the imported plan — Find issues with your schedule runs Owl's guardrails over it and flags dangling logic, out-of-window work, and more. It's worth doing right after any import.
- Keep working — talk to Owl to extend or resequence the schedule; every change re-runs the dates and re-checks your guardrails.
