Dynamics 365 Project Operations: Import MPP Files Into Existing Projects Without a WBS

Tracked under AI at Work roadmap ID 576805 (and earlier communicated to tenant administrators via Microsoft 365 Message Center notice MC1296862 ), Microsoft has rolled out a fix for this exact friction point: the ability to import projects in .mpp files directly into existing projects in Dynamics 365 Project Operations.

While this update removes a major administrative hurdle, there are strict rules under the hood regarding what qualifies as an "eligible" existing project, what happens if you accidentally click the wrong tab before importing, and how project attributes behave during the handoff.

Release Timeline and Deployment Scope​

If you manage a Dynamics 365 environment, here is where the feature stands across Microsoft's release channels:

• Product: Dynamics 365 Project Operations (applicable to Project Operations Integrated with ERP and Project Operations Core per Microsoft Learn documentation)
• Platform & Cloud Instance: Web platform; Worldwide (Standard Multi-Tenant)
• Release Status: Launched (General Availability)
• Timeline: Entered Public Preview in August 2025 (specifically August 1, 2025, per Microsoft Learn release plan records) and reached General Availability in August 2026 (listed as August 4, 2026, in the 2026 release wave plan, following an earlier May 31, 2026 target noted in Message Center archive MC1296862 ).
• Enablement: Enabled by admins, makers, or marketers/analysts for end users.

(A quick note for admins digging through the roadmap metadata: the official roadmap entry's "More info" link erroneously points to a Dynamics 365 expense mobile app article. The actual operational rules live in Microsoft Learn's "Import projects from the Microsoft Project desktop client" documentation.)

What Changed in the .mpp Import Workflow​

The core problem Microsoft set out to solve is hybrid planning. In many organizations, high-level project origination—setting up the customer, contracting unit, and financial shell—happens inside Dynamics 365 Project Operations, while individual project managers still draft detailed task schedules offline in the Microsoft Project desktop client.

With this update, Microsoft states that users can:

1. Choose the destination: Import a .mpp file into either a brand-new project or an eligible existing project.
2. Manage key project attributes: Update key project attributes—Microsoft's roadmap and release plan specifically cite Contracting Unit and Owning Company—directly within the import experience, while confirming the import follows configured settings.
3. Speed up setup on empty projects: Populate pre-created, empty project records without starting from scratch or generating duplicate project records that have to be reconciled or deleted later.

The "Gotcha" Every Admin Should Know: What Counts as an "Empty" Project?​

Before your project managers try to merge an offline .mpp schedule into an active project that already has tasks in it, hit the brakes. In Dynamics 365 Project Operations, importing into an "existing project" means importing into an existing project with no work breakdown structure (WBS). It is a project shell population tool, not a schedule-merging or bi-directional sync tool.

According to Microsoft Learn's operational documentation for .mpp imports, there is a very specific—and easy to trip over—technical condition for eligibility:

• Do not open the Task tab first: A project without a WBS is one that has been created in Dynamics 365, but where nobody has clicked on the Task tab yet. The moment a user opens the Task tab on a project record, Project Operations automatically generates a blank WBS in the background.
• Even a blank WBS blocks the import: Microsoft's documentation explicitly warns that if a project already contains a WBS—even if that WBS is completely blank—you cannot import tasks into it from a .mpp file.
• Filtered picker: When you launch the importer, only eligible projects (those without an initialized WBS) will appear in the destination dropdown list.

In practice, if an operations coordinator creates a project shell and clicks over to the Task tab just to "check that it's empty," they will inadvertently initialize the WBS and disqualify that project record from receiving a .mpp import.

Step-by-Step: Importing a .mpp File in Project Operations​

Microsoft Learn outlines two distinct paths in the Projects view depending on whether you are spinning up a new record or populating an existing shell.

Option A: Importing into an Eligible Existing Project (No WBS)​

1. Open the Projects view in Dynamics 365 Project Operations.
2. On the top toolbar, select Import > Import from MPP.
3. Select the target existing project from the picker (remember, only eligible projects without a generated WBS will be listed).
4. Choose Choose File, browse to your local .mpp file, and select Open.
5. Select Import to begin the migration.
6. Once completed, review the validation summary dialog to see if any unsupported items or resources were stripped during the import.
7. Click Go to project to inspect your newly populated schedule.

Option B: Importing to Create a New Project​

1. Open the Projects view and select Import > Import from MPP.
2. Update the required header fields in the dialog: Work hour template, Project manager, Schedule mode, and Contracting Unit.
3. Select Choose File, pick your .mpp file, and select Open.
4. Select Import, review the post-import validation summary, and click Go to project.

New vs. Existing Destination Comparison​

Note on attribute editing: There is a slight nuance between Microsoft's high-level roadmap description and its technical documentation. While the roadmap notes the ability to update key attributes like Contracting Unit and Owning Company within the import experience, Microsoft Learn's procedural guide states that when selecting an already-created existing project, the project fields in the dialog are locked because the record already exists. If your workflow requires changing those organizational attributes during an existing-project import, test the dialog behavior in your specific wave build to see which fields your environment exposes before locking the record.

Operational Limitations to Keep in Mind​

Even when an import succeeds, Project for the web / Project Operations does not support every legacy or advanced scheduling feature available in the Microsoft Project desktop client. Microsoft highlights three major guardrails administrators and PMs need to watch:

1. Unsupported Desktop Capabilities: Not every desktop feature migrates to the cloud engine. Always check the validation summary immediately after importing. (For example, Microsoft's documentation illustrates a validation summary where nine resources were automatically removed during import.) If tasks, links, or data points appear missing, they likely relied on a desktop-only capability.
2. Work Breakdown Structure (WBS) Limits: The incoming .mpp schedule must conform to Dynamics 365 Project Operations' existing WBS limits.
3. Custom Required Fields on the Project Main Page: Because customizing the Import from MPP dialog box is not currently supported, adding custom required fields to your Project main form can break new-project imports unless you configure default values for those required fields.

Summary for Dynamics 365 Admins​

The ability to import .mpp files into existing Dynamics 365 Project Operations records closes a glaring gap for teams that split project origination and detailed schedule creation. To get the most out of it, train your project coordinators on the golden rule of Project Operations shells: create the project record, leave the Task tab untouched until the .mpp file is imported, and always audit the validation summary before handing the schedule over to the delivery team.