Project Online

Import Project Online plans into a new tool

Your Project Online exports still work after the retirement. Open each .mpp file in Project desktop, save it as XML, and import the XML into the new tool. Then check dependencies, calendars and custom fields, because no import keeps everything.

Last checked: 9 October 2026.

Which files you have

FileWhat to do with it
.mppOpen it in Project desktop and save it as XML. Most tools outside Microsoft cannot read .mpp directly, Teamhood included.
XML (MS Project XML)Import it as it is. This format carries the task outline, dates and dependency links.
Excel or CSVImport it as a list. Check the links: exports from the reporting feeds can miss task dependencies.

You need Project desktop for one step

Project desktop does not retire with Project Online and still opens .mpp files. Check your version:

No Project desktop at all? Use your Excel or CSV exports instead, and relink the dependencies after import.

Import a plan into Teamhood

  1. Save as XML. Open the plan in Project desktop. Choose File, Save As, and set the type to XML Format (*.xml).
  2. Start the import. In Teamhood, select + at the top of the sidebar, then Import. Drop the XML file. It can be up to 10 MB.
  3. Place the tasks. Pick the item type the tasks become. By default, the tasks go under one item named after the plan.
  4. Map and review. Map columns such as duration, work, % complete, priority, milestone, WBS and deadline to fields. Check the people the import could not match, then import.

Full steps: Import a plan from MS Project.

What the import keeps, and what it leaves out

KeepsLeaves out
Every task, nested as in the plan’s outlineConstraints, such as Start No Earlier Than
Start and finish datesCalendars, working time and holidays
Predecessor links of all four types, with lag rounded to whole working daysBaselines, costs and custom fields
Task notes, as the item’s descriptionMaterial and cost resources
Assigned resources, matched to people and teams by nameResources whose names match nobody (listed for you to fix)

After the import: a short checklist

  1. Dependencies. Open the Gantt and check the links on the critical path.
  2. Dates. Calendars do not come across, so set people’s working weeks and time off, then check the dates that matter.
  3. Baseline. Save a new baseline once the plan looks right, so you can track changes from here.
  4. People. Fix the unmatched names from the import review.
  5. Fields. Recreate the custom fields you still need.

If you are moving to Planner instead

A Microsoft Q&A moderator answered in April 2026 that there is no native, automatic path from Project Web App to Planner premium. Importing .mpp files into Planner is not part of its main interface, and resources and baselines do not come across. Plan for the same checks either way.

Test one plan first

Import one real plan and check it against the list above before you move the rest.

First month free, no credit card.

Questions

Can Teamhood open an .mpp file?
No. Teamhood imports the XML file that MS Project saves. Open the .mpp in Project desktop, choose File, Save As, XML Format, and import that file.
Do dependencies survive the import?
Yes, from XML. All four link types come across, and lag is rounded to whole working days. Excel and CSV exports from the reporting feeds can miss links, so check them.
Do baselines and custom fields come across?
No. Baselines, costs, custom fields, constraints and calendars stay behind. Save a new baseline after the import and recreate the fields you still use.
What happens if we import the same plan twice?
Its tasks are added again. The review step shows matching items under Already there, so you can choose to reuse an existing parent item.
We have no Project desktop. What now?
Import your Excel or CSV exports and relink the dependencies. Planner and Project Plan 3 also includes Project desktop if you need it for the conversion.

Sources

SourceUsed for
Teamhood help: Import a plan from MS ProjectSteps, what the import keeps and leaves out
Microsoft Learn: Prepare for Project Online retirementProject desktop after the retirement
Microsoft Lifecycle: Project 2021, Project 2024Desktop support dates
Microsoft Q&A 5846989Moving PWA plans to Planner premium (moderator answer)

Change log: 9 October 2026, page published.

Teamhood uses cookies, to personalize content, ads and analyze traffic. By continuing to browse or pressing "Accept" you agree to our Cookie Policy.