Getting a spreadsheet into Trello
Trello can create one card per line from pasted text, but that is all it does natively. Getting descriptions, dates, labels and checklists across needs a Power-Up, and five specific problems catch almost everyone: Excel serial dates, ambiguous date formats, board membership, the absence of undo, and keeping a board in sync afterwards.
Sooner or later somebody hands you a backlog in Excel, a Jira export, or a CSV a colleague made, and asks for it as a Trello board. Having done this enough times, here is the collection of ways it goes wrong, and what Trello does and does not do on its own.
What Trello gives you for free
Paste a list of lines into a card and Trello offers to make one card per line. It is genuinely useful and plenty of people do not know it is there.
The limit is that you get bare cards. No descriptions, no due dates, no labels, no members, no checklists, and everything lands in one list. If that is all you need, you can stop reading. You do not need anything else.
1. Excel dates arrive as five digit numbers
A date in Excel is stored as a number counting days from 1899. Export to CSV and 3 September 2026 becomes 46264. Hand that to Trello and you get either a rejected value or a due date somewhere in the 2090s.
Doing it by hand, the fix is to format the column as text in a date format you control before exporting. ISO, so 2026-09-03, is the one format nothing gets wrong.
There is a second trap underneath. Excel believes 1900 was a leap year, so every conversion is a day out before March 1900. That will never matter unless you are importing historical records, but it is exactly the sort of detail that makes you stop trusting an importer once you notice it.
2. Half your dates are ambiguous
Is 3/9/2026 the third of September or the ninth of March? Nothing can tell from the value alone, and different tools guess differently.
If the file is going to be read by somebody else's software, convert to ISO first and the question disappears. If you cannot, make sure whatever you use lets you say which order your dates are in, rather than guessing silently.
3. Members only attach if they are already on the board
Trello will not assign a card to somebody who is not a member of that board. This is Trello's rule, not a limitation of any particular tool, and it catches people every time.
Add the people to the board first, then import. Otherwise the cards arrive unassigned and you end up doing it by hand anyway, which was the thing you were trying to avoid.
4. There is no undo, and re-importing duplicates everything
This is the expensive one. If an import half fails and you run the same file again, every row that worked the first time gets a second card. Now you are deleting cards by hand on a board you were trying to build automatically.
Two habits avoid it. Run five rows first, to check your columns are matched the way you assume. And when something does fail, re-import only the failed rows rather than the whole file.
5. Keeping it up to date is a different problem
Importing once is easy. Keeping a board matched to a file that keeps changing is not, because the second run has to know which card came from which row. Without a stable id per row, nothing can tell an update from a new item, and you get duplicates again.
If you need this, the questions to ask of any tool are: does it stamp each card with the id of its source row, and what does it do when a row disappears? Archiving is recoverable. Deleting is not.
One practical warning if you go down this road. A published Google Sheets link cannot be read by a browser based tool, because Google sends no Access-Control-Allow-Origin header on those URLs. A raw file link from a repository works. That one cost an afternoon to discover.
What we built, and why it is mentioned here
We hit all five of these for a client whose backlog lived in Excel. The options were a morning of copy and paste or a subscription for a tool that solved half of it, so we wrote our own and released it free: Kanban Importer, a Trello Power-Up.
It reads CSV, TSV, Excel, OpenDocument and JSON, maps columns to card fields, shows every card it is about to create before it creates any of them, and hands back failed rows as their own small file. It can also lay out Backlog, Ready, In Progress, In Review and Done on an empty board.
There is no account and no import limit, and the file is parsed in your browser rather than uploaded anywhere.
The five points above stand on their own whether you use it or not, which is why they came first.
What it does not do
It will not push changes from Trello back out to your file, it does not update checklists after a card already exists, and it cannot read the old binary .xls format. Knowing the edges of a tool is more useful than a feature list.
If you want the detail on keeping a board matched to a file, that is written up separately in keeping a board in sync.
Need something like this built around your own workflow? That is custom app development.