CSV import and export

Take your items out of buildIt.Social as a CSV file, for a spreadsheet or a report, and bring items in from a spreadsheet or another tool. Exported files use the same format the importer reads, so you can export, edit and import again.

Export#

From a project’s view#

On the Board, Backlog, List or Calendar, open Import and export in the view bar and choose:

• Export CSV: shown columns: the columns the view shows.
• Export CSV: all fields: every field, custom fields included.

The file holds the items the view shows, with its filters and in its order. Exporting works offline.

On the Table, select Export CSV, then Visible columns or All fields.

From the Work hub#

In the Work hub’s Search, select Export CSV to save the results across projects. A search across several projects needs a connection.

What’s in the file#

• Headers and names are in your language. Dates are written as 2026-10-20, and times in UTC.
• With all fields, people are included with their names and emails, so the importer can match them.
• Comment counts and GitHub states aren’t exported: they aren’t fields of the item.

Import#

Project admins can import items into their project from a CSV file. Importing needs a connection and a larger screen: use the desktop app or the web on a computer.

1. Open Import and export in a project’s view and choose Import from CSV….
2. Follow the five steps: File, Columns, Values, Check and Import.

1. File#

Choose a CSV file exported from a spreadsheet, Jira, Trello or Asana, and say which under Exported from so the importer can suggest the right fields. The file must be:

• UTF-8 text (in a spreadsheet, save it as “CSV UTF-8”), with commas or semicolons between values;
• at most 5 MB, 5,000 rows and 1,000 columns. Split bigger files into smaller ones.

Pick the file’s Date format: the dialog shows how a value from your file reads.

2. Columns#

Choose the field each column fills, or Skip to leave it out. Only the title is required.

• Parent: a column can name each row’s parent, by the parent’s title or by its external id. Parents can be rows in the same file or items already in the project.
• External id: keep another tool’s ids in a custom field with Keep external ids in, to find items later.

3. Values#

Choose what each type, status and priority in the file means in this project. A status the item’s workflow doesn’t have starts the item in its type’s first status.

Then decide about names the project doesn’t have yet: Add new labels, Add new releases, Add new sprints (as planned sprints), and new options for option fields. When a box is off, rows that name a missing one are skipped.

4. Check#

The server checks every row without importing anything. It tells you how many rows are ready, how many will be skipped and how many have warnings, and lists the rows to look at with the reason for each. For example:

• a person who isn’t a member, or isn’t in the channel, is left empty (a reporter who isn’t a member becomes you);
• a sprint that’s already completed, or a field the project doesn’t use, such as estimates, is left out.

Fix the file and select Check again, or go on.

5. Import#

Select Import. Rows are added in the file’s order, so items get their numbers in that order. You can Stop at any time; the batch being sent finishes first.

The result says how many items were imported and skipped. Select Download skipped rows to get a CSV of the rows that weren’t imported, with the reason for each. If an import stops partway, Import the other N rows picks up where it left off, and rows that were already imported aren’t added again.