Importing tickets from a spreadsheet
Moving to KAMI Tasks from another tool — or from a planning spreadsheet — doesn't mean retyping the backlog. The import takes a spreadsheet and turns its rows into tickets.
Where: Settings › Import
How it works
Prepare your file as .xlsx or .csv, upload it on the Import page, and the rows become tickets in your chosen project.
Coming from another tool, the usual route is: export from the old system to a spreadsheet, reshape the columns to match, import here. Titles, descriptions, types and priorities carry across; history and comments from the old tool generally stay behind — the ticket starts its KAMI life with its content, not its baggage.
An alternative when you have a brief, not a backlog
If what you actually have is a project brief rather than rows of tickets, KAMI PM can draft the plan for you — upload the brief and let it propose the tickets, or download its import template (XLSX/XLS/CSV), fill it in, and import the finished plan. Same destination, different starting material.
Rules and things to watch
- Import into a test project first if the file is large. Checking twenty tickets landed right beats discovering four hundred didn't.
- Clean the spreadsheet before, not after. Every vague row becomes a vague ticket; the import is faithful, not clever. Ticket Standards and its one-click AI fixes can rescue titles afterwards, but starting clean is cheaper.