Make a copy of a project

All plansMember

When you run the same kind of project again, the quickest start is the last one. Make a copy builds a new project from an existing one with its full structure: tasks at every level, the links between them, epics, sprints and milestones. Every task starts again as To do, so the copy is a fresh plan, not a clone of the old project’s progress.

Make a copy

Open the project’s menu. You can do this in three places: the ⋯ button in the project header, the menu on the project’s card on the Projects page, or the menu on its row in the Health view.
Choose Create new, then Make a copy. (When Make a copy is the only thing you can create there, the menu shows it directly.)
In the dialog, check the name. It starts as Copy of followed by the project’s name; change it to what the new project is called.
Optionally set a New start date. Every task, milestone and sprint moves by the same number of days, so the schedule keeps its shape. Leave it empty to keep the original dates.
Leave Bring the people ticked to bring the members, the assignees and the collaborators, or untick it to start with only yourself.
Select Make a copy. Onplana creates the project and opens it.

You own the copy either way. When you bring the people, the original project’s owner joins the copy as a manager.

What is copied

Tasks at every level, with their order, priority, estimates, durations, constraints and recurrence.
Dependencies between the copied tasks.
Epics, sprints and milestones.
Tags, and the values of organization-wide custom fields.
The project’s settings and description.
With Bring the people: members, assignees and collaborators.

Every task goes back to To do with no progress, no actual dates and no completion. Milestones and sprints are set back to not done, and the new project starts in Planning.

What is not copied

The dialog lists these too, so nobody is surprised:

Comments, files and documents.
Risks and issues.
Baselines. The copy has not been baselined yet; capture one when the plan is ready (see Capture and compare baselines).
Time entries and expenses.
Sharing, including portfolio membership and links to tasks in other projects.
Values of custom fields that belong only to the original project.
Lists, folders and pages in the project’s workspace, and closeout and completion records.
Anything synced from elsewhere, such as a Planner link, calendar events or the project’s inbound email address.

Copy or template?

Both start a new project from an old one. They suit different jobs.

	Make a copy	Save as Template
Plan	Every plan	Pro and above
Task levels	All of them	Two (tasks and subtasks)
Dependencies, epics, sprints, milestones	Kept	Not kept
People	Optional	Not kept
Reuse	One new project each time	Listed in the Templates window for anyone you share it with

Use Make a copy to run the same project again with its whole schedule, for example next year’s audit or a second site rollout. Use Save as Template for a lighter pattern that many people will start projects from.

Who can make a copy

Anyone who can create projects in the organization and can see the original project. By default that is every member except Guests. The copy counts as a new project, so your plan’s project limit applies: if the organization has no room for another project, the copy is refused with the limit named, as it would be for any new project.

FAQs

Does the copy change the original project? No. The original is only read. Nothing in it moves, and nobody on it is notified.

What if someone on the original has left the organization? They are left out of the copy. Their tasks are still copied, unassigned.

Can an agent make a copy? Yes. The in-app AI assistant and agents connected over MCP use the duplicate_project tool, which makes the same copy with the same rules. The person behind the agent owns the copy, and the agent’s undo deletes it again.

Save and reuse project templates
Do more from any item, the menu this lives in
Organize the Projects page
Restore from the Recycle Bin

Was this helpful?