Export guide

Jake Sawyer

Updated June 18, 2026 20:43

This guide contains high-level information about the exporting methods available in Productboard, which items can be exported, and the best way to fulfil certain export use cases. It also contains links to more detailed articles about specific export methods.

Note: This article references our public API, but not in detail. For that, visit our API documentation.

Export methods

There are three main ways to export data from Productboard.

CSV endpoint

Paste a special URL into your browser to trigger a pre-configured export. The exact set of data included in this export depends on the URL you use. You'll receive an email containing a link to download the CSV.

This is good for quickly pulling tons of data indiscriminately. It's also useful if you need timestamps for when entities were created or updated, as the UI export method does not include such data.

See Exporting your features into a CSV or Exporting your feedback into a CSV for more details.

Note: To use a CSV endpoint, you'll need the name of your Productboard workspace, which you can find in your URL bar once you've logged in. (It's the bit just before ".productboard.com".)

UI export

Click a button on a board to export the visible data on that board (respecting filters, data columns, item type configuration, and other local settings). Export file types and delivery mechanisms vary depending on the board type you're exporting from.

This is good for targeting specific data for export, and for collecting UUIDs for use with our public API.

See Exporting your features into a CSV, Share your roadmap by exporting to PNG, or Collaborate on documents within Productboard for details.

Public API

We have a robust collection of API endpoints you can use to design your own export tools and integrations. Data you export via API is delivered however you configure it to be.

This option is good for technical implementations, though it's by far the most labor-intensive, and as such it is beyond the scope of this article.

See API Documentation for details.

Method matrix

The following matrix describes which export methods are possible for fulfilling specific export use cases. You can read more about these use cases below.

Data to export	CSV endpoint	UI export	Public API
Main product entities (products, components, features, and subfeatures)	✅ YES	✅ YES	✅ YES
Any product entities (anything you can set as an item type on a grid, including features, objectives, and companies)	❌ NO	✅ YES	✅ YES
Feedback (with or without feature associations)	✅ YES	❌ NO	✅ YES
Roadmap images (PNGs of timelines and columns boards)	❌ NO	✅ YES	❌ NO
Workspace members and team assignments	❌ NO	❌ NO	✅ YES
Audit logs	✅ YES	❌ NO	❌ NO

Specific export use cases

Here is a list of common export use cases, tips for efficient execution, and links to more in-depth articles.

Note: These use cases will ignore the public API as a solution, since that method requires programming expertise which is outside the scope of this article.

Export an unorganized list of your main product hierarchy items

If you need a quick and comprehensive export of all your products, components, features, and subfeatures, with no pre-filtering or organization, use the features CSV endpoint:

https://[your_workspace].productboard.com/api/features/export

Requires minimal setup.
Includes timestamps (created_at and updated_at).
Includes all custom fields and many default fields, like status, team assignment, and timeframe data.

See Exporting your features into a CSV for details and troubleshooting.

Export an organized, filtered list of any product hierarchy items

Anything you can put on a grid board can be exported as-is using the grid UI export. That means only the item types, filters, and data columns you add to the grid will be included in the final export.

Requires a bit more setup.
Able to export any item type (products, components, features, subfeatures, objectives, key results, initiatives, release groups, releases, companies, and users), though not all at once.
Only includes in the CSV what's on the board, meaning you can exclude custom fields you aren't interested in by not adding them as columns before exporting.
The order of items on the board dictates the order of items in the CSV.
Includes UUIDs for each item, its parent, and its overall path, making it much easier to collect data for building more advanced tools with the public API.
Also includes URL data for each item.

See Exporting your features into a CSV for details and troubleshooting, and Grid boards: Planning and prioritization management for help configuring your grids to display the right data.

Export your companies and users

To export a list of companies, users, or both, you should use the grid UI export. Before you start the export, configure the grid so that your main item type is Companies and (optionally) your second item type is Users, and add any filters you might want. In effect, your Board controls should look like the image below.

Otherwise, see the previous section for details.

Export all your feedback across all insights boards (with or without feature associations)

There's currently only one option for exporting feedback data, and that's the feedback CSV endpoint:

https://[your_workspace].productboard.com/api/notes/export

This exports all feedback in your workspace. If you want to include information about which features are associated with each piece of feedback, you can use this endpoint instead:

https://[your_workspace].productboard.com/api/notes/export?export_type=with_features

For cleaner text in the export, you can append "&strip_html=true" to your endpoint, like so:

https://[yourworkspace].productboard.com/api/notes/export?export_type=with_features&strip_html=true

Note: Feedback originating from Slack, Zendesk, and Intercom is exported without the text of the feedback itself. It's not a bug, it's a (missing) feature.

See Exporting your feedback into a CSV for details and troubleshooting.

Export a list of features with associated insights

You have to use the feedback CSV endpoint as laid out above. There is currently no way to export this data in a feature-forward way; it must be feedback-forward.

Export roadmaps as images

If you want to download images of your timelines and columns boards, use the timeline or columns board UI export. The image will immediately download to your local device via your web browser.

Remember that this method respects board configuration and filters, and you don't have to save a board before exporting it.

See Share your roadmap by exporting to PNG for detailed instructions.

Export a list of deleted features

If you want to track down deleted features and who deleted them, you can use the audit log CSV endpoint with the "?action_name=delete" command.

Note: To export an audit log, you must be a workspace admin, and your workspace must be on the Enterprise plan.

To do this:

Open a new tab in your browser and paste the following into your URL bar:

https://<your_workspace>.productboard.com/api/audit_logs/export?action_name=delete

Follow the instructions on screen to receive your export.

See Export an audit log for your workspace for more details and other options.

Export your entire workspace for backup or offboarding

There is currently no way to do this efficiently. Instead, you'll have to use the various export methods outlined in this article (potentially alongside the public API) to collect the data you need piece by piece.

See our portal to provide feedback about this limitation.

Limitations and quirks

Here is a non-exhaustive list of other things that our current export capabilities cannot handle, or cannot handle well.

Using the audit log to view deleted features does not give you the ability to restore them. If critical data has been deleted from your workspace, email support@productboard.com to attempt restoration.
Feedback from Slack, Zendesk, and Intercom is exported without its body text, meaning you can't actually export the feedback part of that feedback. Please let us know your feelings about this on our portal.
The public API uses UUIDs, not IDs, to read and write item data. The features CSV endpoint does not contain UUID data, but the grid UI export does, so you should use the latter if you're looking for UUIDs to use with the public API.
Conversely, the grid UI export doesn't include timestamps for item creation and update date. So if you need timestamps, you need to use the features CSV endpoint.