What MppToExcel does not do, and when you don’t need it

What MppToExcel does not do, and when you don't need it: the workbook goes one way only, it is a snapshot to export again, it does not feed Power BI, and sometimes Project or a PDF is enough

In the first two articles of this series we took the plan into Excel with the Gantt chart and made four different workbooks for four readers. This one goes the other way: what MppToExcel does not do, and when you don’t need it at all.

You choose a tool better when you know where it stops. And anyone looking for a Microsoft Project Excel export alternative does well to know first where this one ends.

In short

  • MppToExcel takes the plan into Excel one way only: whatever is written in the workbook never goes back into the plan.
  • The workbook is a snapshot of the .mpp file as it was saved: every time the plan is updated, you export again, with the same columns.
  • To feed Power BI every month, or for an export that runs on its own, you need a different tool. For a small plan delivered once, Project itself is sometimes enough.

It goes one way only

The workbook is a delivery, not a second copy of the plan. If the site manager types the week’s progress into it, those percentages stay in the workbook: the plan never sees them.

This is not an oversight. A workbook that anyone can edit and that rewrites the plan by itself is the quickest way to lose track of which version is the real one. To bring the team’s hours and progress back into the plan there is GanttTimesheet: it sends each person their own tasks in Excel, collects the completed timesheets and writes into the plan only the rows the planner has approved.

Diagram: from the .mpp plan, MppToExcel takes the Excel workbook with the Gantt chart to readers without Project; changes made in the workbook never reach the plan; the team's hours go back into the plan with GanttTimesheet, approved rows only; for Power BI, OneClickExporter writes fixed CSV files, also from a scheduled task
Three roads around the plan, each with its own tool: MppToExcel only goes outward.

It is not a live link

The workbook captures the plan at the moment you export. If the plan changes tomorrow, today’s workbook doesn’t know: you export again. The columns you chose are remembered from one launch to the next, so this week’s workbook has the same shape as last week’s. The filters, on the other hand, always start empty, so that the cut made for one reader doesn’t end up with another by mistake.

There is one more detail worth knowing. MppToExcel reads the .mpp file without opening Project, so it reads it as it was saved. Critical path, slack and outline numbering are values Project recalculates when it opens the plan: if the file was saved without an up-to-date calculation, the workbook shows the values from back then.

On the critical path the program does an extra check. Tasks whose criticality it cannot confirm are not coloured as if someone had checked them: it counts them in the line at the top of the sheet, where the reader can see them. The practical advice is simple: before exporting, open the plan in Project, let it recalculate and save it.

It is not a data feed for Power BI

The MppToExcel workbook is made to be read by a person: the Gantt chart drawn in the cells, the colours, the plain-language headers, the status line at the top. A Power BI model needs the opposite: fixed columns, with the same name and the same data type month after month, and an export that runs at night with nobody at the keyboard.

MppToExcel is a desktop application with no command line. For that job there is OneClickExporter: from the same .mpp file, or from a whole folder of plans, it writes a fixed set of CSV files, and it can also run from a scheduled task.

When you don’t need it at all

  • The person receiving the plan has Project. Send them the .mpp file: they read everything, with Project’s own calculations. At most, clean out first what they shouldn’t see.
  • The plan is small and you deliver it once. Copying the table into Excel or saving from Project’s menu is enough: the Gantt chart doesn’t come along, but for twenty rows you often don’t need it. The possible routes, with their pros and cons, are in five ways to send the plan to someone without Microsoft Project.
  • All you need is a document to attach to the minutes. A PDF printed from Project is perfectly fine. The workbook is worth it when the reader has to filter, sort or annotate.

You need MppToExcel when the same plan reaches several people who don’t have Project, again and again, and every time it has to have the same shape.

Base or Pro, and how to try it

The licence is annual, per workstation, in two editions. Base gives you the Gantt workbook with no limit on the number of tasks. Pro adds cost data, four extra sheets, column selection and filters. It is the same program: the key decides the edition. The 15-day free trial is the full Pro edition, with no key needed, and if you buy it and it turns out not to be what you needed, you have 14 days to ask for a refund.

Frequently asked questions

If the client edits the workbook, what happens to the plan?

Nothing. The changes stay in their workbook and the plan never receives them. At the next delivery you export again from the plan, and the new workbook starts from the real data.

Can the export run on its own, every week?

Not with MppToExcel: it is a desktop application, and a person starts the export. For a scheduled export with nobody at the keyboard there is OneClickExporter, with its command line.

Is the critical path in the workbook always the right one?

It is the one saved in the file. If the plan was saved after recalculating, it matches Project’s; if not, it may be out of date. Tasks whose criticality the program cannot confirm are counted in the line at the top of the sheet. Before exporting, it pays to open the plan in Project and save it.

How much does it cost to keep it for a year?

The licence is annual, per workstation, Base or Pro: prices are on the product page. Before deciding you get a 15-day trial of the full Pro edition, and after buying, 14 days for a refund.


This is the third and last article in the series on MppToExcel. The first takes the plan into Excel with the Gantt chart, the second makes four workbooks for four readers.

#MSProject #Excel #GanttChart #ProjectReporting

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top