Import troubleshooting
When the wizard skips rows or flags errors, here’s what the messages mean and how to resolve them. Most of the time it’s a fixable issue with the source spreadsheet, not a bug in the importer.
How import works
- Upload — CSV or XLSX file, up to a few MB. We auto-detect the format (Card Ladder, Collectr, generic) and pre-fill column mappings when we recognize the headers.
- Map — you confirm which spreadsheet column maps to which card field. Unrecognized columns can be skipped.
- Validate — we run every row through the planner and surface any issues. Rows with errors are flagged but not yet committed.
- Commit — you review and confirm. Rows you choose to skip and rows the planner couldn’t plan are excluded. Everything else lands in your binder atomically — either the whole batch saves or none of it does.
- Roll back — if you realize the file was wrong, the result page has a one-click rollback that removes everything from the same batch. Use within a few hours of import for the cleanest experience.
Common errors and how to fix them
grading_company "XXX" not in schema enumThe row has a cert number but the grader name isn’t one we recognize. We accept PSA, BGS, SGC, CGC, CSG, TAG. Common fix: a misspelling (“Beckett” instead of “BGS”) or a defunct grader name. Update the grading column in your spreadsheet, or unmap the column if the cards are actually raw.
grading_company mismatch: condition="X" vs column="Y"Two columns are telling us different graders — usually a free-text condition column (e.g. “PSA 10”) and an explicit grading-company column (e.g. “BGS”). Pick one source of truth in your spreadsheet and unmap the other.
cert ... also appears in row NTwo rows in the same import file have the same cert number under the same grader. Cert numbers are unique per grader globally, so we keep the first row and reject the duplicate. If both rows are real, double-check that you didn’t accidentally duplicate a row in the spreadsheet.
cert ... is already registered to another userThat cert is already in another user’s binder on CardboardChasr. If you bought the slab and the previous owner imported it before you, that’s the cause. Contact support and we’ll transfer ownership after verifying.
card_sold=true but sales_date or sales_amount missingYou marked a row as sold but didn’t map a sale date and a sale amount. Either fill those columns in your spreadsheet, or unmap the “sold” column and import the card as still-owned (you can sell it from the binder later).
year out of range / invalid yearWe accept years from 1900 to 2100. If your spreadsheet has a column like “Year of release” with values like “2024–25” or “2024 Topps”, we can’t parse those reliably. Clean to a 4-digit year per row.
missing required fieldEvery card needs at least a player or a brand/set so we can index it. If you have a row with neither, fill one in or skip the row in the wizard’s preview step.
Supported file formats
- Card Ladder export — auto-detected. Columns map cleanly. The most common case for portfolios with grades and sales history.
- Collectr export — auto-detected. Most users only need to confirm the mapping.
- Generic CSV / XLSX — works as long as your file has a header row and one card per row. Map columns manually in step 2.
- Multi-card cells — if a single row represents multiple players (dual autos, jersey relics with two subjects), separate names with comma, slash, or semicolon: e.g.
Mahomes / Mariota.
We don’t currently support image columns or grader-PDF uploads in the import path. Add those after the cards land via the card edit page.
Still stuck?
If your file fails repeatedly and the errors don’t map to anything above, send us a sample (you can redact sensitive columns) and we’ll either fix the parser or tell you exactly what to change. Faster for everyone than guessing.
Email: knation@gmail.com · Subject line: “Import help — [your filename]”