Importing from Other Formats

OmniPlan understands several other applications’ file formats. You can open files of these types in OmniPlan the same way you would open an OmniPlan document. The file is imported into a brand new OmniPlan document, which you can then edit, save, or export.

When it’s time to import a file other than an OmniPlan .oplx file (or with Pro, an .opld Dashboard file), choose File > Open (Command-O), and be sure that Allow import of other recognized file types is checked in the Open dialog.

The following file formats are recognized and can be imported by OmniPlan 4:

• Comma-Separated Values (.csv) and Tab-delimited text files (.tsv)—OmniPlan can read comma-separated or tab-delimited values from a plain-text file. To see how the data in a CSV file should be formatted, export an OmniPlan document as a CSV file and open the result in any text editor. Tab-delimited files are formatted like CSV files, except that tab characters are used instead of commas to separate fields.

• OmniOutliner (.oo3 and .ooutline)—Task lists can be imported from OmniOutliner files. A column mapping dialog appears, where you can choose which outline column should correspond to which field of task information. If the outline has multiple levels of hierarchy, task groups are created.

Exporting to Other Formats

OmniPlan can write files in several formats for use with other applications. To export an OmniPlan file, choose File > Export (Option-Command-E). When you export, a new file is created, leaving your original document as it is on the screen. Note that not all aspects of an OmniPlan document can be represented in all file formats; see details for each format below.

If you export a project while a filter is on, you can choose whether to export the entire project or only the contents that are visible.

• OmniPlan Document (.oplx)—OmniPlan can export to its own format. This is useful when you want to use the filtering feature to make a new OmniPlan file of tasks matching certain criteria: filter the tasks and make sure that Only Filtered Contents is checked when you go to export the project.

• iCalendar (.ics)—This is the calendar format used by Apple iCal, Apple Calendar, and many other calendar applications. You can choose to export the tasks as calendar events or as items on a to-do list. If you export calendar events, you can also choose whether each task should become to a single event, regardless of how long it may be (One event per task), or whether tasks should be broken into chunks when they span working and non-working hours (One event per work period).

• Comma Separated Values (.csv)—CSV is a common plain-text format that can be read by many different applications.

• Image Export (.png, .pdf, .tiff, .jpg)—You can export a picture of the Gantt View, Resource View or Network Diagram, selected from the Image Content menu in the Export panel. Depending on the view you choose, you can have the image include the outline, the Gantt chart or resource timeline, or both.

• OmniOutliner 5 (.ooutline)—The task outline is exported as an OmniOutliner file (supported by OmniOutliner 5), with row hierarchy that corresponds to OmniPlan’s task groupings and columns corresponding to those available in OmniPlan’s Gantt View.

• Graphviz (.gv)—An OmniGraffle-compatible file format used for network diagramming. There are three types of Graphviz export available, representing an array of diagram types and styles.

  • Work Breakdown Structure—Tasks and groups are represented by a tree of objects. The connection lines in this diagram type represent the hierarchy of the task outline; dependency lines are not represented.

  • Activity-on-Node Network Diagram—Tasks are represented by objects, connected by dependency lines. While a Gantt chart emphasizes durations, this type of chart emphasizes the path of dependencies.

  • Activity-on-Arrow Network Diagram—Tasks are represented as lines between objects, with the title and duration of the task as a label on each line. Like the Activity-on-Node network diagram, this diagram type emphasizes dependencies.

Microsoft Project Support (Pro)

If you are ever called upon to use OmniPlan in tandem with Microsoft Project, there is good news—OmniPlan Pro supports both export to and import from the vast majority of MS Project file formats.

Importing from Microsoft Project

Documents in the Microsoft Project .xml or .mpp formats created with Microsoft Project versions 2003 through 2019 can be opened by OmniPlan Pro. To import such a file, choose File > Open (Command-O) or double-click the file in Finder. The file is imported as a new OmniPlan .oplx file, ready to be edited or saved for future work.

An imported Microsoft Project file appears in OmniPlan with a blue-accented notice bar at the top. If errors show up in the document, you can use Report Problems in the notice bar to let us know about them, or click Done to dismiss the bar.

Exporting to Microsoft Project

Along with importing from the most-used MS Project formats, OmniPlan Pro can export to them as well. The following Microsoft Project formats are supported:

Microsoft Project Plan (.mpp)—This is the preferred format for most interactions with modern versions of Microsoft Project.

Extensible Markup Language (.xml)— As an open standard, .xml is useful with both Microsoft Project as well as interactions with other applications.

Quirks in Microsoft Project Import and Export

OmniPlan is pretty good at working with Microsoft Project documents up to and including the Microsoft Project 2019 .mpp format, and we’re always working to make it even better. There are a few things to note as you work with Microsoft Project documents in OmniPlan.

• Scheduling—Support for importing and exporting new scheduling features introduced in OmniPlan 4 has not yet been implemented in OmniPlan’s Microsoft Project Import/Export tool.

• Assignments to Task Groups—In Microsoft Project, a resource can be assigned to a group of tasks. In OmniPlan, this assigns the resource to all tasks in the group, not to the group itself. When you import a Microsoft Project document with an assignment to a task group, a warning appears in the violations column to let you know that the assignment was not imported.

• Custom Columns—Many of the optional columns in the Task and Resource View outlines don’t have direct analogs in Microsoft Project, and vice versa. These columns won’t be displayed when importing from or exporting to the affected app, and data in them will be left behind as well.

• Efficiency—Microsoft Project doesn’t support the OmniPlan efficiency attribute for resources.

• Styling (Document, Tasks, and Resources)—Styles you apply to items in OmniPlan, as well as those for the project as a whole, aren’t carried along when you export to Microsoft Project formats.

• Unequal Assignments—In Microsoft Project, if you assign more than one resource to a task you can specify how many hours of effort each assigned resource should contribute. If you don’t specify, it assigns however much work to each that will complete the task earliest (taking schedule and resource assigned units into account). OmniPlan always uses that same automatic method. So, a task with effort hours specified for its resources may take a different amount of time in OmniPlan than it did in Microsoft Project.

• Overloaded Resources—When importing a Microsoft Project file, OmniPlan will not overload resources as it schedules tasks. If a resource is overloaded in the original Project file, the auto-scheduled dates will change to avoid overloading resources (allowing for a maximum of 100% utilization of any resource). Therefore, the initial scheduling of tasks with previously overloaded resources will differ from the dates in the Project file.

• Tasks with ALAP Scheduling and Other Constraints—ALAP is a mutually exclusive status with other constraints on a task in Microsoft Project. When exporting an OmniPlan project as an .mpp file, tasks that are marked to start as late as possible (ALAP) and have have another constraint applied will lose ALAP scheduling (and be reverted to the default ASAP) when exported to .mpp. The other constraint will be preserved.

• Inactive Task Status—OmniPlan lacks an equivalent of Microsoft Project’s “inactive” task status. Any tasks marked Inactive in an .mpp file will have that status removed and be treated as regular active tasks when imported to OmniPlan (potentially affecting task scheduling and resource allocation).