logo
search
Others

How to Separate Two Projects into Standalone Microsoft Project Files

Nimra MalikNimra Malik Sep 29, 2026 868 views

Question details

The user needs to separate two projects currently stored in a single Microsoft Project schedule into two independent project files.

How to Separate Two Projects into Standalone Microsoft Project Files
Product
Microsoft Project
Device & OS
not provided
Scenario
Managing multiple projects in a single schedule and needing to split them into separate, standalone files while maintaining data integrity.
Observed behavior
The projects are merged within one file, requiring a split that properly handles tasks, progress, shared resources, and cross-project dependencies.
Before you start

Before separating your projects, review your schedule for any cross-project task links or shared resource pools to determine the most appropriate separation method.

Solution 1Recommended

Split Unlinked Projects by Saving Copies

Use this straightforward method if the two projects do not share resources and have no cross-project task dependencies.

This is the simplest way to separate two schedules. By duplicating the file, you ensure all initial data is preserved before you begin removing the unnecessary project from each copy.

1
Save copies of the schedule

Open the merged Microsoft Project file and use the 'Save As' function to create two separate copies with distinct file names.

2
Remove the first project

Open the first copied file, select the summary task for the project you want to remove, and delete it entirely along with its subtasks.

3
Remove the second project

Open the second copied file, locate the summary task for the other project, and delete it to isolate the remaining schedule.

4
Review resource assignments

Navigate to the Resource Sheet and check for any duplicated or unassigned resources left behind, deleting them if they belong exclusively to the removed project.

Split Unlinked Projects by Saving Copies
Resource Duplication: If you simply delete tasks without managing shared resources, your resources may be duplicated across the two new files, potentially causing tracking issues.
Free Microsoft Office alternative

Try WPS Office for Your Daily Project Tracking Needs

While Microsoft Project is designed for complex scheduling, WPS Office provides an excellent, free, and lightweight alternative for all your general documentation and spreadsheet-based project tracking needs. It features a familiar interface and allows for seamless migration.

  1. 1. Download and Install: Download WPS Office for free from the official website and complete the lightweight installation.
  2. 2. Open a Spreadsheet for Project Tracking: Launch WPS Office and open WPS Spreadsheet to create customized Gantt charts, task lists, and project timelines.
  3. 3. Save in Compatible Formats: Save your project trackers in fully compatible .xlsx formats, ensuring seamless sharing with colleagues using Microsoft Office.
Free and lightweight office suite for daily productivityHighly compatible with Microsoft Excel, Word, and PowerPoint formatsCreate and manage project timelines easily using WPS SpreadsheetBuilt-in PDF editing tools for comprehensive project documentationFamiliar user interface ensuring a seamless transition
microsoft office alternative - wps office

Frequently Asked Questions

What happens to shared resources if I just copy the file and delete tasks?

If you simply copy the file and delete the other project's tasks, the shared resources will remain duplicated in both independent files. This can cause resource overallocation and tracking issues unless you set up a central resource pool.

Can I keep task dependencies active between the two separated project files?

Yes, cross-project dependencies can be maintained. When you separate the files, you must establish external links by entering the standalone file's name and the specific task ID into the predecessor column of the dependent task.

How do I remove a project's summary task without deleting all of its subtasks?

To remove a summary task while keeping its subtasks in Microsoft Project, you must first outline (outdent) all the subtasks to the same hierarchical level as the summary task itself, after which you can safely delete the summary task.