Confluence Archive and Restore
Every wiki collects clutter over time: finished projects, outdated guides, duplicate drafts. Old pages mislead readers and bury useful content. Confluence offers two cleanup tools, archive and delete, and both can be reversed when the situation calls for it.
Archive vs Delete
| Feature | Archive | Delete |
|---|---|---|
| Purpose | Keep for reference, hide from daily view | Remove from the site |
| Appears in search | Hidden by default | No |
| Recovery | Restore at any time | Restore from trash |
| Best for | Completed projects and old policies | Duplicates and mistakes |
Plan details matter here. Archiving options and limits depend on your Confluence plan and edition, so confirm availability with your administrator.
The Page Lifecycle
CREATE --> ACTIVE --> OUTDATED --> ARCHIVED --> RESTORED
| ^
| |
+--> DELETED --> TRASH --+
|
+--> PURGED (gone for good)
A page can move along either path. Archive keeps the content safe and quiet. Delete sends the page to trash, where it waits until someone restores it or empties the trash.
Archiving a Page
- Open the page you want to retire.
- Click the three-dot menu at the top right.
- Choose archive.
- Confirm the action.
The page disappears from navigation and default search results. Links from other pages may lead to the archived page with a banner that marks it as archived.
Restoring an Archived Page
Space administrators open space settings and browse the archived pages list. Select the page and choose restore. The page returns to its position in the tree, or to a new location when the original parent no longer exists.
Deleting a Page
The delete option sits in the same three-dot menu. Confluence warns you when the page has child pages. Read the prompt carefully before you confirm. Child pages commonly move up one level in the tree, and the prompt explains the exact outcome.
Using the Trash
Each space has a trash area under space settings. Deleted pages stay there until someone restores them or an administrator purges them. Purging removes a page permanently, and no undo exists for that step. Retention rules vary by edition and site settings.
A Review Routine
Step One: Find Candidates
Search for pages not modified in the last year. A query on the last modified date builds the list quickly.
Step Two: Ask the Owner
Mention the page creator in a comment and ask whether the page still serves readers.
Step Three: Decide
- Update pages that readers still need.
- Archive pages with historical value.
- Delete pages with no value at all.
Benefits of Regular Cleanup
- Search results stay accurate and short.
- New joiners trust the content they find.
- Teams avoid decisions based on outdated instructions.
- Space structure stays easy to navigate.
Safety Habits
- Archive first and delete later when you feel unsure.
- Export a space before a large clean-up.
- Tell the team about bulk changes in advance.
- Limit delete rights to trusted space administrators.
A Clean-Up Example
A marketing team finishes a campaign. The space holds forty pages: briefs, drafts, final assets, and meeting notes. The space owner archives the drafts and old notes, keeps the final summary page active, and deletes two duplicate pages. New team members now see a short, accurate list instead of forty scattered pages.
BEFORE AFTER Campaign space (40) Campaign space (3 active) - drafts (15) - Final Summary - old notes (12) - Results Report - duplicates (2) - Asset Library - final pages (11) Archived: 35 pages
Key Takeaways
- Archive hides pages while keeping them recoverable.
- Delete moves pages to trash before permanent removal.
- Space administrators restore both archived and deleted pages.
- A regular review routine keeps a wiki healthy.
