# Move to Kanera: Trello, CSV, and Assisted Migration > Bring project data into Kanera with a reviewable Trello import, CSV mapping, a Kanera board archive, or a scoped migration. Export any board back out as JSON or Excel. Canonical page: https://www.kanera.app/migration Move to Kanera # Change platforms without starting over. Import one real board, check every mapping before a single card is created, and move the rest of the team once the pilot has earned it. [Import from Trello](https://www.kanera.app/trello-migration) Plan a migration Trello Jira Asana Notion monday.com Boards Lists Cards Members Custom fields Attachments Kanera All your data, intact Bring boards, cards, members, fields, comments, and attachments into one Kanera workspace. You review before import One-time copy, no sync Source stays untouched Export back out any time ## Four ways in. Pick the one that fits. Trello JSON, CSV, and Kanera board archives ship in the product. For platform-specific history, files, or structures that do not fit those routes, plan an assisted move. In the product ### Trello board import Upload one board’s JSON export. Kanera reads it and hands you the mapping: which lists to create, reuse, or skip, which labels and fields to match, and who each Trello member is here. Cards, descriptions, due dates, checklists, comments, field values, and attachment links come across. Connect Trello during review and uploaded files are copied too. Workspace settings → Import [The Trello route in detail](https://www.kanera.app/trello-migration) In the product ### CSV card import Bring an export from Jira, Asana, a spreadsheet, or any system that can produce CSV. Kanera detects the layout, then lets you decide what every column means. Map repeated columns, multi-value cells, dates, lists, labels, people, comments, checklists, and typed custom fields. Group repeated rows into one card with a source ID. Workspace settings → Import [The CSV import guide](https://www.kanera.app/docs/csv-import) In the product ### Kanera board archive Export any board to JSON from its own toolbar, then import that archive into another workspace — or another Kanera install entirely. This is the route between Kanera Cloud and your own server, in either direction. The same mapping review runs before anything is written. Workspace settings → Import [Self-hosting Kanera](https://www.kanera.app/docs/self-host) With our help ### Everything else For data that does not fit a board archive or useful CSV — including history, attachments, or platform-specific structure — we plan the move with you. We read the source structure, agree what maps cleanly and what needs separate treatment, then script the remaining move against Kanera’s REST API. For company evaluations [The REST API](https://www.kanera.app/docs/api) Still deciding whether to move? Read the case tool by tool: [Trello alternative](https://www.kanera.app/trello-alternative), [ClickUp alternative](https://www.kanera.app/clickup-alternative), [Linear alternative](https://www.kanera.app/linear-alternative), [Jira alternative](https://www.kanera.app/jira-alternative), [Asana alternative](https://www.kanera.app/asana-alternative), [Notion alternative](https://www.kanera.app/notion-alternative), [monday.com alternative](https://www.kanera.app/monday-alternative), [Wrike alternative](https://www.kanera.app/wrike-alternative), [PLANKA alternative](https://www.kanera.app/planka-alternative), [Focalboard alternative](https://www.kanera.app/focalboard-alternative), [Wekan alternative](https://www.kanera.app/wekan-alternative), and [self-hosted Trello alternative](https://www.kanera.app/self-hosted-trello-alternative). How an import runs ## Nothing is created until you confirm. Every built-in importer follows this review-first sequence. Kanera analyses the export and writes nothing while you work through the decisions. - 1 ### Upload and analyse Kanera reads the export and reports what is in it. For CSV, it also detects the encoding and delimiter and previews every source column. - 2 ### Map the structure Map CSV columns when needed, then decide whether each list, label, and custom field should be created, reused, or skipped. Incompatible field types are never guessed. - 3 ### Match the people Map each source assignee to someone with access here, or leave them unmapped. CSV comments are attributed to the person running the import. - 4 ### Review, then confirm A summary shows the board options, skipped cards, data issues, and every mapping. Only confirming creates data. ## Test the move before the rollout. Start with one real project. The current system stays exactly where it is while the team checks the structure, the imported data, permissions, and an ordinary working day. Under 30 minutes to prepare and review a standard Trello board. Larger moves start with one representative board so the structure and field mapping are settled before the rest follows. ### What carries over? CSV carries cards, descriptions, dates, lists, labels, mapped assignees, comments, checklist items, and custom-field values. Trello JSON also preserves attachment links and can copy uploaded files. ### What if something does not map? You decide per column and per destination item: import it, create it, map it onto something existing, or skip it. The review reports rows and values that cannot be imported. ### Who verifies the result? Someone who knows the current workflow and the people in it. They review the mappings before the import and validate the board afterwards, then decide what moves next. No lock-in ## And the way out is a button. A migration promise is worth very little if leaving means raising a support ticket. Every board carries its own Export control, and you never need us to use it. ### Export → JSON The complete board archive: lists, labels, custom fields and their options, cards, assignees, checklists and items, comments, reactions, watchers, and attachments. ### Export → Excel A workbook of the board. Table view exports too, so a filtered, grouped, totalled report leaves as Excel or JSON. ### Run it yourself The same product self-hosts with Docker Compose, source-available under Elastic License 2.0, with no Kanera per-seat fee. ## Moving a team, not just a board? For suitable company evaluations we will go through your current setup, pick the workflow worth piloting, and prepare the first Kanera workspace with you. Plan a migration - Which boards should become workspaces, and which should stay standalone - List, status, and custom-field mapping agreed before the first import - Member, guest, and board-permission planning - A representative pilot import you review together - A rollout order, and how each step gets verified - Scoped custom migration development where no importer exists ## Migration questions Which platforms can Kanera import from today? Three import routes ship in the product: Trello board JSON, general CSV, and Kanera board JSON. Each runs a reviewable mapping flow from Workspace settings, under Import. Trello has the richest source-specific path, including attachment links and optional file copying. CSV works with Jira, Asana, spreadsheets, and other exports when the data fits rows and columns. Can I move a board between Kanera Cloud and a self-hosted install? Yes, in either direction. Export the board to JSON from its toolbar, then import that archive from Workspace settings on the destination install. The archive carries lists, labels, custom fields and their options, cards, assignees, checklists and their items, comments, reactions, watchers, and attachments. Does an import change the system we are moving from? No. Kanera reads an export file you supply. It never writes back to the source, and the original board is left exactly as it was. An import is a one-time copy rather than a live sync, so changes made in the source system afterwards are not reflected in Kanera. How long does a migration take? A standard Trello board can usually be prepared and reviewed in under 30 minutes. The import itself depends on card volume, history, and whether attachments are being copied. For a wider move, plan around one representative board first. Confirm the structure, the field mapping, and permissions before the rest follows. Can we run Kanera alongside our current system? Yes, and for a first evaluation it is the safest order. Import one representative project, run it in parallel, and keep the current tool in place until the team has judged the result on real work. How do we get our data back out of Kanera? From any board, use Export in the board toolbar. JSON produces the complete board archive; Excel produces a workbook for reporting and finance. Table view exports a filtered, grouped report to Excel or JSON. The REST API covers workspaces, boards, lists, cards, labels, custom fields, comments, attachments, and notes, and Kanera is source-available under Elastic License 2.0 if you would rather run it yourself. Can you help us move a whole team, not just one board? For suitable company evaluations, yes. We help choose the pilot board, decide which boards should become workspaces, plan list, status, and custom-field mapping, plan member and guest access, and agree how the result gets verified before the rollout continues. ## Bring one board over and judge it on real work. Start with the complete product for 30 days. No card required. [Start free](https://board.kanera.app/signup)[See the Trello import](https://www.kanera.app/trello-migration) No card required, 30-day Pro trial, free plan available after it ## Machine-readable resources - [Kanera AI index](https://www.kanera.app/llms.txt) - [Kanera documentation index](https://www.kanera.app/docs/llms.txt) - [Agent discovery guidance](https://www.kanera.app/agents.md)