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. Names are matched against the Scryfall card database, including face names and printed names, so a card entered by one of its faces or in another language still finds its entry. A row we cannot match is still imported with the name your file gave it, and the import tells you which names those were, so nothing is silently dropped and no "best guess" quietly puts a different card in your binder. There is also a one-way sync: give MTG Burrow your Moxfield collection URL and it treats that collection as the source of truth, adding, updating and removing rows to match it.

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 Power 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 its normal/foil/etched column, language, condition, and the binder columns a full-collection export carries. A Manabox export can rebuild its binders and decks in MTG Burrow as part of the import, and rows that belong to a Manabox list can be left out.

For collections that started life elsewhere, the importer reads the column names Moxfield and Manabox use: card name, set code, collector number, quantity, and the optional foil, language, and condition fields. An export that does not use those headers needs to be renamed to match before it will import — there is no column-mapping step to confirm a guess for you.

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. A foil and a non-foil of the same printing are separate rows, and Manabox's etched finish is read as its own value; Moxfield's CSV has no etched column to read.
• 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? Set codes and collector numbers are language-neutral, so those columns read the same either way. A localized card name is matched against the printed names Scryfall records for each card, so it resolves to the English entry rather than failing.

Get started

Create a free account to import your Magic: The Gathering collection. Already a member? Log in and run a fresh import — an upload updates the rows it names rather than replacing your collection, 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 Power 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.