If you exported your library from ScryDeck (Collection → Export), you can import that backup to restore cards or merge into an existing account.
Collection → Import → **ScryDeck backup** accepts both `.json` and `.csv` files on the same screen. ScryDeck detects the format automatically when you tap **Import**.
**JSON** is the full-fidelity restore path — tags, notes, status, acquisition details, and placement. **CSV** restores printings, quantities, status (owned, proxy, need), binders, decks, and deck zones but omits tags and notes.
-
Open ScryDeck backup import
Sign in and go to Collection → Import → ScryDeck backup.
On desktop, a modal opens. On mobile, you land on the upload screen.
-
Choose import mode
**Add to collection** (default) keeps your existing cards, binders, and decks and merges in rows from the backup.
**Reconcile with collection** smart-merges the backup: it matches cards by printing, finish, condition, and status; reuses binders and decks with the same name; skips duplicates; and inserts only net-new rows. Cards in your library that are not in the backup stay put. Reconcile shows a preview summary before you confirm.
**Replace collection** permanently deletes your entire current library — all cards (including sold, lost, and removed rows), binders, and decks — then imports the backup. Use this for full restore after data loss or to start over from a known-good export.
Replace mode shows a confirmation step with remove/import counts. You must check an acknowledgement box and type `REPLACE` (case-sensitive) before the import runs.
-
Upload and import
Choose your backup file — for example `scrydeck-collection-YYYY-MM-DD.json` or `scrydeck-collection-YYYY-MM-DD.csv`.
For **Add to collection**, tap **Import** to merge the backup into your library.
For **Reconcile with collection**, tap **Continue**, review matched/new counts, then confirm with **Reconcile import**.
For **Replace collection**, tap **Continue**, review what will be removed and imported, then confirm with **Replace collection**.
When import finishes, a success message summarizes removed and imported counts (replace) or added rows (append).
-
JSON backup (full restore)
JSON exports include one object per card row with condition, finish, language, status (owned, proxy, need), tags, notes, acquisition date and price, and binder or deck assignment. Sold and lost rows are not included in backups.
Deck location zones (mainboard, commander, sideboard, maybeboard) restore from the export.
If your plan does not include proxies, proxy rows import as owned.
-
CSV backup (structure restore)
ScryDeck CSV aggregates copies by printing, finish, condition, status, language, container, and deck zone.
Container type and Container name place cards in binders or decks. Location zone preserves deck boards. Status preserves owned, proxy, and need placeholders.
CSV does not include tags or notes — use JSON when you need that metadata.
-
Append vs reconcile vs replace
**Add to collection** is append-only: existing cards are kept and backup rows are added, even when binders or decks share the same name (ScryDeck creates new containers).
**Reconcile with collection** matches backup rows to existing cards (`card_meta_id`, finish, condition, status). Sold and lost copies are not matched — reconcile may insert a fresh owned row instead. Matched cards keep your existing notes and tags; metadata from the backup applies only to new inserts. Loose owned copies can be moved into binders or decks when the backup assigns them there.
**Replace collection** wipes your library first, then imports the backup. Failed replace imports roll back — your library is unchanged if validation or tier checks fail.
Invalid files fail with a clear error and no partial writes. JSON imports fail if the file references printings not in the ScryDeck catalog.
Free tier limits apply to net-new rows and containers on reconcile, and to the post-replace library size on replace.
Have your backup ready?
Open Collection → Import → ScryDeck backup and upload your JSON or CSV export.
Go to import