How to Import and Export Your Magic Collection (Deckbox, Moxfield, MTGGoldfish, CSV)

You don’t have one source of truth for your Magic: The Gathering collection. You have a Deckbox account from 2015, an Archidekt deckbuilder you’re using now, a Moxfield deck list your friend shared, and a spreadsheet your dad made tracking his 1997 rares. All of them use different formats.

Here’s the compatibility map.

The formats

Plain text (decklist)

The original. Just card names, quantities, one per line:

4 Lightning Bolt
2 Counterspell
1 Black Lotus

Used for imports into every deckbuilder. Loses information about set, collector number, finish, and condition. Best for quick deck sharing; not suitable for collection management.

CSV

Comma-separated columns. The lowest common denominator. Typical columns:

Count,Name,Set,Set Code,Collector Number,Finish,Condition,Language
4,Lightning Bolt,Fourth Edition,4ED,207,Nonfoil,NM,EN

CSV handles everything — conditions, foils, sets, notes — provided the columns line up. Every collection tool imports and exports CSV, though column names vary.

Deckbox CSV

Deckbox’s specific CSV dialect. Column headers include: Count, Tradelist Count, Name, Edition, Card Number, Condition, Language, Foil, Signed, Artist Proof, Altered Art, Misprint, Promo, Textless, My Price.

Deckbox-specific but easy to handle if an app maps Edition → Set and Foil → Finish.

Archidekt CSV

Similar to Deckbox but with slightly different column names and additional “Tags” and “Category” columns for deck organisation.

Moxfield CSV

Moxfield exports a CSV with Count, Name, Set Code, Collector Number, Condition, Language, Foil, Tags, Last Modified.

MTGGoldfish CSV

MTGGoldfish’s export uses Quantity, Card, Expansion, Price, Condition, Language, Foil columns. Slightly different naming.

.dek and .dec files

XML-based formats from MTGO / Magic Online. Less common now but still used for importing/exporting MTGO deck files.

Arena format

Text format specific to Magic: The Gathering Arena:

4 Lightning Bolt (STA) 42
1 Counterspell (M21) 46

The set code and collector number are included in each line. Used for Arena imports.

Format compatibility matrix

Moving between apps, here’s what reliably survives:

From → To	Cards	Counts	Sets	Finishes	Conditions	Tags
Deckbox → Moxfield	✓	✓	✓	✓	✗	✗
Moxfield → Archidekt	✓	✓	✓	✓	✗	partial
Archidekt → Moxfield	✓	✓	✓	✓	✗	✗
Deckbox → CSV → Excel	✓	✓	✓	✓	✓	✓
Plain text → anywhere	✓	✓	✗	✗	✗	✗
Arena → MTGO .dek	✓	✓	✓	✗	✗	✗

Notes:

• Conditions are almost never preserved between collection-management apps. Only Deckbox and Archidekt store them in CSV exports.
• Tags rarely survive because the receiving app defines its own tag system.
• Altered art and signature flags only survive Deckbox-to-Deckbox and CSV-level.
• Prices are never preserved — always recalculated by the receiving app.

How Scrytics handles imports

Scrytics’ collection import (shipping) handles:

• Deckbox CSV — full fidelity including conditions and signed flags
• Moxfield CSV — full fidelity minus conditions (Moxfield doesn’t store them)
• Archidekt CSV — full fidelity
• MTGGoldfish CSV — full fidelity minus tags
• Plain text decklists — card names only, auto-matches to most common printing
• Arena format — card names + sets + collector numbers
• Generic CSV — auto-detects columns; falls back to name-only if mapping is ambiguous

Import runs entirely on-device. The full catalog is already loaded locally, so matching 10,000 cards takes under a second. No network round-trip.

How Scrytics exports

Scrytics’ collection export (shipping) supports:

• Deckbox-compatible CSV
• Moxfield-compatible CSV
• Archidekt-compatible CSV
• MTGGoldfish-compatible CSV
• Plain text (decklist format)
• Raw JSON for custom imports

The “master CSV” approach

If you use multiple apps, maintain a single master CSV as your source of truth. Export from your primary tool (Scrytics, Deckbox, etc.) whenever your collection changes. When you need to import to another tool, convert from the master rather than re-exporting across apps.

A master CSV survives:

• App shutdowns (Deckbox has had reliability issues; a CSV backup guarantees survival)
• Subscription expirations
• Data-migration bugs between versions

Common import pitfalls

Duplicate cards across sets. “Lightning Bolt” appears in 20+ sets. Without set code, the importer guesses (usually picks the most common printing). Use CSV with set codes when precision matters.

Foil vs non-foil confusion. Some CSV formats use “Yes/No”; others use “Foil/Nonfoil/Etched”. Check the format spec.

Japanese / foreign-language imports. Most CSV exports include only the English name. Scrytics’ localized-name-matching (shipping) resolves Japanese/German/etc. names back to canonical cards.

Fun cards and tokens. Some tools don’t index Secret Lair Alchemy-exclusives or token cards. Names may not match cleanly.

Collection-management workflow

The approach most serious collectors use:

1. One primary app for day-to-day collection updates (Scrytics, Deckbox, or equivalent).
2. Quarterly CSV export to a cloud folder (iCloud, Google Drive, Dropbox) as backup.
3. Secondary app for specific use cases (Moxfield for deck sharing, MTGGoldfish for Magic Online tracking).
4. Yearly reconciliation — import CSV back into primary app and verify card counts.

This keeps your data safe across app changes and makes it possible to migrate tools later without losing years of accumulated data.

Scrytics and the future of your collection

Scrytics treats your collection as local data. It’s in your phone’s storage, synced via iCloud if you enable it, never uploaded to our servers. When you export to CSV, you own the file. If Scrytics shuts down (it won’t, but if), your data isn’t trapped.

Every other app in the space makes similar claims but implements them differently. Always verify what “your data” means by exporting a CSV and checking it’s complete.