Navalo , home
Migrate

Bring the board
you already have.

Live importers ship for Jira, Asana, Trello and Linear, and a monday.com board comes across through the paste importer while its direct connection is switched off. Each has a page that says, field by field, what comes across and what is left behind, because the only question worth answering before a migration is what you are going to lose.

Live import: Business and abovePaste import: every plan
Start freeAll integrations
The five

Pick where your work lives now.

Every page lists the mapping and the ceilings. None of them claims a step the importer does not perform.

Jira

5 of 12 fields

Pick a Jira project and Navalo builds it here: one column per status, one task per issue, the issue key kept in the title. What is mapped and what is not, in full.

Read it

Asana

4 of 12 fields

Pick an Asana project and Navalo builds it here: one column per section, one task per task, the notes field as the description. What is mapped and what is not, in full.

Read it

Trello

4 of 12 fields

Pick a Trello board and Navalo builds it here: one column per open list, one task per card, the card description kept as written. What is mapped and what is not, in full.

Read it

monday.com

By CSV for now

Direct import from monday.com is off for now. Export the board to CSV and paste it: the name, status, owner, due date, priority and description columns come across.

Read it

Linear

5 of 12 fields

Pick a Linear team and Navalo builds it here: one column per workflow state in Linear's own order, one task per issue, the identifier kept in the title.

Read it
True of all five

What an import is, and is not.

These five sentences are written once and rendered on every importer page, because five copies of one paragraph is five chances for four of them to go stale.

  • An import is a one-off copy, not a running sync. Nothing is written back to the source, and running the same import twice creates a second project with the same tasks in it.
  • Your credentials are never stored. They travel with the request, make the calls and are discarded; there is no token table behind this.
  • There is no undo. If an import is wrong, delete the project it made and run it again.
  • Every finished import writes an audit row: which source, how many columns, how many tasks, who ran it, whether it finished cleanly and why any rows were skipped. A live import that fails writes one too. Pasting a file writes one, and both kinds appear in the same list.
  • The person who runs the import becomes a manager on the new project, and the project takes your organisation's default visibility.
Questions

Before you migrate.

Is an import a one-off copy or a running sync?
A one-off copy. Nothing is written back to the source, nothing here changes when the source does, and running the same import twice creates a second project with the same tasks in it.
Are my API tokens stored?
No. They travel with the request, make the calls and are discarded. There is no token table behind the importer.
Can I undo an import?
There is no undo button. If an import is wrong, delete the project it created and run it again. Every import does leave an audit row: which source, how many columns, how many tasks, who ran it and whether it finished cleanly.
What if the importer does not bring the field I need?
Export a CSV from your current tool and use the paste importer instead. It is on every plan and it maps a due date, and an assignee when the name or email matches someone in your workspace, which the live importers do not.
Every comparisonPricing