Deck

How to Migrate from Productboard to Deck

Last updated: · By Matt Teixeira, Founder and CEO

To migrate from Productboard to Deck, export your feedback with Productboard's notes CSV endpoint, upload it to Deck as a Feedback CSV, reconnect Slack, Intercom, Zendesk, and Gong directly to Deck, and import roadmap work from Jira or Linear. Feedback text and requester details carry over. Portals and votes do not.

Key Takeaways

  • Productboard feedback exports through one route: the notes CSV endpoint https://[workspace].productboard.com/api/notes/export, which emails you a download link (Productboard Support).
  • Known gap: Productboard exports feedback from Slack, Zendesk, and Intercom without the feedback text (Productboard Support). Reconnect those sources to Deck instead.
  • Deck imports five CSV types: NPS, User Interview, CS Ticket, Feedback, and Survey. Files can be up to 10 MB each (Deck CSV Import docs).
  • Budget credits: Deck's planning baseline is about 3 credits per CSV row and about 17 credits per 30-minute interview (Deck pricing).
  • Plan for about 2 hours of hands-on work for a typical workspace, plus processing time.

What Carries Over from Productboard to Deck?

Productboard dataHow to export itWhere it goes in DeckCarries over?
Feedback notes created in Productboard, the Portal, the Chrome extension, or emailNotes CSV endpointFeedback CSV upload, where each row becomes insights and themesYes
Note requester (user name, user email)Included in the notes CSVMapped to Respondent Name and Email and linked to Unified ContactsYes
Note created dateIncluded in the notes CSV (created_at)Mapped to Submitted DateYes
Feedback from Slack, Zendesk, and IntercomExports without body textReconnect the integration in DeckRe-synced from the source (Intercom and Zendesk: last 90 days)
Tags and feature links on notes?export_type=with_featuresNot imported as fields; Deck re-themes the feedback automaticallyPartly (kept in your CSV archive)
CompaniesGrid UI exportSegments plus CRM contact sync (HubSpot, Salesforce, Attio)Rebuilt in Deck
Features and roadmap itemsFeatures CSV endpoint or grid exportImport Jira epics or Linear projects as Deck Projects; recreate top bets as initiativesVia Jira or Linear
Portal ideas and votesNot covered by an export route in Productboard's guideNo direct equivalent; use the Deck Collect widget going forwardNo
Roadmap imagesPNG export from timeline or columns boardsArchive onlyNo

Sources: Productboard export guide, Deck CSV Import, Deck Projects, Deck Intercom and Zendesk docs.

What Do You Need Before You Start?

You need maker or admin access in Productboard, a Deck workspace, and enough Deck credits for your feedback volume.

  • Productboard: You must be a maker or admin to run a CSV export. You also need your workspace name, which is the part of your URL before .productboard.com (Productboard Support).
  • Deck: Create a free workspace at getdeck.io. Choose your hosting region (North America, Europe, or APAC) during setup, because the region is set when the organization is created (Deck pricing).
  • Credits: Multiply your row count by about 3 credits. For example, 2,000 notes ≈ 6,000 credits, which fits within Deck Business's 7,500 monthly credits. If an upload exceeds your credits and overage is off, Deck processes what it can and marks the rest as "Waiting for Credits" instead of discarding them (Deck CSV Import).

How Do You Export Feedback from Productboard?

Paste the notes export URL into your browser while signed in, then download the CSV from the email Productboard sends.

  1. Sign in to Productboard.
  2. Open https://[your_workspace].productboard.com/api/notes/export?export_type=with_features&strip_html=true in your browser. with_features adds the linked feature name and ID. strip_html=true removes HTML from the text (Productboard Support).
  3. Wait for an email from Productboard with a download link, then download the CSV.
  4. Check the columns: note_title, note_text, user_name, user_email, company_name, company_domain, created_at, tags, source_url, and others (Productboard Support).

How Do You Export Features and Companies from Productboard?

Use the features CSV endpoint for a full product hierarchy with timestamps, and use a grid board export for companies and users.

  1. Features: open https://[your_workspace].productboard.com/api/features/export. It includes timestamps, custom fields, status, team, and timeframe data.
  2. Companies and users: create a grid with Companies as the main item type and Users as the second, then choose ••• More actions → Export as CSV (Productboard Support).
  3. Keep both files as your archive. Productboard notes that "there is currently no way" to export an entire workspace efficiently, so collect each piece you need (Productboard export guide).

