Treat every row as one card

A bulk import works best when each source row represents one independent task or record. Put the concise task name in one column, supporting context in another, and the workflow stage in a dedicated list column.

If one row contains several tasks, split it before importing. Trello cards are easier to assign, move, and complete when each card has one clear outcome.

Normalize list names and text

Choose the exact Trello list names before the import. Replace abbreviations and spelling variations so the source uses one value for each destination.

Uncontrolled valuesNormalized value
todo, To-do, not startedTo Do
doing, active, underwayIn Progress
complete, shipped, closedDone

Run a controlled test import

  1. Create a temporary Trello board with the intended list structure.
  2. Copy five varied rows into a separate CSV.
  3. Map the title, description, and list columns in JSON/CSV Importer.
  4. Preview the records and run the small import.
  5. Correct the source and mapping before using the complete file.
Avoid duplicate bulk imports

Keep a dated copy of the source file and record which rows were imported. If a run fails, identify the completed records before retrying the entire file.

Verify quality, not only quantity

A matching card count is necessary, but it is not the entire check. Open cards with long descriptions, empty optional values, punctuation, and non-English characters. Confirm those values survived the spreadsheet export and field mapping.

Turn rows into Trello cards.

Use the dedicated CSV and JSON import workflow instead of rebuilding the backlog manually.

Explore JSON/CSV Importer