Skip to content
BestOutcome Logo
Skip to content
  • There are no suggestions because the search field is empty.

Repeated imports and Import-Export Cycles

Overview

You can:

  • Merge two project plans.

  • Perform one-way transfers multiple times.

  • Execute repeated two-way transfer cycles.

A common cycle looks like this:

  1. Work on MS Project file.

  2. Save as XML.

  3. Import to PM3.

  4. Work on the project in PM3.

  5. Export from PM3.

  6. Load the exported file into MS Project.

  7. Continue working in MS Project.

  8. Repeat as necessary.

Important Guidelines for Repeated Import/Export Cycles

1. Stay Organized with Updates

  • If you update either MS Project or PM3, synchronize the changes before updating the other.

  • Not following this can cause conflicting UIDs.

Example of a Problematic Sequence:

  1. Import from MS Project into PM3.

  2. Add items in MS Project → new UIDs not known to PM3.

  3. Add items in PM3.

  4. Export from PM3 → generates UIDs for its new items.

  5. Merge into original MS Project → UIDs clash between new items from both sides.

Important Caveats When Repeating Transfers

A. Items Are Never Deleted During Import/Export

  • If a task is deleted in PM3, but still exists in MS Project, it will reappear during import from MS Project.

  • To permanently delete an item:

    You must delete it in both PM3 and MS Project.

B. Handling Milestones and Dates

  • PM3 allows empty date fields.

  • MS Project does not.

  • If a milestone without dates is exported from PM3 and imported into MS Project:

    • MS Project will assign it a date based on the start date of its Summary Task.

    • You can change the date in MS Project, but not remove it.

  • When re-imported to PM3:

    • MS Project's assigned date overwrites PM3’s empty field.

    • The date is mapped to the rightmost non-empty field:

      1. CompletedDate, otherwise

      2. Revised(End)Date, otherwise

      3. Planned(End)Date.

C. External Dependencies

  • These link to milestones or tasks in other plans.

  • MS Project does not recognize other plans:

    • It cannot display or store external dependencies.

    • These are not included in imports or exports.

Note: Additional considerations apply to Gateways and Dependencies during the export/update/import cycle. Refer to the detailed guidance on those topics if needed.