Skip to main content

Microsoft Project XML Import and Export on Mac, iPad, and iPhone

A planning team exchanging project schedules with XML across Mac, iPad, and iPhone

Even if you plan entirely on Apple hardware, Microsoft Project rarely disappears from your work life. Clients send schedules built on Windows desktops, and PMO teams still ask for deliverables in MS Project format. QuickPlanX reads and writes Microsoft Project XML (.xml) files on Mac, iPad, and iPhone so you can bring existing schedules into your workspace or hand a finished plan back to a Windows-based stakeholder.

What XML Import and Export Actually Does​

A planning team using XML as a schedule handoff between project tools and Apple devices

Microsoft Project saves schedules in a proprietary binary format (.mpp), which requires a Microsoft license or viewer to open. Exporting that schedule as .xml produces an open file that QuickPlanX can read and write directly.

Think of XML exchange as a clean point-in-time handoff. When you import, you take an XML file saved out of MS Project and turn it into a native QuickPlanX project. When you export, you package your QuickPlanX schedule—or a single phase of it—into an XML file that MS Project can open. The two apps do not maintain a live connection after the file changes hands; once a schedule is imported, you manage it inside QuickPlanX.

For the operational steps, see Microsoft Project Integration.

What Data Transfers in the XML Exchange​

A planning team reviewing core schedule data that travels through Microsoft Project XML

The structural backbone of a schedule carries across in both directions:

  • Task hierarchy — phases, sub-phases, summary tasks, and individual tasks at any depth
  • Task names and notes — text descriptions and notes attached to each item
  • Dates and durations — start dates, finish dates, and working-day durations
  • Dependencies — Finish-to-Start links connecting predecessors and successors
  • Milestones — zero-duration checkpoints
  • Resources and progress — resource names, assignments, work, cost data, percentage complete, and actual work values

For most day-to-day schedules, the imported file opens with its work breakdown structure and resource assignments intact.

What Does Not Transfer​

QuickPlanX and Microsoft Project make different design trade-offs. QuickPlanX is built for fast, direct schedule manipulation on Apple devices rather than enterprise-scale complexity, so features unique to one application are omitted when moving to the other.

When exporting from QuickPlanX to MS Project, visual and attachment layers stay behind. Task colors, icons, attached photos, and display settings are specific to QuickPlanX and have no place in the MS Project XML schema.

Going the other way—from MS Project into QuickPlanX—strips out scheduling mechanics that QuickPlanX intentionally omits:

  • Baselines — QuickPlanX does not track separate baseline snapshots, so baseline fields in the XML are ignored.
  • Sub-day durations — QuickPlanX schedules at day-level granularity; hour-level task durations from MS Project are rounded or dropped.
  • Non-FS link types and lag/lead time — QuickPlanX supports Finish-to-Start dependencies and its own Simple Linked List mode. Start-to-Start (SS), Finish-to-Finish (FF), Start-to-Finish (SF), and dependency lag or lead offsets do not map across (see Link Style).
  • Manual vs. auto-scheduled modes — QuickPlanX treats all task dates as direct start and finish values without a separate manual-scheduling mode.
  • Enterprise and custom fields — enterprise resource fields, custom VBA-linked attributes, consolidated multi-project structures, and MS Project visual formatting are not imported.

Because of those differences, especially around link types and sub-day durations, check the timeline and critical path in QuickPlanX right after importing an MS Project file.

Exporting From QuickPlanX to Microsoft Project XML​

A planning team importing and exporting project schedules through XML files

You can export a complete project or isolate a single task branch as Microsoft Project XML. Branch export is helpful when a client or contractor only needs one phase of a larger master plan.

On Mac: Click the ··· toolbar button and choose Export → MPP XML for the full project. To export a single branch, right-click the summary task and select Export → MPP XML.

On iPad and iPhone: Select the summary task, tap ··· on the action bar, and choose Export → MPP XML.

Step-by-step details are covered in Microsoft Project Integration: Exporting.

Importing a Microsoft Project XML File into QuickPlanX​

Because QuickPlanX reads .xml rather than binary .mpp files, the person sending the schedule needs to save it as XML from Microsoft Project first. Microsoft documents that export step in Saving and Opening Projects in XML Format.

Once you have the .xml file, import it as a new project in QuickPlanX on Mac, iPad, or iPhone. Detailed instructions are in Create a Project from a Microsoft Project XML File.

Working with Third-Party XML Files​

"XML" is a file container, not a universal scheduling standard. Other planning tools can export .xml files, but their internal tag structures often differ from Microsoft Project's schema.

QuickPlanX's parser expects the schema generated by Microsoft Project. If an XML export from another planning tool fails to import cleanly, open that file in Microsoft Project (or MS Project Online) first and re-save it as XML before bringing it into QuickPlanX.

Who This Integration Is For​

Most people use XML import and export at the boundary between two working styles. You might inherit a legacy schedule built in MS Project and want to move your ongoing planning onto a Mac or iPad without maintaining a Windows virtual machine. Or you might prefer building and adjusting timelines in QuickPlanX, then exporting an XML snapshot whenever a client or PMO requires an MS Project file for their own reporting.

For a broader look at how the two tools differ in everyday use, see our Microsoft Project alternative guide.

Keeping Your Imported Schedule in Sync Across Apple Devices​

After an XML file is imported, it becomes a normal QuickPlanX project stored in iCloud CloudKit sync. Any edits you make on your Mac show up on your iPad and iPhone automatically—no further XML exports or manual file transfers required unless you need to send an updated snapshot back to a Microsoft Project user.


Ready to try QuickPlanX?

Download on the App Store

Related articles: Connect Your Planning Workflow · Keep Every Device in Sync · Share Clear Project Reports