Importing and Exporting Boards

Overview

Every board can be taken out of Yaplet in four different file formats, and boards can be brought in from Trello, from any spreadsheet, or from a Yaplet backup file. Which format you want depends entirely on what you're doing with it afterwards.

Exporting

What you can export

You can export at three different sizes, each from the place it belongs:

All three live on a board — there is no separate boards page any more. Exports are deliberately per board: a file holds exactly one board, and importing it restores exactly that board.

Choosing a format

Trello JSON is only offered when a whole board is selected, because a Trello file is a board — there's no such thing as a Trello file holding a single card. The CSV carries a comment count rather than the comment text, because multi-paragraph cells break most spreadsheets and importers; use Trello JSON or Markdown if you need the comments themselves.

What goes into the file

By default an export contains the title, description, status, priority, labels, dates, assignee, comments, upvote count, and the customer's form answers. That default is deliberately safe to share and small enough to paste into an AI assistant.

Two checkboxes add more:

• Customer details — the name, email and country of whoever reported each ticket. This makes the file a personal data export, so handle it accordingly. Only organisation owners can tick this.
• Technical logs — the console, network and event logs captured with bug reports. These are typically around 16 times larger than the ticket text itself, so a file with logs is far bigger and much less useful for an AI assistant.

Copy for AI

Next to each export option there's Copy for AI, which puts the same readable Markdown straight on your clipboard instead of downloading a file — ready to paste into ChatGPT. It's available for a single ticket, a column, or a whole board.

Copy for AI never includes customer details or technical logs, regardless of the export checkboxes. It's the "paste this somewhere else" path, so it always produces the safe, compact version.

Importing

What you can bring in

• Trello JSON — the file from a Trello board's menu: Share, print and export → Export as JSON
• Any CSV — from Jira, Canny, Featurebase, Asana, GitHub, or made by hand
• A Yaplet backup — restored exactly as it was

Yaplet works out which of the three you've given it from the file itself, so you don't have to say.

Import happens in two steps

A board created by an import is always of type Custom. If you imported a public roadmap, change its type on the new board's Settings tab before you try to share it.

Matching spreadsheet columns

A CSV gets an extra step where you match its columns to Yaplet's fields. Yaplet guesses these from the column names first — a Canny export's "Details" becomes the description, its "Score" becomes upvotes — and you only correct what it got wrong.

There are also starting points for the most common sources: Jira, Linear, Trello CSV, Canny and Featurebase. Any column that isn't matched to anything is listed in the preview so you know it's being ignored rather than silently dropped.

Limits

A file over any of these is refused up front in the preview rather than imported halfway. Split larger migrations into several files.

What doesn't come across

Every import preview lists these for your specific file, but in general:

• Upvotes are not recreated. Each vote in Yaplet belongs to a real person we email when a ticket's status changes, so votes are never invented. Imported tickets start at zero.
• Due dates and custom fields have nowhere to live in a Yaplet ticket and are dropped.
• Checklists are kept, but folded into the ticket description as text.
• Attachment links are kept in the description; the files themselves are not copied across.
• Comments are attributed to whoever ran the import, with the original author's name preserved at the start of each message — the people who wrote them have no Yaplet account.

Common moves

• Coming from Trello — export the board as JSON from Trello, then open any board, use the two-arrow menu → Import into this board…, and choose A new board as the destination in the dialog. Lists become columns, cards become tickets, and labels come across with their colours intact.
• Coming from Canny or Featurebase — export their CSV, upload it, and pick the matching preset in the column-matching step.
• Moving to another tool — export the board as Trello JSON and import that into Linear, Planka, Wekan or Breeze.
• Working with an AI assistant — use Copy for AI on the board and paste it straight into the chat.
• Reusing a board setup — use Duplicate this board in the same two-arrow menu rather than exporting and re-importing. It needs the Board management right, and the entry is not hidden without it, so a colleague with only the Tickets right gets an error message.

For what a board is and where to create one, see Boards. For labels and the board toolbar, see Board View.