Your data
Import
A board that starts empty stays empty. If you already keep requests somewhere, a spreadsheet, a doc or another feedback tool, bring them in on day one. Open Requests in the dashboard and choose Import a list.
A plain list
Paste one request per line. Each line becomes a request in New, with the line as its title and its description. Edit the descriptions later, on the requests that turn out to matter.
Dark mode
Bulk export to a spreadsheet
Slack alerts for new invoicesA CSV export
Paste the export from the tool you are leaving, header row included. CatchLoop reads it as a table when the first row names a title column, and keeps what it recognises:
| Column | Header names read | What it becomes | |
|---|---|---|---|
| Title | title, request, subject, name | required | The request's title. |
| Description | body, description, details | optional | Its description. Without one, the title is used. |
| Votes | votes, score, upvotes | optional | Imported votes, added to the public count. |
| Date | created, date, posted | optional | When it was first asked. A date in the future is ignored. |
| Status | status, state, stage | optional | Mapped to the five statuses: "under review" becomes New, "completed" becomes Shipped, "won't do" becomes Not planned. Anything unknown stays New. |
Commas, semicolons and tabs all work, and quoted fields may contain line breaks. Other columns are ignored.
After the import
- Votes. Imported votes count in the public number on the board. The dashboard shows them apart from the votes of your customers' accounts, since nobody on your portal cast them.
- No emails. Importing sends nothing to anyone.
- No matching. Every row becomes a new request, and nothing is compared with what the board already holds. A list pasted twice is imported twice.
An AI agent can do the same through the MCP server, up to fifty requests per call.