Moving from ChatPRD to Deck: What Transfers and How to Use Both

Last updated: · By Matt Teixeira, Founder and CEO

You do not migrate data from ChatPRD to Deck the way you would from a feedback tool, because ChatPRD stores documents and Deck works from customer feedback. Export your PRDs to Notion, Confluence, or Google Docs, connect your feedback sources to Deck, and, if you like ChatPRD's writing, keep it and connect both through MCP.

Key Takeaways

  • There is no data migration in the usual sense. ChatPRD stores documents and chats; Deck stores customer feedback and the opportunities derived from it.
  • Keep your PRDs by exporting them to Notion, Confluence, or Google Docs, which ChatPRD supports (UX Magic).
  • Start Deck from feedback, not documents. Deck does not document a PRD importer. Its Notion and Confluence integrations sync pages, such as meeting notes, and analyze them as feedback.
  • Or keep both and connect them in one assistant through MCP.

What Moves and What Does Not?

ChatPRD contentWhat to doIn Deck
PRDs and specsExport to Notion, Confluence, or Google DocsNot imported; link from Projects as needed
TemplatesKeep in your doc toolNo equivalent
ChatsNot portableNo equivalent
Project knowledgeKeep source filesDeck builds context from feedback sources
Customer evidenceNever lived in ChatPRDConnect sources; Deck creates themes and ranked opportunities

How Do You Move from ChatPRD to Deck?

  1. Export your ChatPRD documents. Use ChatPRD's export to Notion, Confluence, or Google Docs so your PRDs stay in your document system.
  2. Create a Deck workspace. Sign up at getdeck.io and choose your hosting region during setup.
  3. Connect feedback sources to Deck. Connect Intercom, Zendesk, Gong, Granola, Slack, or upload interview recordings and CSVs.
  4. Review the Opportunity Backlog. Check which ranked problems support, or contradict, the PRDs you exported.
  5. Create Projects for active work. Create Projects in Deck or import Linear projects and Jira epics, and attach the evidence.
  6. Connect Deck to your AI tools. Add the Deck MCP server to Claude, Cursor, or ChatGPT so new specs start from customer evidence.

Should You Switch or Use Both?

Most teams that like ChatPRD's writing should keep it and add Deck for evidence. Switch fully only if your PRDs mainly restate customer problems and Deck Project specs are enough for your engineers and coding agents.

Frequently Asked Questions

Deck does not document a PRD importer. Export your ChatPRD documents to Notion, Confluence, or Google Docs and link them from Deck Projects where useful.

The tools store different things. ChatPRD stores documents and chats, while Deck stores customer feedback and the opportunities it ranks.

No. Many teams use ChatPRD for writing and Deck for customer evidence, connected through MCP.

Connecting a few feedback sources usually takes minutes. Processing time depends on volume and credits.

Deck uses customer feedback from interviews, tickets, calls, Slack, surveys, and NPS to create themes, ranked opportunities, initiatives, and Projects with specs.

Sources

Related: Deck vs ChatPRD · ChatPRD alternatives · ChatPRD alternatives by team · Deck MCP server · All comparisons