Import a Project Board from Jira, Trello, or Asana

1. What Migrates

Every import — regardless of source — brings across each task's title, description, status/column, priority, and due date. Assignees migrate too, but only by matching the file's email address against an existing member of the destination project — a plain display name ("Dev User" instead of "[email protected]") won't match anyone, and the task simply imports unassigned.

What does not come across: sprints, epics, comments, attachments, and change history. If you rely on any of those, plan to recreate them on UnityFreak — there is no automated migration for them today. Labels/tags are a special case: they only import when the uploaded file is a raw JSON export that already contains a labels array on each task. Neither Jira/Asana's CSV column-mapping flow nor Trello's list-to-status mapping carries labels through, so tags on those imports need to be re-applied by hand afterward.

2. Export from Jira

From your Jira project's issue list: Issues → Export → CSV (the current filter's fields). Include at least Summary, Description, Status, Priority, Assignee, and Due date in the export.

Jira's default CSV export puts the assignee's display name in the Assignee column, not an email address — if your Jira admin has added an assignee email field to the export configuration, map that column to Assignee instead of the name column during the import step below to get real assignee matching.

3. Export from Trello

From your board: the board menu (Show Menu) → More → Print, export, and share → Export as JSON. UnityFreak reads the board's lists and cards directly from that file — no column mapping needed.

Trello exports don't include an assignee email at all, so Trello imports always land unassigned — plan to reassign tasks manually after the import. You'll map each Trello list to a UnityFreak status (or leave it blank to skip status) before the import runs.

4. Export from Asana

From your Asana project: the project menu → Export/Print → CSV. If your Asana plan lets you customize which columns are included, add Assignee Email to the export alongside the default Assignee column — UnityFreak prefers the email column automatically when both are present, since assignee matching only works by email.

Asana's Notes column maps to the task description and Section/Column maps to status automatically — no manual mapping needed for either.

5. Run the Import

From Project Settings → Import / Export, choose the matching source (CSV, Trello, Jira CSV, or Asana CSV) and upload the file you exported above. For CSV-based sources, UnityFreak auto-detects columns it recognizes and shows a mapping step so you can adjust or fill in anything it missed before confirming.

Imports over 500 rows only bring in the first 500 — split a larger export into batches if you need everything.

6. After the Import

Once the import finishes, work through this checklist:

• Re-create any sprints or epics your old tool grouped tasks into.
• Re-apply labels/tags if you imported from a CSV source — they don't carry over automatically (see the note in What Migrates).
• Reassign any tasks that landed unassigned because the email didn't match.
• Check due dates and priorities against a sample of the original board — imports fall back to sensible defaults (Medium priority, To Do status) for any row a column mapping didn't cover.