Skip to content

CSV import/export

CardBoard moves card data to and from CSV files. This page answers: what columns are supported, what’s preserved, and what’s lost.

  • Board content — the cards, stickers, boundaries, groups, and connections on a single board. This is the import/export you use to bulk-edit a board.
  • Workspace report — a list of every board in the workspace (metadata only, not card content), delivered asynchronously by email.

A row’s kind column says what it is:

kindRow represents
nameBoard metadata (map name, map type, snap-to-grid)
card (or blank)A card
boundary (or divider, legacy)A boundary: x, y, orientation, length, locked. The row’s name is the name of the boundary’s outcome.
card_group (or journey, legacy)A journey: name is the journey’s name, and description lists its cards’ id values, comma-separated
card_connectionA connection: description holds the two id values it runs between, from first to second; name is its label
stickerA text or image sticker (x, y, text, font size, color, rotation, size, image URL, locked)

Exports write boundary and card_group. Imports still accept the older divider and journey spellings, so files exported before the rename keep working.

Card fields on import: id, name (max 255 chars; longer titles truncate), description, color (color name), x, y, size, status, shape, width, height, acceptance criteria, card type, and parent card id.

card_group and card_connection rows point at cards by the id column of the card rows in the same file. Put those card rows above the rows that reference them. A group row that names an id the importer hasn’t seen yet fails, and the import reports that a card for the group couldn’t be found.

The ids only link rows inside the file. On import, every card gets a new id.

Exporting then re-importing is not perfectly lossless. The CSV does not carry:

  • Reactions
  • Comments
  • Tracker links (use the tracker’s own bulk import/export instead)

An export writes a card_group row for every group on the board, outcomes included. On re-import, each outcome comes back from its boundary row, and its card_group row adds a journey with the same name and cards. Delete those duplicate journeys from the Groups drawer, or remove the rows before importing.

UUID, Name, Board type, Creator, Organization, Collaborators, Viewers, Cards, Created At, Last View, Last Modification.