Import

Import your collection from a CSV

Bring a collection over from another tracker, or from your own spreadsheet. Mint matches every row against its card database on your device, then shows you exactly what it found before anything is added.

Start with the template

The template is the simplest path: download it, paste your data into the columns, import it. You can also get it inside the app under Profile → Import & export → Download the template.

Download the template CSV

Already have an export from another app? You usually don't need the template at all — see importing from another app.

The columns

Only Card Name is always required, plus enough to identify the printing: a Set Name, a Set Code or a Card Number. Everything else is optional, and any column you leave out falls back to a sensible default. Extra columns Mint doesn't recognise are ignored, so you can leave your own notes in the file.

Importing from another app

You don't have to reformat anything first. Export your collection from the other app and hand Mint that file — it reads the header row and works out which column is which.

Collectr and Dex are recognised by name and read in full, including the things a generic reader would miss: Dex's UTF-16 semicolon files and the card number hidden inside its Id column, and Collectr's Variance finish column and its combined grade cell (PSA 10.0 GEM - MT). Your collections come across too — Collectr's Portfolio Name and Dex's Category both map to Mint collections. Exports from Rare Candy, Pokecardex, Deckbox and most spreadsheets are read by column name instead, which handles the ordinary cases well.

For anything Mint doesn't recognise by name, it shows you a mapping step before importing: every Mint field, the column it guessed for each, and a real value from that column so you can check the guess rather than trust it. Change any that are wrong, set any it missed, and mark the ones you don't want imported. Nothing is read from your file that you haven't confirmed.

Only Card Name is required, plus one of Set Name, Set Code or Card Number so two cards with the same name can be told apart. Everything else is optional.

These are the header names Mint recognises:

• Collection — collection, collection name, portfolio, portfolio name, binder, folder
• Card name — name, card, product name, title, nom
• Set — set, set name, edition, expansion, extension, série
• Set code — set code, set id, expansion code, abbreviation
• Card number — number, num, card no, collector number, numéro
• Variant — variant, variance, printing, finish, foil, holo, parallel
• Condition — condition, cond, quality, état, zustand
• Quantity — quantity, qty, count, amount, copies, nombre, anzahl
• Purchase price — purchase price, price paid, paid, cost, cost basis, buy price
• Grade — grade, psa grade, numeric grade
• Language — language, lang, locale, langue, sprache

A few things Mint does automatically when it reads another app's file:

• Collections are kept. Rows go into the collection they name, and a name you don't have yet is created for you — so Mint never asks which collection to use for a file that already says. Rows that name none, and only those, get a collection you pick in the review step. The split, and how many collections will be created, is shown before you import. Names are matched loosely enough that "Main" and "main" are the same collection rather than two.
• Rows with a quantity of 0 are skipped. Dex writes a line for every printing it has seen you own, including the ones you don't. Those aren't errors and aren't reported as any.
• A purchase price of 0 means "not recorded". Collectr writes 0 for every card you never entered a price for, and storing that as a real €0.00 purchase would report your whole collection as free.
• Conditions are translated, rounding down. Moderately Played, Heavily Played and Damaged have no exact Mint equivalent, so they map to the nearest grade at or below what your file says — never above.
• Only English printings are matched. Mint's card database holds Japanese cards too, and a Japanese set can share a set name and card number with an English one.

Cardmarket and TCGplayer are not supported: their exports are order and transaction histories rather than collection lists, so there is no reliable "what you own right now" in them.

How the import goes

1. Export your collection from the other app as a CSV.
2. In Mint, open Profile → Import & export, or tap the upload icon on your collection.
3. Pick the file. If it came from an app Mint recognises, it goes straight on. Otherwise Mint shows you which of your columns it matched to which field, so you can correct anything it got wrong and fill in what it missed.
4. Mint matches every row against its card database on your device.
5. Review what it found: which collections the cards are going into, cards ready to import, rows that need your input, and rows it can't use.
6. If your file doesn't say which collection a card belongs to, pick one there — or add a new collection. Mint only asks about the rows that need it.
7. Tap any row that needs attention to pick the right card yourself.
8. Import. Anything still unresolved is skipped, never guessed.

Rows that don't match

Mint skips what it can't identify rather than guessing at it — a wrong card in your collection is worse than a missing one. After importing you can download the skipped rows as a CSV, fix the set name or card number in a spreadsheet, and import that file directly.

Exporting

Profile → Import & export → Export my collection writes every holding as a CSV — one row per card, condition and grade, so a graded copy and a raw copy of the same card stay separate. It uses the same seventeen columns as the template, which means your export is also a valid import file: it round-trips without losing anything, your collections included.

Common questions