1. Home
  2. Blog
  3. Converting an MS Project schedule to Primavera P6: method and pitfalls

Converting an MS Project schedule to Primavera P6: method and pitfalls

Published on · Pilotis

The client requires Primavera P6, your schedule is in MS Project, or the other way round: conversion looks simple, just export and import. In practice, the two programs do not calculate the same way, and a schedule converted without checks can show a different finish date, wrong float or a critical path that no longer makes sense. Here is the method we use, and the pitfalls to know.

1. Choose the right exchange format

To go from MS Project to Primavera P6, the most reliable format is MS Project XML: P6 can import it, with tasks, links, calendars and resources. The other way round, Primavera P6 exports to XER (its native exchange format) or to MS Project XML. Avoid copying and pasting from Excel: links and calendars do not follow.

2. Prepare the source schedule

A successful conversion starts with a clean file. Before exporting:

  • Delete empty tasks and unnecessary links
  • Replace fixed dates with logic links where possible
  • Check that every task has a predecessor and a successor
  • Give tasks a stable identifier (code, text field)
  • Freeze and record the baseline to carry over

3. Calendars and durations

This is pitfall number one. MS Project stores durations in minutes and converts them to days using the hours per day set in the project (8 h by default). Primavera P6 calculates from activity calendars. If the calendar has 7 hours a day on one side and 8 on the other, every duration changes. Recreate calendars (working days, hours, holidays, site closures) before importing, and check a few long durations by hand.

MS Project elapsed durations (which count weekends) and lags expressed as a percentage have no direct equivalent in P6: they must be reworked one by one.

4. Constraints, summaries and task types

  • MS Project summary tasks become WBS nodes in P6: links placed on summaries must be moved to activities
  • “Must start on” or “Start no earlier than” constraints have P6 equivalents, but their effect on float differs: review each one
  • Task types (fixed duration, fixed work, fixed units) map imperfectly to P6 duration types
  • Milestones must be true start or finish milestones in P6

5. Baseline and progress

The baseline does not automatically become a target schedule in P6: it is carried over as a baseline project assigned to the project. For a schedule already under way, you also need to choose the P6 progress rule (retained logic or progress override) and the percent complete type (duration or physical), otherwise remaining work no longer matches reality.

6. Check before delivering

A conversion is only finished when both schedules tell the same story. Compare:

  • The number of tasks, milestones and links
  • The project finish date and key milestones
  • The critical path and total float of critical tasks
  • Resources and total costs
  • The baseline and progress at the data date

Every variance is explained in a report: either it is corrected or it is justified (for example a different calendar required by the client).

Example

Fictional example: a 3,200-task schedule moved from MS Project to Primavera P6 came out with a finish date 11 days later. The cause: a 7-hour calendar in P6 against 8 hours in MS Project, and about forty elapsed-day lags. Once calendars were aligned and lags reworked, the finish date and critical path were identical.

Scheduling support

Schedule causing trouble? A planner takes care of it.

MS Project file too heavy or corrupt, conversion to Primavera P6, clean-up, baseline: quote within 48 h, files kept confidential and deleted after the assignment.

Request a quote

The tool to take action

PERT estimate

Three estimates per task, the expected project duration, critical path, floats and the probability of meeting your deadline.

See the tool