SpinstackA bad migration turns a collection into a count. You keep the artist, the title and maybe a cover image, and lose the pressing, the note about the signed sleeve, the play history, and the reason one copy stays while another gets sold. This example is built around the details that make a vinyl library yours.
The goal is more than getting records from one place to another. It is to keep each copy's identity, settle on one source of truth, and leave every record ready for its next spin or its next owner.
The example collection
Picture a collector with 640 records spread across a Discogs collection, a notes app and a shelf organized by instinct. The Discogs collection has release entries and purchase prices. The notes app holds fragments: "light tick through track two," "cleaned March," "original inner missing." A handful of recent spins live only in memory.
Before moving anything, the collector decides what has to survive. The release entry is essential but not enough, because a record is not interchangeable with every other copy of that release. The migration has to keep pressing-level identification, ownership details, physical condition, and the history built up since the record came home.
That changes the job. A catalog migration asks, "Do I still have the album?" A collection migration asks, "Can I still recognize my copy?"
Start with a record-level inventory
The first pass should create one entry for every physical item, not one per title. Two copies of the same release stay as two records. One might be a quiet first pressing with a worn jacket, the other a later reissue bought to play without worry. Merging them erases something useful.
For each copy, keep the release identification from the original library, then add the ownership facts that catalogs tend to flatten: date acquired, price paid, where it came from, where it is stored, and a private note for anything that doesn't fit a field. A useful migration record has four layers:
- Release identity: artist, title, label, catalog number, country, format and pressing details.
- Owned-copy facts: price paid, date acquired, duplicate status, shelf or crate location, and whether it is for sale.
- Condition evidence: media and sleeve grades, sleeve observations, cleaning notes and playback behavior.
- Collection history: spins, comparisons, repairs, upgrades, and the small decisions that explain why this is the copy you kept.
The first layer can usually come from an existing catalog. The other three are where a migration gets personal.
Choose the source of truth first
Most migrations go wrong because collectors try to clean data after it has been copied into three new places. Decide where each kind of fact belongs before you move a single record.
For release metadata, Discogs can stay the reference if that is where your pressings are already identified. For ownership and activity, pick the library you will actually open beside the turntable. An old spreadsheet with useful notes is source material, not a permanent second database.
This is also when to separate facts from guesses. "Bought for $18 at a record fair" is a fact. "Probably VG+" is a starting point. Mark uncertainty instead of turning it into certainty on the way across. Condition is especially easy to overstate when it was copied from a seller's description years ago.
Two-way Discogs sync helps only if you know where its job ends. It keeps collection records aligned, but it can't tell whether your sleeve has a split seam, whether a tick is audible on your system, or whether a copy has become the one you always reach for. Those are facts about your copy, and they need a home built for your library rather than for marketplace listings. In Spinstack, if one of your Discogs fields already holds the date a record came to you, you can name it as Date acquired in Settings, so that history comes across instead of being retyped.
Normalize before you automate
Export whatever can be exported. Then resist importing it untouched.
Look first for duplicates caused by inconsistent names, missing identifiers or alternate release entries. A common one is a record entered once as a general release and once as a specific pressing. Another is a box set logged as one title in one place and as separate discs in another. Don't delete anything until you have checked the shelf. The record in your hand gets the final vote.
Settle a few conventions before the move: one date format, one currency, and one name for each storage location and other copy-level field. "Living room cube 3," "LR 3" and "third cube" are one place with three names, so pick one. A migration is a rare chance to make future searches work.
Move free-text notes across intact first. Rewrite one only when it can become a structured fact, such as a grade or a location. "Plays better than it looks" is worth keeping as a note because it records experience, and it shouldn't be forced into a grade it doesn't support.
Migrate in passes, not one big import
The safe version of this migration has three passes. First, move the whole catalog with its release identity. Second, check the records that matter most: expensive pressings, multiple copies, records marked for sale, and anything with incomplete identification. Third, add the physical and personal history an export can't contain.
The third pass is where a collection app has to earn its place. Scan a barcode or a sleeve when it helps identify a record, then confirm the pressing against the copy in front of you. Catalog numbers, matrix details, inserts and label variations can matter more than a matching cover image, and the guide to reading vinyl runouts covers the deadwax side of that check.
For condition, drop the habit of assigning a grade from across the room. Inspect the sleeve, then play a side. In Spinstack, Scratch Detection listens through the iPhone microphone while the side plays in a Silent Session and maps the marks you can hear, track by track. On an iPhone Pro or iPad Pro, Groove Vision adds a look at the surface with the camera and the LiDAR sensor and estimates a grade with a confidence level. You still set the grade; the evidence sits beside it, and a Condition Receipt can go to a buyer when the record changes hands. Our guide to record condition tracking goes further into keeping those notes current.
Not every record needs the same attention. A common reissue you play often may need only a quick grade and a note. A scarce pressing headed for sale deserves a full inspection. The cost is time, so spend it where uncertainty is expensive.
Rebuild only the history you'll use
Don't try to backfill every spin you have ever had unless you actually kept that history. Invented completeness is worse than an honest starting line. Start logging from the migration date, and add older plays only where you have reliable notes, dated photos, or a clear memory tied to a particular record. If you have scrobbled to Last.fm for years, Spinstack can bring those scrobbles in as spins, which is real history rather than reconstruction.
A spin log becomes useful quickly once it is current. It shows whether a record is a shelf trophy or part of your life, and it makes suggestions like What to Spin more interesting when the library knows what has been neglected and what you keep pulling out.
For records that move between rooms, storage and a friend's listening session, an NFC tag on the sleeve gives the object a direct route back to its entry: tap it, and the Tap Card shows that copy's pressing, grades and play history. Alphabetical shelving can't do that. The shelf stays physical, and the context is one tap away.
Validate against the shelf
Don't trust the final count until you have walked the shelves. Take the library to the record room and check one section at a time. Confirm that duplicates are distinct, that missing records are really missing, and that copies marked for sale aren't still filed among the keepers.
This is where the library settles down. You stop wondering whether the entry on screen is the copy you own, you stop keeping a backup notes file because the catalog can't hold a sentence, and when a buyer asks about condition you have more than a grade typed from memory.
Questions collectors ask
How long does a migration like this take?
The first pass, moving release data, can take an afternoon for a few hundred records. The checking and condition passes are better spread over weeks, done as you pull records to play, clean or sell. Trying to finish everything in one sitting is how mistakes get copied in.
Should I keep the old spreadsheet after migrating?
Keep it as an archive, read-only, until you have walked the shelves and are happy with the new library. Then stop editing it. Two live copies of a collection drift apart within months, and you end up not trusting either one.
Can I get my data back out of the new app later?
You should check before you commit to any app. With Spinstack, the collection itself lives on Discogs, which has its own export, and your spin history can be exported as JSON or CSV whenever you like.