Migrating from another tool is a few clicks. Lattica imports from Asana, Trello, Linear, Jira, ClickUp, Monday, and Notion — preserving structure, comments, attachments, and history.
The general flow
- Open Settings → Imports → New import
- Choose your source tool
- Authorize Lattica to read your data
- Pick which projects, boards, or workspaces to import
- Preview the mapping (Lattica shows you exactly what becomes what)
- Confirm and start
Imports run in the background. You’ll get an email when it’s done — typically a few minutes for small workspaces, up to an hour for very large ones.
Asana
Maps Asana projects to Lattica projects, sections to sections, tasks to tasks, and portfolios to a Lattica folder. Asana custom fields become Lattica custom fields. Comments and attachments come over with original timestamps and authors. Subtasks remain subtasks.
Not imported: Asana goals (use Lattica milestones instead) and inbox notifications.
Trello
Each Trello board becomes a Lattica project; lists become sections; cards become tasks; checklists become subtasks. Power-Ups are not imported — re-implement what you need with custom fields or automations.
Linear
Linear teams become Lattica projects, cycles become milestones, issues become tasks. Linear’s “triage” and “backlog” map to default Lattica statuses. Labels become tags. Sub-issues become subtasks.
Jira
The richest mapping. Jira projects become Lattica projects; epics become milestones with linked tasks; stories and tasks become tasks; subtasks become subtasks. Sprints map to milestones. Custom fields with Jira-specific types (e.g. version, sprint, story-points) become Lattica custom fields of the closest equivalent type.
Notion
Lattica imports from Notion databases that have a “Tasks” structure — anything with title, status, and assignee columns. Pages become rich-text descriptions. Other Notion databases (CRMs, wikis, and so on) aren’t a fit for migration; export them separately.
What to do after
Set up your saved views, customize task statuses to match your team’s flow, and connect your integrations. Most teams find the first week is spent removing structure rather than adding it — your old tool’s quirks come over too, and Lattica is at its best when there’s less of them.