Can I import my tasks into Vikunja from Todoist, Trello, or Microsoft To-Do?

Updated

Yes. Vikunja has built-in migration support for Todoist, Trello, Microsoft To-Do, and other platforms, so you can bring existing tasks over instead of rebuilding your setup by hand. The import is aimed at being quick — the project describes moving your tasks in minutes — and imported tasks land in the same workspace where Vikunja's List, Kanban, Gantt, and Table views are available.

What the import covers

Vikunja's own documentation and FAQ confirm migration support for:

  • Todoist
  • Trello
  • Microsoft To-Do
  • Other platforms (the site refers to "and other platforms" without listing them all)

The site does not publish a field-by-field mapping (for example, exactly how Trello labels or Todoist priorities translate). Treat the import as a way to carry your tasks and projects across, then spot-check the result rather than assuming every attribute survives unchanged.

Before you start

  1. Have a Vikunja instance ready. Either self-host it (Docker, native binaries, or the install wizard) or sign up for Vikunja Cloud, the managed hosted option.
  2. Export from your current tool. Todoist, Trello, and Microsoft To-Do each provide their own export or backup function; use that to produce the file Vikunja's importer expects.
  3. Know where you're importing to. Decide whether the tasks belong in a new project or an existing one, since that affects how you organize them afterward.

How the import works

The general flow is the same regardless of source:

  1. Open your Vikunja instance and start a new import, choosing your source platform (Todoist, Trello, or Microsoft To-Do).
  2. Provide the export file from that platform.
  3. Run the import and wait for it to finish.
  4. Open the resulting project and confirm tasks, lists, and structure arrived as expected.

The site does not document exact menu paths or importer screens, so follow the prompts in your instance rather than a fixed click sequence. The expected result is your existing tasks appearing inside Vikunja, ready to be viewed as a list, Kanban board, Gantt chart, or table.

After importing: what to check

  • Structure: confirm projects and lists map to how you want to work, and merge or rename where needed.
  • Views: switch between List, Kanban, Gantt, and Table to see which layout fits each project — the same tasks are available in all four.
  • Collaboration: if you're moving a team, share the imported projects and assign tasks so colleagues can pick up where they left off.
  • Cleanup: archive or delete anything you no longer need; a migration is a good moment to prune stale tasks.

Common snags

  • Missing export file: the importer needs a file from your old tool, so complete that platform's export step first.
  • Unexpected structure: if lists or boards arrive in a shape you didn't expect, reorganize within Vikunja rather than re-importing repeatedly.
  • Unsupported attributes: because the site doesn't promise a complete field mapping, verify anything critical (due dates, assignees, labels) after the import.

Why this matters for switching

Vikunja is open-source under the AGPLv3 and free to self-host, with Vikunja Cloud as a paid managed alternative that includes automatic updates and backups. The import path means you can test either option with your real tasks instead of starting from an empty list — and if you later move between self-hosting and Cloud, your data stays in a tool you control.