Archive Finished Projects in Asana
Archive a finished project to reduce active-work clutter while retaining its tasks and context. Write a final summary first so archived work remains understandable later.
Step-by-step guide
Check access and scope
Only project admins can archive the project. Archiving does not change its project status. Confirm unfinished tasks and external dependencies have an active owner.
Review incomplete work
Review incomplete tasks and decide which need follow-up.
Write the final update
Publish a final status with shipped scope and unresolved exceptions.
- Worked example: Archive a completed onboarding launch after moving ongoing bug fixes to the maintenance project. Retain the final rollout decision and link the follow-up project from the summary.
Move continuing obligations
Move continuing work to its appropriate active project.
Archive the project
Use the project menu archive action. Open the project title dropdown and choose Archive; only project admins can archive, and archiving does not mark project status complete.
Retrieve retained context
Find the archived project and confirm key resources remain available.
Verify the result
The project leaves active planning views while authorized readers can still retrieve its final decisions.
Common mistakes
Avoid the main failure mode
Archiving is not a data-retention policy or a backup export. Review confidentiality and retention requirements independently.
Check the handoff edge case
Leaving unresolved ownership in an archived project hides follow-up work from active planning. Move or reassign continuing obligations first.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.