Build a migration view
Clone a list view and remove filters that would omit archived or older ideas.
Check what a Jira Product Discovery CSV preserves — before migration.
JPD can export ideas and their fields, but a CSV is not a complete backup of your discovery context. Audit the header locally, spot missing columns, and plan separately for data the standard export does not contain.
No file upload Header-only analysis Based on Atlassian documentation
Short answer
Insight content is the most important limitation.
According to current Atlassian documentation, a CSV can contain ideas and field information from the selected view. It does not export insight content: even when the Insights field is included, the file contains only the number of insights per idea. Reactions and Atlas fields are not supported in CSV export either.
That is why a high column count is not the same as migration readiness.
JPD export audit
Start with what is actually in your file.
The browser reads at most the first 64 KB locally to locate the first row; the tool analyzes only its delimiter and column names. It does not grade idea content or data quality, or claim that insight content was preserved.
Check your JPD CSV header
Choose a CSV or paste its first row. We analyze only the header locally and check which columns are visible.
The file stays in this browser. It is not sent to WorkThroughLine or any other server.
Transfer matrix
What standard JPD export preserves — and what it does not
Treat view CSV, the Excel/Google Sheets integrations, and JPD space configuration as three different scopes.
Yes / auditablePartial informationNot supported
| Data | View CSV | Excel / Sheets | What to do |
|---|---|---|---|
| Ideas and visible fields | Yes, from the selected view | Yes, for supported fields | Add every required field to the view before Download CSV. |
| Insight content and evidence links | No; Insights returns a count only | No | Request a separate data-portability export from Atlassian Support and validate its format independently. |
| Reactions | Not supported | Not supported | Record them through a separate process if they materially affect decisions. |
| Atlas fields | Not supported | Not supported | Create a separate goals and projects inventory before cutover. |
| Delivery progress and delivery status | Check the actual CSV header | Not supported | Preserve Jira delivery relationships and map them during preflight. |
| Custom formula fields | Check the actual CSV header | Not supported | Preserve the formula, its input fields, and calculated value as separate artifacts. |
| Views, field and project settings | Not a configuration backup | Not a configuration backup | Document views, filters, fields and rules before migration. |
Preflight workflow
Seven steps before retiring the old discovery space
Add identity and context
Include Key, Summary or Title, Description, Status, Created, Updated, Reporter, and every prioritization field.
Download CSV
Export from that view. Record the date, space, filter, and expected idea count.
Run the header audit
Check column names here. If a core field is missing, fix the view and export again.
Inventory known losses
Track insights, reactions, Atlas context, formulas, delivery relationships, and configuration separately — not as ordinary CSV columns.
Test a small sample
Import a representative set and verify statuses, users, special characters, dates, and custom fields before the full move.
Reconcile the result
Compare idea counts by status, owner, and period, document exceptions, and only then schedule cutover.
How to interpret the audit
What the result confirms
- Which column names are present in this file.
- Whether four core fields were found: Key, Summary/Title, Description, and Status.
- Whether Insights appears as a count and whether delivery columns need another check.
What the result does not confirm
- That every row is populated or correctly formatted.
- That insight text, source, author, or evidence links were preserved.
- That a destination can understand custom fields and users without mapping.
Primary sources
Recheck limitations where they change
JPD evolves quickly. This page was last verified on August 28, 2026; reopen the current Atlassian documentation before a large migration.
Move from inventory to controlled migration
Jira Product Discovery export FAQ
Does JPD CSV export insights?+
It does not export insight content. If the Insights field is present in the view, Atlassian says the CSV contains only the number of insights for an idea. For data portability, Atlassian directs customers to request a separate insights export.
Does this tool upload my CSV?+
No. The browser reads at most the first 64 KB locally to locate the first CSV row. The contents are not sent to WorkThroughLine or any other server.
Can a header audit prove that migration is safe?+
Not by itself. It confirms column presence. You still need value inspection, mapping, a test import, and reconciliation of idea and relationship counts.
Why is a field I can see in JPD missing from the export?+
View CSV depends on the selected view and its fields. Some fields have method-specific limitations, so check the view, export permission, and export method first.
Do Excel and Google Sheets export delivery and formula fields?+
According to Atlassian documentation verified on August 28, 2026, delivery progress, delivery status, and custom formula fields are not supported by those export methods.
What should I preserve alongside the CSV?+
Document views, filters, field settings, project settings, formulas, delivery relationships, and how insights supported decisions. CSV alone is not a complete backup of a discovery system.
Do not import blind. Build the inventory and mapping first.
Once you know what the CSV carries, run a controlled preflight on a representative sample and record every known loss before cutover.