Moving in: bring your Jira, Linear and Asana boards, and your Toggl hours

Import projects from Jira, Linear, Asana and any CSV, and time entries from Toggl, Clockify and Harvest. With a preview before anything is written, and six new comparison pages that also say when you should stay where you are.

The worst feature of any new tool is the old tool: four years of cards and a few thousand hours live there, and nobody is going to retype them. Until now devbord could only take over a Trello board. That list just got longer.

Projects from Jira, Linear, Asana and CSV

Choose Import project on the home page, drop the export file, and devbord works out by itself which tool it came from.

- **Jira** (CSV export, all fields): statuses become lists, subtasks become a checklist, epics become a label, and SHOP-12 becomes card 12.
- **Linear** (CSV export): statuses become lists, sub-issues become a checklist, projects become a label, and ENG-12 becomes card 12.
- **Asana** (CSV or JSON): sections become lists, subtasks become a checklist, tags become labels, and your custom fields come along.
- **Any other CSV**, from a spreadsheet or a tool we have never heard of: one row per card, and you tell us which column is the title, the list, the due date and so on. Columns that are left over can come along as custom fields.
- **Trello** still works as before.

Cards keep their numbers, so the SHOP-12 in an old commit message or a three-year-old chat thread still points at the right card.

Before anything is written you get a preview: how many lists, cards and labels, and which people the file mentions. You match those people to members of your workspace yourself. Somebody who is not in the workspace yet cannot be picked, so invite the team first and import second.

Hours from Toggl, Clockify and Harvest

Time tracking has the same problem with more decimals. Under Time › Reports you can now import the detailed report from **Toggl Track**, **Clockify** or **Harvest**, or a CSV of your own.

- Start, end, project, client, tags and who did the work come along.
- Durations are read the way exports write them: `1:30:00`, `1.5`, `1,5`, `1h 30m` or `90m`.
- A date like `03/04/2026` is read the way the rest of the column suggests, so April does not quietly become March.
- Importing the same file twice does not double your hours. What came in before is skipped.
- If the file holds hours of several people, you import your own. Whoever manages time tracking can import them for the whole team.

Honest comparison pages

We also wrote down how devbord compares to the tools people usually come from, with a table per tool:

- [Jira](https://devbord.com/jira-alternative)
- [Asana](https://devbord.com/asana-alternative)
- [ClickUp](https://devbord.com/clickup-alternative)
- [Toggl](https://devbord.com/toggl-alternative)
- [Harvest](https://devbord.com/harvest-alternative)
- [Statuspage](https://devbord.com/statuspage-alternative)

Each page has a list of reasons to pick devbord and, right next to it, a list of reasons to pick the other one. If you run hundreds of people on custom Jira workflows, the Jira page will tell you to stay. We would rather lose that argument on our own website than in your second month.

The door works both ways

Importing is only half of trusting a tool. Every project and every workspace can still be exported in full, whenever you like. We just hope you will not need it.

devbord · Pricing: one flat price per team · News · API documentation · Support: help and contact · Privacy: what we can and cannot see · Terms of service · Privacy policy · Error tracking for dev teams, Sentry-compatible · Time tracking and invoicing for dev teams · Status pages with uptime monitoring and incidents · Changelog and release notes from done cards · Incident management and on-call for dev teams · Release management, test runs and DORA metrics for dev teams · Meeting agendas, async stand-ups and retros for dev teams · A feedback portal with voting and a public roadmap · Automation, a REST API, webhooks and an MCP server for dev teams · Sprint planning with burndown, a roadmap and OKRs · A Trello alternative for dev teams · A Sentry alternative that keeps your SDKs · A Linear alternative with error and time tracking · A Jira alternative for small dev teams · An Asana alternative for software teams · A ClickUp alternative with error tracking and invoicing · A Toggl alternative with a board and invoicing · A Harvest alternative with a kanban board · A Statuspage alternative with monitoring built in