Export Notion Comments and Check the Decision Context
Export Notion comments as HTML, then inspect the reply conditions, thread status and decision ownership behind the page text before relying on the download.
A page can state a deadline without showing, in its main wording, who proposed it or which condition made it acceptable. This guide proposes a discussion-context check using a hypothetical project; it does not report a performed export or guarantee complete fidelity for a particular workspace.
Begin with the question the discussion must answer
Imagine a project page that now says delivery is Friday. A comment beside the delivery paragraph asks whether Thursday is still possible. A reply says, “Friday works if the test report arrives by noon.” Another participant later closes the thread.
These are invented details, not a real project record. They illustrate why the sentence “Delivery is Friday” may be insufficient for a later handoff. The conditional reply matters, and the act of closing the thread does not establish who accepted responsibility for the condition.
Write the question you need the retained discussion to answer: “Was Friday unconditional, or did someone still need to deliver the report?” Keep that question separate from a general desire to archive every comment.
You may need the current outcome, the unresolved obligation or an explanation of an earlier choice. Decide which task matters before choosing the threads to inspect. Our app-switching guide covers broader migration planning; this workflow concerns the meaning of one page's discussion.
Locate page-level and block-level context before exporting
Notion distinguishes top-level page discussion from comments attached to specific page content. Its comments pane opens from the comment icon at the top; you can filter by person or open/resolved status and select a comment to locate its page context. Threads are arranged by recent reply, so pane position alone is not a chronological decision record. Comments documentation
For the hypothetical delivery decision, inspect both the overall discussion and the thread beside the deadline. Identify whether a reply addresses the delivery date, the report condition or a different question that happens to sit nearby.
Keep these observations distinct:
- The page currently states Friday.
- A participant's reply attaches a condition to Friday.
- Someone closed the thread.
- Ownership of the report is explicit, or remains unclear.
Those are proposed checks. Do not record them as findings until you inspect your actual page. In particular, avoid turning a comment's existence into proof that its condition was satisfied.
Use the documented HTML export route
On desktop, open the page's upper-right menu, choose Export, select HTML and export the download. Include subpages only if they are part of your intended scope. Notion describes a ZIP containing HTML pages and, where included, associated assets. Its HTML guidance explicitly covers page/block comments, resolved and unresolved threads, and mentioned files, pages and users. Export documentation
The HTML statement also does not establish that every other format preserves the same discussion. If you choose another output, verify the actual content you need rather than turning this guidance into either a universal compatibility claim or a claim that other formats can never contain comments.
If the problem is extracting or opening the downloaded archive on Windows, our Notion ZIP guide handles that separate access task. A file opening successfully does not yet establish that its discussion answers your project question.
Inspect the condition, the reply and the decision owner
Open the actual retained page and find the discussion you selected earlier. Check the needed comment text and its relationship to the relevant paragraph. Do not stop after recognizing the page title.
For the hypothetical Friday delivery, inspect the wording after “if.” If the condition is absent from the copy you are reviewing, a summary of “Friday agreed” would overstate the evidence. Keep the missing condition visible as an inspection gap.
Next ask who is responsible for the action and where that responsibility is expressed. A person mentioned in a thread may be the subject of a question rather than its owner. A reply may acknowledge reading the discussion without accepting the task.
If the assignment is not explicit, write “Report owner not established in the retained discussion.” That is a more useful handoff than assigning ownership based on proximity, a mention or who happened to reply last.
Inspect mentioned references that affect the decision as well. A linked report could contain the condition's details; a page title alone does not prove you retained the information inside it. Record what you could actually open and what still depends on access elsewhere.
Keep status separate from approval
Resolved status is useful discussion metadata, but it does not tell you why someone closed a thread. For your decision record, inspect the words establishing the outcome rather than treating a status label as authorization.
In the invented example, the thread might have been closed because the page was updated, because the question moved elsewhere, or because someone believed it was answered. Those are possible interpretations to investigate, not facts you should insert into the record.
Use a short evidence record to avoid blending the different layers:
| Layer | What to retain or record |
|---|---|
| Page outcome | Relevant current wording and page identity |
| Discussion | Needed comment and reply with their visible attribution |
| Condition | The requirement attached to the proposed outcome |
| Ownership | Explicit responsibility, or a clearly marked uncertainty |
| Status | Observed thread state without an invented explanation |
| Inspection | Date checked and missing references or context |
This is a proposed working-note structure, not a claim about an automatically generated export schema. Keep any manual summary clearly labeled as your interpretation of the retained material.
Write a handoff that does not overstate certainty
Compare two possible summaries of the hypothetical discussion. “Friday approved” erases the condition and assumes the meaning of closure. “Page states Friday; reply makes that conditional on a noon report; report ownership needs confirmation” preserves the actionable uncertainty.
Your real summary should follow your real evidence, not this example's wording. If the condition was later met and the discussion explicitly records that, include that result with its source. If you cannot find it, leave it unresolved rather than inferring completion from the final page text.
Retain the inspected download alongside your handoff note and identify which copy you reviewed. If you later export again, distinguish the newer copy so a reader can tell which discussion your summary describes.
This check concerns one page and its discussion. For an app migration, separately inspect the other content and workflows you need.
For choosing a wider personal reference workflow, our second-brain app guide covers broader organization. Keep this decision-context task grounded in the page and discussion you actually inspected.
Nemos is our own app, so weigh what we say about it with that in mind. Nemos keeps links, notes, screenshots and files in one library. Nemos lets you search saved links, notes and text in screenshots.
Those capabilities can support a separate working-reference collection. They do not establish Notion discussion import, permission coverage or restoration of collaboration history. Keep the retained source, manual summary and unchecked gaps distinct.
FAQ
Can Notion export comments along with page content?
Yes. The documented HTML route covers page and block discussion. Inspect the actual output for the comments and references needed for your task instead of assuming a successful download certifies completeness.
Does a resolved thread mean the decision was approved?
No. Establish the outcome from the discussion and the relevant responsibility, not the status label alone. If the reason for closure is unclear, preserve that uncertainty in your handoff.
Is keeping the final page text enough?
Not when your task depends on a condition, responsibility or explanation held in discussion. Identify the question you need to answer and inspect the relevant thread as well as the page's conclusion.
Sources
Last reviewed: 2026-11-17. Documentation-backed guidance with an invented project example and proposed inspection; no performed export test.
Taha built Nemos after years of losing screenshots and voice memos across a dozen apps. He writes about on-device AI, personal knowledge management, and building privacy-first tools for iPhone.
@nemosapp
Stop losing things you save.
Nemos remembers every screenshot, voice memo, link, and note — and surfaces them when you need them. Free, private, on-device AI.
Free to download · No credit card · Sign in with Apple