Import From CSV

Boarbs does not currently expose a self-serve CSV importer inside the settings area.

If you are migrating from another tool today, the reliable approach is to prepare the data first and then import it through your own workflow with the API or CLI.

Start by Cleaning the Source Data

Before you import anything, decide what is actually worth moving over.

Usually you should:

• remove obvious duplicates
• archive stale requests you do not plan to act on
• normalize status names
• decide which requests belong on public boards and which should stay internal

Migrating less usually gives you a better system.

Decide the Target Structure First

Before you touch the import itself, set up:

• your boards
• your default statuses
• your shared tags
• your roadmap strategy

Importing into a half-defined workspace usually creates cleanup work you could have avoided.

Recommended CSV Columns

A practical source sheet often includes:

• title
• description
• board
• status
• tag or tags
• requester email
• created date
• ETA, if you already trust it

You do not need a perfect export to get started. You do need consistent columns.

Choose the Right Import Path

Use a manual import when:

• you only have a small number of requests
• the old data is messy
• you want to rewrite titles and descriptions while migrating

Use an API or CLI workflow when:

• you have a larger migration
• your data is already structured
• you want repeatable imports
• you need to assign tags or statuses programmatically

A Safe Migration Sequence

A practical sequence looks like this:

1. create the target boards in Boarbs
2. define statuses and tags
3. import into a private board first if you need review time
4. check titles, statuses, and tags
5. move only the right requests into public workflows

This protects the public portal from messy first-pass data.

What to Be Careful About

• do not import every stale request just because it exists
• do not copy old status names that no longer fit your workflow
• do not expose internal-only imports on a public board before review
• do not assume old categories should become boards

If You Need Ongoing Syncs

If feedback keeps coming from another system, use the API or CLI as the source of truth for migration logic instead of hoping for a one-time CSV cleanup forever.

That gives you a maintainable path instead of repeated manual imports.

Next Steps

• Create Boards — Build the destination structure before importing
• Tag New Submissions — Decide how imported feedback should be labeled
• API — Understand which import-friendly endpoints live in the explorer and which workflows do not
• CLI — Use scripted workflows for larger migrations