Migrating from another tool is a few clicks. Lattica imports from Asana, Trello, Linear, Jira, ClickUp, Monday, and Notion \u2014 preserving structure, comments, attachments, and history.<\/p>\n
Imports run in the background. You’ll get an email when it’s done \u2014 typically a few minutes for small workspaces, up to an hour for very large ones.<\/p>\n
Maps Asana projects<\/em> to Lattica projects, sections<\/em> to sections, tasks<\/em> to tasks, and portfolios<\/em> to a Lattica folder. Asana custom fields become Lattica custom fields. Comments and attachments come over with original timestamps and authors. Subtasks remain subtasks.<\/p>\n Not imported: Asana goals (use Lattica milestones instead) and inbox notifications.<\/p>\n Each Trello board<\/em> becomes a Lattica project; lists<\/em> become sections; cards<\/em> become tasks; checklists become subtasks. Power-Ups are not imported \u2014 re-implement what you need with custom fields or automations.<\/p>\n Linear teams<\/em> become Lattica projects, cycles<\/em> become milestones, issues<\/em> become tasks. Linear’s “triage” and “backlog” map to default Lattica statuses. Labels become tags. Sub-issues become subtasks.<\/p>\n The richest mapping. Jira projects<\/em> become Lattica projects; epics<\/em> become milestones with linked tasks; stories<\/em> and tasks<\/em> become tasks; subtasks<\/em> 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.<\/p>\n Lattica imports from Notion databases that have a “Tasks” structure \u2014 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.<\/p>\n 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<\/em> structure rather than adding it \u2014 your old tool’s quirks come over too, and Lattica is at its best when there’s less of them.<\/p>\n","protected":false},"excerpt":{"rendered":" Step-by-step migration from six tools, what maps to what, and what to clean up after.<\/p>\n","protected":false},"author":0,"featured_media":56,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[69,68,71,45,67,70],"class_list":["post-55","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-getting-started","tag-asana","tag-import","tag-jira","tag-linear","tag-migration","tag-trello"],"_links":{"self":[{"href":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/wp-json\/wp\/v2\/posts\/55","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/wp-json\/wp\/v2\/comments?post=55"}],"version-history":[{"count":0,"href":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/wp-json\/wp\/v2\/posts\/55\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/wp-json\/wp\/v2\/media\/56"}],"wp:attachment":[{"href":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/wp-json\/wp\/v2\/media?parent=55"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/wp-json\/wp\/v2\/categories?post=55"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/demo.fasterthemes.com\/mywiki-wordpress-theme\/wp-json\/wp\/v2\/tags?post=55"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Trello<\/h2>\n
Linear<\/h2>\n
Jira<\/h2>\n
Notion<\/h2>\n
What to do after<\/h2>\n