> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.edworking.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Import work from Asana, ClickUp, Jira, Monday, Notion or Trello

The import assistant copies supported exported work into Edworking. It is a one-time migration, not an ongoing connection to the original tool. The assistant is available on all plans, subject to workspace limits and permissions.

## Start with one project

1. Open **Import** in workspace settings.
2. Select **Asana**, **ClickUp**, **Jira**, **Monday**, **Notion** or **Trello**.
3. Read the export instructions for that source and prepare the supported export file.
4. Upload the file, then review the detected tasks, hierarchy and states.
5. Map assignees to Edworking members. Review unmatched people rather than assigning work to the wrong person.
6. Confirm the import, then inspect the resulting work in Edworking.

![Choose Asana, ClickUp, Jira, Monday, Notion or Trello in Edworking’s import assistant.](https://cdn.sanity.io/images/k9mx6lbx/production/e69fa0e00350d84c66e34321e50ce20021f8f669-770x560.png?w=770&fit=max&auto=format)

You need the relevant permission to create spaces or content in the destination.

## Notion documents

Notion imports can include documents as well as tasks. Upload the supported export ZIP and choose the destination space for documents. Review both counts before confirming. HTML and Markdown exports preserve different content, so use the wizard's guidance when choosing the export format.

## Know the limits

What comes across depends on the source and export. Automations, custom-field configuration and most attachments are not carried over. Asana CSV does not contain comments or attachments. Authenticated Jira and Trello attachment links are not imported.

The source workspace remains unchanged. Avoid repeating the same import without checking the result, because a second run may create duplicate work.

## Validate before moving the rest

Check a sample of titles, descriptions, states, dates, owners, subtasks and documents against the source. Review unassigned work and unsupported content. Keep the export and original workspace until your team is satisfied with the migration.

Related: [task management](https://help.edworking.com/en/article/task-management-in-edworking-a-complete-guide-for-teams-1drrukw/), [Docs](https://help.edworking.com/en/article/managing-documentation-in-edworking-13qeehy/) and [integrations](https://help.edworking.com/en/article/integrations-api-webhooks-in-edworking-sqxu8d/).

---

**Read this guide in another language:** [Deutsch](https://help.edworking.com/de/article/importieren-sie-arbeiten-aus-asana-clickup-jira-monday-notion-oder-trello-qpw2x6/) · [Español](https://help.edworking.com/es/article/importar-trabajo-desde-asana-clickup-jira-monday-notion-o-trello-1t13uhe/) · [Français](https://help.edworking.com/fr/article/importer-des-travaux-depuis-asana-clickup-jira-monday-notion-ou-trello-3sxjnu/) · [Italiano](https://help.edworking.com/it/article/importa-lavoro-da-asana-clickup-jira-monday-notion-o-trello-1iygqnm/) · [Português](https://help.edworking.com/pt/article/importar-trabalho-de-asana-clickup-jira-monday-notion-ou-trello-3yj79p/)