For AI agents: a documentation index is available at /llms.txt. A markdown version of this page is available at /guide/cloud/tasks/import-and-export.md.
Import and export
Bring work in from another tool, and get your data back out.
Pro and Premium
Import and export require Pro Unlimited or above. See the feature matrix.
#Importing tasks
CSV import creates tasks in bulk — the usual path when migrating from another tool or from a spreadsheet.
Export from the old tool
Most trackers export CSV. Get everything, then trim.
Decide what actually moves
Do not import everything
Years of closed tasks add noise and hide the work that matters. Import what is open or recently closed; archive the rest as a CSV file somewhere safe.
Map the columns
Match your CSV headers to Orangescrum fields. At minimum: title, status, assignee, due date.
Assignees match on email address. Anyone not already a user in the workspace will not map — invite them first.
Test with 20 rows
Import a small slice into a scratch project and look at the result. Fix the mapping, then run the full file.
Import for real
Then spot-check: pick five tasks and compare against the source.
#Common mapping problems
Dates come in wrong
Date format ambiguity — 03/04/2026 is two different dates depending on
locale. Convert the CSV to YYYY-MM-DD before importing.
Assignees are blank
The CSV has display names, not email addresses, or the people are not users yet. Invite them first, then map on email.
Statuses don't match
Your source statuses differ from your Orangescrum custom statuses. Either map them during import, or set up matching statuses first.
Descriptions lose formatting
CSV carries plain text. Rich formatting, embedded images and attachments do not survive — plan to re-attach anything critical.
Everything imported twice
A re-run duplicates rather than updating. Delete the first batch before retrying.
#What doesn't import
| Not carried over | Do instead |
|---|---|
| Comment history | Export to PDF/CSV and keep as an archive |
| Attachments | Re-attach the ones that matter |
| Time logs | Export from the old tool and keep for reporting |
| Cross-tool links | Re-link after import |
Keep the old system read-only for a while
Do not decommission it the day you migrate. Keep it readable for a few months so people can retrieve history you did not bring across.
#Exporting
Export task lists to CSV from the task list view, with your current filters applied — so you can export exactly the slice you want rather than everything.
Useful for:
Pull into a spreadsheet or BI tool for analysis you cannot do in-product.
A filtered export of one client's work.
A periodic snapshot outside the product.
Export, edit in a spreadsheet, re-import as new tasks.
Sprint reports can also be exported to PDF — see Reports.
#Programmatic access Premium
For anything ongoing, use the Developer API rather than scheduled CSV exports — 59 endpoints covering projects, tasks, timelogs and more, with proper filtering.
⚡Developer APIRead and write your data programmatically.