Discogs to App Migration: Your Workflow Guide

A smart workflow migrating Discogs to app is not a blind copy-and-paste job. Discogs is brilliant as a reference library because it is pressing-aware, marketplace-aware, and built by collectors who care about tiny details. A listening app has a different job. It should help you remember what you actually play, how your habits change, and which records are part of your real home rotation.

That distinction matters because vinyl collections are bigger and more valuable than many collectors planned for. The RIAA reported that U.S. vinyl revenue reached $1.4 billion in 2024, up 7%, and vinyl albums outsold CDs for the third year in a row, 44 million units versus 33 million [1]. When your shelves grow from a crate to a wall, migration stops being admin work. It becomes preservation.

The goal is simple: keep Discogs as your exact-release archive, then use What's Spinning as the day-to-day listening layer. Do it in batches, keep the pressing data intact, and let the turntable rebuild your active history from records you actually play.

Start with a Discogs export you can trust

Discogs says Collection entries are tied to specific release pages, not master releases, and recommends checking catalog number, images, and other identifiers before adding an item [2]. That is the same discipline you want before migrating. Export your entire Collection as a CSV file from the Collection settings, then save the untouched file with a date in the filename.

Make a second working copy. Never clean the only export. Your original CSV is the audit trail you can return to if a spreadsheet sort goes sideways or if you later notice that a reissue was mistaken for an original pressing.

Separate identity fields from habit fields

The first pass through the spreadsheet should label each column by purpose. Artist, title, release ID, label, catalog number, format, country, and year are identity fields. They answer, "Which object is this?" Media condition, sleeve condition, custom notes, rating, folder, and date added are context fields. They answer, "What do I know about my copy?"

Discogs also lets collectors manage custom folders and custom fields, with a 1,000-folder limit, and its Collection view can show estimated value based on the last 30 Discogs marketplace sales. Items without sales history are not included, and Discogs cautions that exact value depends on many variables [2]. Treat that value as context, not truth. A $6 record played monthly is more important to a listening app than a sealed limited variant that never leaves the outer sleeve.

Use Discogs data for what it does best

Discogs is huge. In a live API check for this guide on September 8, 2026, the Discogs API reported 19,432,849 releases, 10,245,445 artists, and 2,430,154 labels. The same response exposed an unauthenticated rate limit header of 25 requests [3]. That scale is why exact release IDs are worth preserving. It is also why you should not try to rebuild every field manually in another app on a Saturday afternoon. That way lies madness, and probably a duplicate copy of Rumours.

Keep a column called "Discogs release URL" or "Discogs release ID" in your working file. If you later need matrix numbers, pressing plant clues, alternate covers, or marketplace context, you can return to the authoritative record instead of relying on memory.

Build a migration queue, not a mega-project

Pick 50 records for the first batch. Include the 20 albums you play most, 10 recent purchases, 10 records with confusing versions, and 10 records you have not played in years but still think you love. That mix catches the main migration problems: obvious favorites, new arrivals, metadata messes, and sentimental shelf residents.

Before playing each batch, clean the records, check sleeve notes, and compare the label or runout against the Discogs entry if the pressing matters. Then play them normally. Do not create fake listening history to match your old collection. If a record has not spun in three years, that is valuable information. Let the app start with reality.

Map folders to decisions

Discogs folders are often personal archaeology: "For Sale," "Inherited," "Need Clean," "Jazz Shelf," "Upstairs," "Maybe Upgrade." During migration, convert those folders into decisions. "Need Clean" becomes a prep task. "Maybe Upgrade" becomes a note to compare reissues. "For Sale" should probably not be part of your listening migration at all unless you want one last play before it leaves.

If you have multiple copies of the same album, migrate them intentionally. Keep the keeper copy, the play copy, and the sell copy distinct in your archive. In the listening layer, however, focus on the copy you actually put on the platter. Listening data gets muddy when three near-identical pressings are treated as three equal daily records.

Reconcile after two weeks

After two weeks, compare the app's listening history with your Discogs working file. Which favorites appeared immediately? Which expensive records did not move? Which genres are overrepresented in the catalog but absent from real listening? That review is the payoff. The migration becomes less about having a perfect database and more about understanding the collection you live with.

Keep the Discogs export somewhere safe and repeat the batch process until the active shelf is represented. You do not need every record migrated on day one. You need a workflow that protects exact-release data while making the listening layer honest, useful, and easy to maintain.

FAQ

Can I import my Discogs CSV directly into a vinyl app?

Sometimes, but direct import is rarely the cleanest first move. Use the CSV as your source of truth and migration checklist, then move records in batches so duplicates, bad pressings, and stale folders do not pollute the new system.

Which Discogs fields matter most during migration?

Preserve release ID, artist, title, label, catalog number, format, year, condition, notes, and folder. Those fields let you trace a record back to the exact Discogs entry while still deciding what belongs in your listening workflow.

Should I migrate records I plan to sell?

Usually no. Keep them in Discogs for inventory and value tracking, but do not add them to a listening app unless you plan to play them. Migration is a good moment to separate shelf ownership from active listening.

How often should I reconcile Discogs and my new app?

Do one review after two weeks, then monthly until the active collection feels stable. After that, reconcile after big purchases, collection cleanouts, or major shelf reorganizations.