CSV Import Guide
Upload Your Collection to CardNexus
Written By Gaultier Romon
Last updated 4 months ago
Our CSV importer makes it easy to upload your entire trading card collection from any spreadsheet or existing collection management platform. Whether you have 10 cards or 10,000, you can import them all at once.
What is the CSV Importer?
The CSV importer is a powerful tool that:
Accepts any CSV file - No matter where your data comes from
Automatically detects columns - Smart recognition of your column headers
Validates your data - Checks every card to ensure accuracy
Fixes errors easily - Simple interface to correct any issues
Works for all games - Magic: The Gathering, Pokemon, Lorcana, Sorcery: Contested Realms, One Piece and much more to come.
Step-by-Step Import Process
Step 1: Prepare Your CSV File
Create a CSV file with your collection data. You can use Excel, Google Sheets, or any spreadsheet program. If you already have one from your current collection manager / deckbuilder this is even better. Your file should have columns for the card information.
Step 2: Upload Your File
Click the Upload CSV button and select your file. CardNexus accepts files up to 10MB.
Step 3: Map Your Columns
CardNexus will try to automatically match your columns. If needed, you can manually select which column contains which information.
You can also override the values from your CSV if they are wrong : Example : you got Light Played as condition but we support LP or Lightly Played
On top of that, if you are missing some columns in your CSV because you did not take the time to put condition or language for example, or if your collection manager did not support those you can set a default value for all the rows inside of those columns.
Step 4: Review and Fix Errors
If any cards couldn't be matched, you'll see them listed with the issue. You can fix them individually by handpicking the proper printing of the card inside of the quick search dialog that would be populated with the game, the name of the card as search and its expansion, this way you should not have like 100 results.
This gets around trying to find the proper version of your Island in Magic: The Gathering which has to this date more than 700+ printings, trust me, we have been there.
In case you have too many errors to be fixed individually, you can always download the error file so you correct in bulk all of your data on Excel or Google Sheets.
Step 5: Confirm Import
Once everything looks good, click "Import to Inventory" or “import to list” to add the cards to your list or inventory.
Understanding the Required Fields
CardNexus needs specific information about each card to add it to your inventory. Here's what each field means:
Card Identification (at least one required)
You must provide either the Card Name OR the Print Number (or both):
Print Number: The collector number on the card
Example: "#25" (for Pikachu)
Tip: This is the preferred attribute to be given as it is 100% accurate since it is unique per printing of a card.
Card Name: The name of the card
Example: "Lightning Bolt"
Example: "Charizard"
Tip: If multiple versions exist, use the print number instead, because nowadays publishers are releasing many cards with the same name in the same expansion.
Set/Expansion (required)
The set or expansion the card is from:
Can be the full name: "Limited Alpha Edition"
Or the set code: "LEA"
CardNexus recognizes many variations automatically
Quantity (required)
How many copies you have:
Must be a whole number (1, 2, 3, etc.)
Cannot be zero or negative
No decimals (not 1.5 or 2.25)
Condition (required)
The physical condition of your cards. CardNexus accepts both US and European grading:
US Grading System:
NM (Near Mint) - Perfect or nearly perfect
LP (Lightly Played) - Minor wear, still tournament legal
MP (Moderately Played) - Noticeable wear but playable
HP (Heavily Played) - Major wear, still readable
DMG (Damaged) - Severe damage
European Grading System:
NM (Near Mint) - Perfect or nearly perfect
EX (Excellent) - Slight wear on edges
GD (Good) - Clear play wear
PL (Played) - Heavy play wear
PO (Poor) - Very heavy wear
You can also write out the full names like "Near Mint" or "Lightly Played".
Finish (required)
The surface treatment of the card. This varies by game:
Standard (also accepts: non-foil, normal, regular)
Foil (also accepts: holo, holographic, shiny, premium)
Game-specific finishes (see game guides below)
Language (required)
What language the card is printed in:
Full names: "English", "French", "German", "Spanish", "Italian", "Japanese"
Or codes: "EN", "FR", "DE", "ES", "IT", "JA"
Not case-sensitive (en, EN, En all work)
Optional: Variant
Some games have variants like "First Edition" or special printings. This field is optional and game-specific.
Column Mapping Made Easy
CardNexus automatically recognizes common column names. For example:
"Card Name", "Name", "Card" → Maps to Card Name
"Set", "Expansion", "Edition" → Maps to Expansion
"Qty", "Quantity", "Count" → Maps to Quantity
"Condition", "Grade", "Quality" → Maps to Condition
If your columns aren't recognized, you can manually select them from the dropdown.
Using Overrides
Want to set the same value for all cards? Use the override feature:
Set all cards to "Near Mint" condition
Set all cards to "English" language
Set all cards to "Standard" finish
Fixing Import Errors
Sometimes cards can't be matched automatically. Here are the most common issues and how to fix them:
"Card not found"
Problem: The card name doesn't match our database Solution:
Check the spelling carefully
Try using the print number instead
Make sure you've selected the right game
"Invalid expansion"
Problem: The set name or code isn't recognized, or you might be trying to import cards from a Pokémon in a Magic: The Gathering import. Solution:
Try the set code instead of the full name
Check for typos
Some promotional sets have specific codes
"Multiple cards found"
Problem: The name matches several different cards Solution:
Use the print number to specify exactly which version
Add more details if available
"Language not available"
Problem: That card doesn't exist in the specified language Solution:
Check if the card was printed in that language
Some promos are English-only
"Duplicate entry"
Problem: The same card appears twice in your CSV Solution:
Combine the quantities into one row
Remove the duplicate row
Download Templates
Complete Template
All possible fields including optional ones
CardName,PrintNumber,Expansion,Condition,Finish,Quantity,Language
Lotus Field,68,Edge of Eternities: Stellar Sights,Heavily Played,Standard,3,enSee the example spreadsheet
Troubleshooting Guide
CSV Formatting Issues
File won't upload?
Make sure it's a .csv file (not .xlsx or .xls)
Check the file size (max 10MB)
Try saving as "CSV UTF-8" in Excel
Special characters showing incorrectly?
Save your file with UTF-8 encoding
In Excel: Save As → CSV UTF-8
In Google Sheets: Download as CSV
Columns not separating properly?
Ensure you're using commas to separate values
Some regions use semicolons - convert to commas
Check for commas in card names (should be in quotes)
Data Issues
Card names with special characters:
Accented letters (é, ñ, ü) are supported
Apostrophes in names like "Urza's Saga" work fine
Put names with commas in quotes: "Sword of Fire and Ice, Masterpiece"
Expansion name variations:
Try both full name and set code
Check official set names (some differ from common usage)
Promotional sets often have specific codes
Tips for Success
Use print numbers: More accurate than names alone (some game do not have one, in this case use name + variant)
Check your data: Review the preview before importing
We save your work: Even after having successfully imported your card they still will not be in your inventory, you will need to commit the import. So you can always delete the import and start fresh.
Ask for help: Contact support if you get stuck
Game-Specific Guides
Each game has unique features and formats. Check the game-specific guides to see the complete examples for your favorite game.
Need More Help?
Contact support: support@cardnexus.com
Community Discord: Join for tips from other users