Select the data
Open "Issues", apply a search query and filters, then review the results. Export uses that selection and your issue access. A project filter is useful when you need to transfer work to another project. Use QQL for precise selection.
A person without a writing seat retains reading and export access within their permissions. Export does not grant access to restricted issues. A downloaded file is a copy of the data; later changes in Quevell do not update it.
CSV table
Open "Export" and choose "CSV". The interface exports the first 1000 matching issues; the API allows up to 10000. Narrow the filter or use ZIP when you need more. Check the row count and sample values after opening the file.
CSV is useful for spreadsheet work and import preparation. It does not contain binary attachments or the complete issue history. See import columns for field names and mapping rules. When opening a spreadsheet, check the encoding and delimiter so a multiline description remains a single cell.
Issue and attachment archive
Open "Export" and choose "ZIP with attachments". Quevell builds the archive in the background. Wait until it is ready and use its download link; you receive a notification in Inbox when the export is ready. The export belongs to the person who requested it. A ready file is kept for one day, after which you must request another export.
An archive contains no more than 50000 issues. A request over that limit is rejected in full. The archive contains:
| File | Contents |
|---|---|
issues.csv | Issue table with attachment paths |
issues.json | Detailed issue data, fields, comments, links and history |
attachments/ | Accessible issue files present when the archive is built |
Deleted attachments and image thumbnails are not included as separate original files. Issue links are limited to accessible objects. Individual worklogs are not exported as a complete ledger: JSON contains the time totals.
After downloading, open the archive and inspect issues.csv, sample records in issues.json and their files. If the export fails or the link expires, check access and filters before requesting another. A partial download is not a complete export. MCP checks access to each issue again when reading export results; losing access may call for a fresh export.
What re-import restores
You can upload a Quevell ZIP through the destination project's importer. It reads issues.csv and attaches files using their paths. The import checks issue types, field values, required fields, people and hierarchy against the destination project's settings. Start with a ZIP preview and resolve the reported errors.
| Data | In the export | ZIP import |
|---|---|---|
| Summary, description, status, priority, assignee and reporter | CSV and JSON | CSV values mapped to the destination project's settings |
| Type, parent and creation date | CSV inside ZIP and JSON; not included in standalone CSV | Type and creation date; the parent matched to a file key or an accessible issue |
| Original key, project and update date | CSV and JSON | The original key is retained for search; issues receive new keys in the selected project, and the update date is not restored |
| Attachments | Files in the archive, paths in CSV and details in JSON | Files matched by the ZIP import rules |
| Custom fields, labels, original and remaining estimates, time spent, start date and due date | JSON only | Not transferred from JSON |
| Issue links, comments and history | JSON only | Not restored; parent hierarchy is transferred separately through CSV |
Standalone CSV contains basic issue columns, without type, parent, creation date or files. The importer accepts additional columns, such as custom fields and estimates, if you prepare them yourself. That does not mean those columns are included in the standard CSV or in the ZIP's issues.csv. See import columns for the full reference and ZIP format for file matching.
issues.json lets you read and process detailed data. The importer does not use it for restoration. Individual worklogs are not included as a complete ledger; JSON holds only time totals. This export is not a full company backup.
When you import a ZIP into the same destination project again, rows whose original keys have already been imported are skipped. Quevell matches the retained original key, not the issue summary; it does not update an existing issue. The preview lists skipped original keys and their matching issues. The import result counts skipped rows and maps original keys to newly assigned keys. Plain CSV does not skip rows this way, so importing it again can create duplicates. ZIP does not provide universal duplicate protection either: another destination project or a row without an original key is outside that check.
Import allows up to 5000 rows and has a file-size limit, so a large export may need splitting. Set up destination fields and types, review the mapping in the preview and keep the result with the new issue keys after the transfer.
Markdown pages
Open a knowledge page and choose "Download .md" from its actions menu. This downloads one page's title and body. An open editor exports its current text; publish first when you need the saved version.
Markdown does not transfer the page tree, permissions, history or structured links. See Knowledge base for the workflow. There is currently no single user export that restores an entire company with all its configuration.
Employee data
In Administration → Users, choose Export employees. You can select the standard and company profile fields to include. The export follows the current search and status filter across the full result, not just the loaded page.
The CSV contains employee data without activity metrics, sign-in dates, issues or time records. Erased personal data and service accounts are excluded. Person field values are written as email addresses. Files use UTF-8 for spreadsheet compatibility; potential formulas are escaped as text.