Skip to main content

Migrate from Trello

Keep your boards. Gain a client portal.

Each Trello board becomes a Mishka project attached to a client: lists converted to statuses, cards to tasks, due dates kept. Included from Solo.

What is imported

  • Each board → one project (name, description)
  • Each list → one Mishka status, mapping suggested then adjusted by you
  • Each card → one task (name, description, due date)
  • Link to the original card, at the end of the description
  • Only open (non-archived) boards, lists and cards

What is not

  • Members and assignees: the Trello API does not expose emails
  • Labels, checklists, attachments, comments
  • Custom fields and Power-Ups
  • Butler automations
  • Card order and priority (all tasks arrive with normal priority)

In four steps

  1. 1

    Create a Trello API key

    On trello.com/power-ups/admin, in two minutes, no development. The assistant takes you there.

  2. 2

    Authorize read access

    The assistant generates a read-only authorization link, valid for 24 hours. Paste the token you get.

  3. 3

    Pick the boards and the client

    Tick the boards to bring over, choose the client they belong to, then adjust the lists → statuses mapping.

  4. 4

    Review and import

    Summary of projects and tasks, detailed warnings. The token is deleted as soon as the fetch ends.

usemishka.com/import
Mishka import assistant, status mapping
usemishka.com/import
Mishka import assistant, result

What you get on top

What the source tool does not offer, according to its official pages.

  • One space per client, outside your board, with deliverable approvals

  • No billed guests, whatever the number of projects

  • Editorial calendar and PDF reports in your colours

  • Credential vault and native multi-client

Official pages consulted on September 2, 2026. trello.com1 · support.atlassian.com2 · support.atlassian.com3 · support.atlassian.com4

Frequently asked questions

Are my Trello members matched?

No. The Trello API does not expose member emails, so tasks arrive unassigned. You assign them afterwards in Mishka, per task or in bulk from the kanban.

Does a client with several boards become several projects?

Yes: each ticked board becomes a separate project, all attached to the chosen client. You can run the assistant again for another client with other boards.

What happens to attachments and comments?

They are not imported, whatever the source. The assistant brings over projects and tasks (name, description, status, due date, priority, assignee) and appends a link to the original item at the end of the description: you can open the source card, task or page in one click as long as the source tool stays open.

Can I re-run or undo an import?

An import cannot be undone: the projects and tasks it created are deleted like any other project. Re-running it on the same data creates duplicates; the assistant warns you when these data have already been imported, the decision is yours.

Are my keys and tokens kept?

No. They are encrypted (AES-256-GCM) while data is fetched, then deleted as soon as the fetch ends, successful or not. Mishka never changes anything in the source tool.

Migrate from another sourceAsanaNotionCSV

Try it with a real board.

Free plan without a credit card, import included from Solo with a 14-day trial. Client portal from Solo.