If your team already tracks work in Trello, Asana, or Jira, Examply can import boards, projects, and issues directly, so you don't have to recreate everything by hand. This article covers how to start an import and how each field maps into Examply.
Starting an import
Go to Settings → Import.
Choose Trello, Asana, or Jira and sign in to authorize the connection.
Select which boards, projects, or issue types to bring over.
Review the field mapping, then click Start import.
Note: Imports create new projects in Examply. They don't modify or delete anything in your source tool.
How fields map into Examply
Concept | Trello | Asana | Jira | Examply |
Container | Board | Project | Project | Project |
Grouping | List | Section | Status | Board column |
Work item | Card | Task | Issue | Task |
Tags | Labels | Tags | Labels | Labels |
Due date | Due date | Due date | Due date | Due date |
Assignee | Member | Assignee | Assignee | Assignee |
Sub-items | Checklist item | Subtask | Sub-task | Subtask |
Priority and estimate fields import when your source tool has an equivalent - for example, Jira's story points map to Examply's estimate field. Custom fields that don't have an Examply equivalent are skipped.
What doesn't come across
Comments, attachments, and time-tracking history from the source tool aren't imported. We recommend bringing over the work items first, letting your team get comfortable with Examply, and then re-attaching any files people still need day to day.
Assigning imported work to teammates
Examply matches assignees by email address during import. If a teammate's email in Trello, Asana, or Jira doesn't match their Examply account - for example, a client-services contractor using a personal address in one tool and a work address in the other - their tasks import unassigned, and you can reassign them in bulk afterward from List view.
Re-running an import
You can run the same import again later to bring over new boards or projects without duplicating what you already imported; Examply skips any source item it recognizes from a previous import. This is useful if a team migrates gradually, project by project, instead of all at once.
Troubleshooting
If an import stalls partway through, check that the connected account still has access to the source board or project - imports fail silently if access was revoked while the import was running. Large Jira projects with thousands of issues can take a few minutes; if an import doesn't complete within an hour, contact support@examply.com with the import ID from the Import log.