A Practical Workflow for Migrating Discogs to What's Spinning

A good workflow migrating Discogs to app is not just a data transfer. It is a cleanup pass, a listening reset, and a chance to make your record shelf easier to use. Discogs is excellent at cataloging exact releases, pressings, labels, catalog numbers, marketplace value, and wantlists. What's Spinning is built around the living part of the collection: what you play, how often you play it, and how your turntable listening turns into a history you can actually revisit.

The smartest migration treats Discogs as the reference library and What's Spinning as the listening log. Export the catalog, clean the rows that matter, keep the pressing detail intact, then let your turntable rebuild the active layer as you play records. That keeps the process accurate without spending a weekend tapping every album into another database.

Why migrate carefully instead of copying everything blindly?

Discogs collections can contain years of collector decisions: multiple versions of the same album, grading notes, custom folders, wantlist items that turned into purchases, and records you sold but forgot to remove. Discogs says its Collection page lets users edit media condition, sleeve condition, notes, and custom folders, and it can export the entire collection as a CSV file from the Export page [1]. That is useful, but it also means your export is only as clean as your old habits.

The stakes are higher than they were a decade ago because vinyl collections have grown with the market. RIAA reported that U.S. vinyl revenue reached $1.4 billion in 2024, up 7%, with vinyl albums outselling CDs in units for the third year in a row, 44 million versus 33 million [2]. More records means more duplicates, more near-identical pressings, and more reasons to separate catalog accuracy from listening behavior.

Step 1: Export your Discogs collection

Start in Discogs, not in a spreadsheet. Open your Collection settings and request a CSV export. Discogs notes that the export request is scheduled and that you will be notified when the file is available [1]. Save the original file untouched. Then make a working copy with the date in the filename, for example discogs-collection-2026-07-21-working.csv.

If you are technical, the Discogs API can also read collection data. The developer documentation describes collection resources arranged into folders, including permanent folders such as All and Uncategorized, plus endpoints for collection folders, releases, custom fields, and collection value [3]. In a live API check, the unauthenticated Discogs API reported 19,312,851 releases and returned rate-limit headers showing a 25-request limit for that unauthenticated request. That is plenty for a quick lookup, but CSV is still the better first move for most collectors.

Step 2: Clean the export before you trust it

Open the working CSV and create four review columns: keep, needs_review, duplicate_candidate, and play_priority. Do not delete rows yet. Mark anything that looks suspicious: duplicate artists and titles, generic album versions, missing media condition, damaged sleeves, box sets, 45s living in LP folders, and records you know you sold.

Use Discogs strengths during this pass. Exact pressing matters when two copies have different masterings, different labels, or different resale value. Listening history cares less about every matrix variation, but your physical shelf does. Keep release IDs and catalog numbers in your archive so you can always trace a row back to the exact Discogs entry.

Step 3: Map collector data to listening data

A migration fails when every old field is treated as equally important. Condition, notes, and folders should become decision helpers. Release ID, artist, title, label, year, and format are identity fields. Rating, date added, and folder are behavior clues. Marketplace value is context, not a listening instruction.

Discogs estimates collection value from recent marketplace sales history and warns that items with no sales history are not included and that the exact value depends on many variables [1]. That is a good reminder: value is not the same thing as usefulness. A five-dollar thrift-store soul record you play every month deserves more attention in What's Spinning than a sealed reissue you never open.

Step 4: Build a migration queue

Instead of trying to migrate everything at once, create three batches. First, pull the 25 to 50 records you play most. Second, pull records with messy metadata or uncertain pressings. Third, pull records you have not played in a year. This turns migration into a listening project rather than a clerical chore.

For each batch, clean the records, check the sleeve and label, and play them through your normal setup. Let What's Spinning capture the real listening activity as it happens. Keep the Discogs export nearby for pressing notes, but resist the urge to recreate old shelf data as fake play history. The win is a current, truthful log.

Step 5: Reconcile after two weeks

After a couple of weeks, compare your Discogs working file against your new listening activity. Which favorites never got played? Which low-value records keep showing up? Which duplicates are unnecessary? This is where migration becomes collection improvement.

Make one folder in Discogs called something like Review After What's Spinning. Move records there if the export says you own them but your listening habits say they are dead weight, unresolved duplicates, or candidates for cleaning. Keep another short list for records you want to rediscover. The goal is not a perfect database. The goal is a collection that invites you back to the turntable.

FAQ

Can I import a Discogs CSV directly into What's Spinning?

Use the Discogs export as a planning file and audit trail, then let What's Spinning build the active listening record from what you actually play. That avoids turning stale catalog rows into false listening history.

Should I use Discogs export or the Discogs API?

For most collectors, the CSV export is simpler and safer. The API is useful for developers or very large collections, but it adds authentication, pagination, and rate-limit handling.

What data should I clean before migrating?

Start with release identity, format, condition, folder, notes, and duplicates. Those fields answer practical questions such as which pressing you own, what needs cleaning, and what should be played next.

What should I do with records that Discogs cannot identify cleanly?

Put them in a review folder, check catalog numbers and runout information, then verify them against the physical sleeve. Do not force a match just to finish the spreadsheet.