Microsoft Planner can export a plan to Excel — but only one plan at a time. You open a plan, pick “Export as Excel” from the ... menu, and get a spreadsheet of that plan’s tasks. What Planner has never shipped is a single file across every plan you can access. If you manage work in more than a handful of plans, that gap turns “export to Excel” into a weekly chore of exporting each plan and stitching the files together by hand. This page is the honest map: what native export gives you, the three real routes to get all your plans into one workbook and their gotchas, and the one-click way to skip the whole thing.

Can Microsoft Planner export a plan to Excel?

Yes — one plan. Open a plan, click the ... menu on the plan header, and choose Export as Excel; the spreadsheet drops into your Downloads folder with that plan’s tasks as sortable, filterable rows, per Microsoft Support. For a single project run by a single team, that’s genuinely all you need — a clean copy of the tasks for reporting or sharing outside Planner.

The catch is the word a. The export is scoped to the one plan you happen to be standing in. There’s no “export everything” option on the Planner hub, no multi-select, no “all my plans” checkbox. Each plan is its own separate download.

Can I export all my plans to one Excel file?

Not natively. This is the gap people actually hit, and they’ve been hitting it for a decade. The most-referenced request on the topic — “How to export Planner status reports in Excel” on the Microsoft Community Hub — was opened back in 2016 asking for plan and task status reports in Excel, and it’s still collecting replies in 2026 (40 and counting). The answers are all workarounds; none of them is “click here.”

The sharpest version of the pain shows up in a thread literally titled “Download all tasks in all plans”: a user explains that every week they go into each plan — “over 70 of them” — and download each one to Excel individually, then consolidate. That’s the native path taken to its logical, miserable conclusion. When someone is exporting 70 spreadsheets by hand every week, the feature isn’t “export to Excel,” it’s “no cross-plan export exists.”

(Sources accessed 2026-08-14.)

The three routes to get every plan into one file

There are exactly three honest ways to produce an all-plans workbook natively, and each has a real cost worth naming before you commit to it.

1. Repeat the native export and merge by hand. Export each plan with Export as Excel, then copy the sheets together (or Power Query them) into one workbook. It uses only built-in Planner and Excel, so there’s nothing to build or maintain. But it scales linearly with your plan count and it’s fully manual — every week is a fresh round of exports. This is exactly the 70-downloads-a-week grind above. Fine for two or three plans; unbearable past a handful.

2. Script it against the Microsoft Graph API. Call GET /planner/plans/{plan-id}/tasks for each plan (Microsoft Graph v1.0, docs), page through the results, resolve bucket / assignee / label IDs to human-readable names, and write the combined rows to a workbook. This is the right answer technically and it can be scheduled. The cost: you own an app registration and its permissions, the paging, the ID-to-name lookups, and the ongoing maintenance. It’s a small software project, not a setting.

3. Build a Power Automate flow. A scheduled cloud flow can iterate your groups and plans with nested “Apply to each” actions, list each plan’s tasks, and assemble the output — which is the shape Microsoft’s own community answers point people at on the all-plans thread. It works, but you wire and maintain the flow, every new plan is a change to it, and the Planner connector famously drops some fields (labels, descriptions) unless you work around them.

RouteWhat you getThe gotcha
Repeat native export + mergeOne workbook, zero setupFully manual, per-plan, every time — the 70-exports grind
Graph API scriptAutomated, all fields, schedulableYou build and maintain a real app (registration, paging, ID lookups)
Power Automate flowAutomated, no codeYou wire it per plan, maintain the flow, and fight connector gaps

All three end in the same place — a single spreadsheet of tasks across your plans. The only question is how much of your time it costs to get and keep there.

The one-click route: cross-plan export in Team Workload

That’s the exact gap we closed in Team Workload. You sign in with your Microsoft account, it reads every plan you can access, and the Export menu writes all of those tasks to a single .xlsx — across plans, in one click. No per-plan repetition, no Graph app registration, no flow to babysit.

The workbook comes out already shaped for reporting: one row per task with columns for Title, Plan, Bucket, Assignees, Status, % Complete, Priority, Labels, Start, and Due (plus Created and Completed dates when your tasks carry them), and the IDs already resolved to names — the exact lookups the Graph route makes you write yourself. Because Team Workload is a cross-plan reporting view first, the export inherits whatever scope and filters you’ve set, so you can pull “every plan” or narrow to the plans and people you care about and export just that.

If your weekly ritual is exporting plan after plan and pasting the sheets together, this is the button Planner never gave you: one export, every plan, one file.

Exporting to Excel is the “get the data out” job. Once it’s out, the questions you’re usually chasing have their own dedicated cross-plan views:

The export is how you get all your plans into a spreadsheet in one file. These are how you answer the questions without leaving Planner for Excel at all.