Esc

↑↓ move↵ openIndex · Pagefind
Scheduling / Import from Primavera P6 and Microsoft Project

Import from Primavera P6 and Microsoft Project

Bring in P6 XER, P6 XML and Microsoft Project XML schedules, review what was read, keep the original file byte for byte, adopt the schedule into the native CPM Planner, or update the current plan from a file with P6-style import options.

On this page

Most schedules start life in Primavera P6 or Microsoft Project. os.construction reads P6 XER, P6 XML and Microsoft Project XML (MSPDI), keeps the original file exactly as uploaded, and can adopt the schedule into the native Planner. There the P6-validated engine calculates it and every planning and analysis tool applies.

Supported files

Format Extension Notes
Primavera P6 XER .xer Export one project per file for the field snapshot. The engine reads projects, WBS, activities, relationships, calendars, constraints and P6 scheduling options.
Primavera P6 XML .xml Detected from the file contents.
Microsoft Project XML (MSPDI) .xml Save from Project as XML.

Files must be UTF-8 and up to 32 MiB, which fits enterprise schedules of 10,000 to 30,000 activities. The format is detected from the contents, and the extension must match. Microsoft Project .mpp files aren’t supported; save them as XML. See Large schedules and time precision for the limits that apply after import.

The import flow

  1. Upload. Open Schedule › Import file (or New schedule › Import a file) and choose the file. A preview is created and the original file is kept as a retained source.
  2. Review. The review page lists what was read and the import limitations for this file, before anything is written.
  3. Commit the field snapshot. Committing creates the field schedule’s tasks, resources and assignments from the file. If source IDs collide with existing tasks that have no matching import history, it’s refused rather than merged.
  4. Adopt it into the Planner. In a Planner with no saved version yet, use the Start from the retained schedule panel. The conversion runs the engine on the retained source and shows a preview with any adoption blockers, such as no activities to adopt or an invalid WBS. Adopting requires that exact preview, so a source that changed after you reviewed it can’t slip in.
  5. Calculate. Once it’s adopted, you work in the Planner: calculate, baseline, analyse and trace.

Update the current plan from a file

Once the project has a saved plan, a new file doesn’t have to start a separate revision. P6’s import options are on the import’s review page, in the Update Current Plan (P6 Import Options) panel. They work for XER, P6 XML and Microsoft Project XML sources.

Import modes

Mode What happens
Update existing plan The file is matched to the plan and each object type follows the action you choose for it.
Replace existing plan The file becomes the plan. Every type is set to Delete Existing, and notebooks and project settings come from the file. Matched activities still keep their identities.
Add into WBS node Every activity, relationship, WBS node and assignment in the file is added as new work under the WBS node you pick. Nothing existing is changed or deleted. Calendars, resources, codes and UDFs are still matched, so shared dictionaries aren’t duplicated.

Creating a separate plan from the file is the usual path: commit the import, then Convert to CPM plan.

Actions per object type

In Update existing plan, choose an action for each of Activities, Relationships, WBS, Calendars, Activity codes, User-defined fields, Resources, Resource assignments, Notebooks and Project settings:

  • Update Existing: matched objects take the file’s values, new objects are inserted, and objects only in the plan stay.
  • Insert New: matched objects stay as they are, new objects are inserted, and objects only in the plan stay.
  • Keep Existing: nothing of this type changes, and new objects are skipped.
  • Delete Existing: like Update Existing, and objects in the plan but not in the file are deleted.

Notebooks and project settings take only Update Existing or Keep Existing. The defaults follow P6: update the network, codes, UDFs and assignments; insert new calendars and resources; keep your notebooks and project settings. So your local notebook entries survive unless you choose otherwise.

How objects are matched

  • Activities match by the P6 GUID kept from an earlier import, when both sides have one, else by Activity ID.
  • WBS nodes match by GUID, else by their code path. Calendars and resources match by ID, else by name. Relationships match by predecessor and successor, and assignments by activity and resource.
  • A matched object keeps its identity in the plan, so its history, links and baselines still line up. A new object keeps the file’s ID unless it’s taken, in which case it gets the next free ID-n, and the preview lists every rename.
  • An object the result still uses is never deleted.
  • Calculated fields, such as dates, float and critical flags, are never compared; the engine recalculates them.

Preview and apply

  1. Choose the mode and, for Update existing plan, the action for each object type. For Add into WBS node, choose the node.
  2. Preview changes. The preview counts what’s inserted, updated, deleted, unchanged, kept and skipped for each object type, lists warnings and renamed objects, and shows a sample of up to 50 activity changes with each field’s before and after value. Nothing is written.
  3. Apply. Apply as plan version N saves one new version through the same checks as a Planner save, calculates it and records an audit event. If the plan or the file changed since the preview, the apply is refused and asks you to review again.

The previous version stays in history, so you can compare the update with what came before or go back to it. Through the API, use POST /schedule/imports/{import_id}/merge/preview and /apply (Schedule API).

To change many fields without a P6 file, use the Excel round-trip instead: see Round-trip the activity table through Excel.

What carries across

Adopting into the Planner keeps what the CPM engine needs, and more: activities and kinds, WBS, durations and remaining durations, actual dates, all four relationship types with lags, calendars (including detailed shifts, which are kept exactly), primary and secondary constraints, P6 scheduling options such as the progress mode, resource assignments with units % complete and cost accounts, activity codes, user-defined fields including indicators, steps, notebooks, notes to resources and feedback, expenses, resource curves and per-WBS earned value settings. P6 financial periods and P6 XML baselines are kept for export. Time precision is detected automatically from the file. The engine then calculates the dates itself instead of trusting the dates stored in the file.

The field snapshot is simpler on purpose. It shows dates as calendar days without recalculating them, makes WBS nodes summary tasks, rounds progress to whole percent and doesn’t import critical flags. Costs, resource quantities, calendars, baselines and notes stay in the retained original.

Getting the original back

Download Original on the import review page returns the exact bytes you uploaded, with a SHA-256 header so you can prove it’s unchanged. If the stored file fails its integrity check, the download is refused rather than served.

Exporting the plan as it stands now

Export the current plan, or any saved version, as P6 XER, P6 XML or MSPDI: use Export Current Plan (XER) or (P6 XML) on the import review page, Export XER or Export P6 XML on the schedule Overview, or the API. The export recalculates the version and writes your edits, including activity codes, UDFs, steps, notebooks and assignments, together with the P6 metadata kept from the original import. P6 compatibility lists exactly what round-trips and what doesn’t.

  • Mistake: Expecting P6 to re-read your edits from the original file

    In the app: The original is unchanged by design. Use Export to get the current plan.

  • Mistake: Exporting a whole P6 database into one XER

    In the app: Export one project per file. The field snapshot refuses multi-project XER files, and says so.

  • Mistake: Trusting the dates in the file

    In the app: Adopted schedules are recalculated by the engine. Compare the result with the P6 dates to catch differences in settings.

  • Mistake: Choosing Replace to bring in a monthly update

    In the app: Replace deletes everything that isn’t in the file. Use Update existing plan, and keep notebooks and settings on Keep Existing.

  • Mistake: Losing the original after edits

    In the app: The uploaded file is retained byte for byte, with a SHA-256 check on download.

Keep exploring

Related across os.construction

Run it on your own project.

Start a 14-day free trial. Want a say in what ships next? Join the founding program.

Your role (optional)

14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →

Ask the OS

Reading this page

Ask anything about this page. Answers use what you're reading as context.

Suggested

    AI · may be imperfect · sample data where shown

    Open file