How Do You Prepare the Productboard CSV for Deck?

Remove rows with no text, combine the title and body, and split files larger than 10 MB.

  1. Delete empty rows. Rows where note_text is blank usually came from Slack, Zendesk, or Intercom. Those sources will re-sync when you reconnect them to Deck.
  2. Combine title and text into one column (for example content = note_title + ": " + note_text), because Deck's Feedback type requires a single content field (Deck CSV Import).
  3. Separate interviews. If some notes are full interview transcripts, move them to a second file and upload them as the User Interview type (required field: transcript).
  4. Split large files into parts under 10 MB.
  5. Start small. Deck recommends a 20–50 row test file before uploading thousands of rows.

How Do You Import Productboard Feedback into Deck?

Upload the CSV in Manage → CSV Uploads, choose the Feedback type, map the columns, and submit.

  1. In Deck, go to Manage → CSV Uploads → Upload CSV. You can also drop the file into the onboarding chat (up to 10 MB).
  2. Select Feedback as the type. Deck detects types from headers where it can.
  3. Map columns: content → Content, user_email → Respondent Email, user_name → Respondent Name, created_at → Submitted Date. Optionally map a column to Source with a value such as "Productboard". The field accepts any text.
  4. Optionally assign a default segment for the whole upload. Every insight from that file inherits it.
  5. Review validation. Deck lists invalid rows with the reason and removes exact duplicates.
  6. Submit. Track status in CSV Uploads (Pending, Processing, Completed, Partially Completed, or Waiting for Credits). A notification confirms how many rows were processed (Deck CSV Import).

How Do You Reconnect Live Feedback Sources?

Connect each source directly to Deck in Settings → Integrations so new feedback flows in automatically.

  • Intercom and Zendesk: Deck fetches the last 90 days of history on connect (Intercom docs, Zendesk docs).
  • Gong: run a historical backfill of the last 1, 3, 6, or 12 months, with a credit estimate first (Gong docs).
  • Slack: add your feedback channels. Every plan includes unlimited Slack feedback channels (Deck pricing).
  • CRM: connect HubSpot, Salesforce, or Attio on Business and higher to rebuild company segments.
  • Plan limits: Free allows 1 integration, Starter 5, and Business unlimited.

How Do You Bring Over Your Roadmap?

Import the Jira epics or Linear projects your Productboard features synced to, then let Deck attach evidence.

  1. Connect Jira or Linear in Deck.
  2. In Build → Projects, import existing Linear projects or Jira epics. Deck refreshes their top-level metadata daily, and Project documents, evidence, and metrics stay owned by Deck (Deck Projects).
  3. Recreate your top strategic bets as initiatives and link the Projects to them.
  4. After feedback finishes processing, Deck can automatically relate high-confidence insights to relevant Projects.

How Do You Check the Migration Worked?

Compare counts, spot-check themes, and ask Deck questions you already know the answers to.

  1. Compare the row count in your CSV with the "rows processed" count in Deck.
  2. Open Themes and confirm the top themes match what your team expects.
  3. Connect the Deck MCP server in Claude, ChatGPT, or Cursor and ask, for example, "What are the top pain points from customers imported from Productboard?" Answers include quotes and source links.
  4. Keep Productboard read-only for a few weeks, until your team trusts the new workflow.

Frequently Asked Questions

Not in one step. Productboard's export guide says there is currently no way to export an entire workspace efficiently. You export feedback, features, and companies separately through CSV endpoints, grid exports, or the public API.

Productboard exports feedback that came from Slack, Zendesk, and Intercom without its body text, and the note_text field is left blank. Reconnect those sources directly to Deck instead. Deck fetches the last 90 days from Intercom and Zendesk when you connect them.

Deck does not list a dedicated Productboard connector. You migrate with Deck's CSV Import using the Feedback type, which accepts a content column plus optional respondent email, name, source, and date.

Deck's planning baseline is about 3 credits per CSV row, so 2,000 notes use roughly 6,000 credits. Actual usage varies with text length. Rows beyond your available credits wait instead of being discarded.

No. Productboard portal ideas and votes have no direct equivalent in Deck. Keep the export as an archive and collect new in-app feedback with the Deck Collect SDK widget.

Most of the work is exporting and cleaning CSVs and reconnecting integrations. Processing time depends on volume and credits, and you can track it live in Deck's CSV Uploads page.

Sources

Related: Deck vs Productboard · Productboard alternatives · Best alternatives by team type · Deck MCP server · All comparisons