Import your MTG collection from Moxfield, Manabox, or CSV

The hardest part of moving any Magic collection between tools is getting the cards across the gap without losing precision. Set codes get re-encoded. Foil flags get dropped. Language variants disappear. By the time a thousand-card collection finishes a sloppy migration, half the printings are wrong and you're back to manual cleanup. The point of MTG Burrow's import flow is to skip that. We accept the standard exports from the tools players already use — Moxfield, Manabox, and any well-formed CSV — and we match each row carefully against the full Scryfall card database before it lands in your collection.

This is a free MTG collection import. Whether you're trying out MTG Burrow as a Moxfield alternative or a Manabox alternative, or running both in parallel, the import side is built so the migration costs nothing in either money or accuracy.

Import Moxfield to MTG Burrow

Moxfield exports your collection as CSV from the collection settings. Drop that CSV into the MTG Burrow import flow and we read each row's name, set code, collector number, foil flag, language, and quantity. Cards are matched by set code and collector number first (the precise match), falling back to set code plus name for older exports that may not include collector numbers. Rows that can't be auto-matched surface in a review step so you can resolve them manually before they commit to your collection — no silent errors and no "best guess" that quietly puts the wrong printing in your binder.

If you're testing MTG Burrow as a Moxfield alternative, importing your collection is the prerequisite for everything else on the site. The collection feeds the digital trade binder, the deck-build search, the trade tool, and the set completion tracker. The import is the first step in trying any of those workflows on real data.

Import from Manabox or any CSV export

Manabox exports collections to CSV too — typically from the collection screen's share/export menu. The MTG Burrow importer reads the Manabox CSV format directly, including foil/etched/non-foil flags, language, and condition columns. As with Moxfield, set code + collector number is the canonical match path; ambiguous rows route to the manual review step.

For collections that started life elsewhere — a homebrew spreadsheet, an old Deckbox export, a Helvault dump from years ago — the importer accepts any CSV with the standard columns: card name, set code, collector number, quantity, and optional foil/language/condition fields. Header names are matched case-insensitively, and we'll surface a column-mapping step for any header we don't recognize so you can confirm the mapping yourself rather than trust an auto-guess.

Migrate from Moxfield without losing data

A few common questions about the migration, answered in the order people usually ask:

• What about foils? Foils stay foils. Foil, etched, non-foil, and gilded are tracked as separate rows the same way they are in your source tool.
• Do language variants survive? Yes. If your CSV identifies a card as Japanese or German, the imported row keeps that language tag.
• What if my CSV uses a non-English Moxfield localization? The importer normalizes Moxfield's set-code and collector-number columns regardless of localization, since those fields are language-neutral. Localized card names route through the Scryfall multi-language matcher.

Get started

Create a free account to import your Magic: The Gathering collection. Already a member? Log in and run a fresh import — re-imports merge with your existing collection rather than replace it, so iterative migrations work fine. Once your collection is in, the rest of the site is ready: the collection tracker is the canonical view of what you own, the digital trade binder shares the collection with your playgroup, the deck-build search runs queries across what you and your group own, the trade tool handles trade requests, and the set completion tracker tells you which sets are closest to done.