Others

Split a Microsoft Project Master File into Linked Projects

John WilsonJohn Wilson Nov 18, 2026 869 views

Question details

Separate summary tasks and their child tasks from a Microsoft Project master file while managing links and updates.

Split a Microsoft Project Master File into Linked Projects
Product
Microsoft Project
Device & OS
not provided
Scenario
A project manager wants to create separate subprojects or a static master from an existing master project.
Observed behavior
The desired result is a set of separate project files with understood update behavior and reduced risk from broken links.
Before you start

Identify which summary tasks and child tasks belong in each subproject, and check whether the master already contains linked subprojects. Note the locations of linked files and avoid moving, renaming, or overwriting them while the master uses those links.

Solution 1Recommended

Create a Separate Project and Link It to the Master

Use this approach when a group of tasks needs its own project file and its updates should appear in the master.

Copying tasks into a new project does not automatically remove them from the original master. Review dependencies, resource assignments, calendars, and custom fields after copying, especially when tasks depend on work outside the selected group.

1
Select the task group

Open the master in Microsoft Project, expand the relevant summary task, and select its row and all child task rows. Use Copy to copy the selection.

2
Create a project file

Choose File > New to create a blank project, then paste the selected rows into the task table. Check the task hierarchy and schedule settings.

3
Save the subproject

Choose File > Save As and save the new project as an .mpp file in its intended location.

4
Insert the linked project

In the master, select the insertion row and choose Project > Subproject. Select the saved file, ensure Link to project is enabled, and insert it.

5
Check the result

Expand the inserted subproject in the master and compare its tasks, dependencies, and assignments with the source. Resolve any duplicate tasks only after confirming which file owns them; edits to linked tasks can affect the linked file.

Create a Separate Project and Link It to the Master
Keep linked files in place: Moving, renaming, or overwriting linked files can break links or contribute to instability. Saving a copy of the master alone does not create independent copies of its linked subprojects.
Free Microsoft Office alternative

Use WPS Office for Project Reports and Supporting Documents

WPS Office is a free, lightweight alternative for working with project reports and spreadsheets in a familiar interface. Its Microsoft Office format compatibility helps teams move supporting documents between applications. It does not manage Microsoft Project master or subproject links.

Prepare project status reports and supporting spreadsheetsOpen and edit common Microsoft Office formats, including DOCX and XLSXUse familiar document and spreadsheet tools for an easier transitionWork with a free, lightweight office suite
microsoft office alternative - wps office

Frequently Asked Questions

Will changes in a linked subproject appear in the master?

A dynamically linked subproject can show changes from its source file in the master. Keep the file in its expected location and reopen or refresh the master as needed.

How do I stop a subproject from updating the master?

In the master, double-click the subproject summary task, open the Advanced tab, and clear Link to project. The inserted tasks become a static snapshot rather than an automatically updated link.

Does saving a master under a new name copy its subprojects?

No. File > Save As creates a copy of the master file, but its links can still point to the original subproject files. Check those links before editing tasks.

Can I automate rebuilding a static master?

You can record a macro in Microsoft Project to create a master, set its schedule, insert subprojects, and clear their links. Test it with your files and keep subprojects in the locations expected by the macro.