Bring your plan
Get your planning documents into Mapparoo.
Wherever your plan lives — Google Docs, Notion, Word, Confluence, Jira, or a platform knowledge file — there is a path here. Each one below says plainly what survives the trip and what does not.
Google Docs
File → Download → Markdown (.md), then upload the file.
What survives. Headings, lists, links, and body text arrive intact.
What doesn't. Comments, suggestions, and images stay behind in the doc.
Notion
Page menu (⋯) → Export → Markdown & CSV, then upload the exported files.
What survives. Page text and structure arrive as Markdown; databases arrive as CSV tables.
What doesn't. Comments, page history, and embeds stay behind.
Microsoft Word
Upload the .docx directly. We extract the text on our side and show it to you before anything is saved — the document is stored only after you confirm.
What survives. Headings, paragraphs, list text, and the text inside tables.
What doesn't. Images, comments, tracked changes, and page layout. We keep the extracted text, never the original file.
Confluence
Page menu (⋯) → Export → Word, then upload the .docx. For a single page, copying the text and pasting it here works just as well.
What survives. The written content of the page.
What doesn't. Comments, page hierarchy, and macros stay behind.
Jira, Trello, Asana
Export your backlog or board as CSV, then upload it.
What survives. We read ticket rows for what they are: a status column is a claim of progress, and acceptance criteria are the testable commitments.
What doesn't. Attachments and comment threads stay behind. Reading tickets this way is newer and less proven than reading narrative documents — your guide says so on its coverage banner.
Platform knowledge files
For CLAUDE.md, agents.md, Lovable or Bolt knowledge, and similar: open the file, copy the text, and paste it here with a name.
What survives. Exactly what you paste, stored exactly as pasted.
What doesn't. Nothing — pasted text is kept verbatim.
The practical limits
What fits.
- Up to 25 documents per project, 3 MB of stored text in total, 1 MB per uploaded file.
- Accepted uploads: .md, .txt, .csv, and .docx (converted to text at upload, with your confirmation).
- Schedule files and spreadsheets of dates are declined with a stated reason — they describe when, not what, so there is nothing there for an audit to check.
- Chat transcripts are not supported as plan evidence. If a transcript is most of what you have, a Discovery run reads the build directly and drafts the starting plan for you.
Your first plan map is free. Map my plan — free →