On May 28, 2026, Nina Protocol told its users to withdraw their earnings and export their releases, purchases, and connections. They had six weeks.
The independent music platform had spent five years building an alternative to conventional streaming: artists ran digital storefronts, sold directly to listeners, and kept their sales revenue. Nina also built an editorial archive, hosted label hubs, and tried to preserve the cultural context that streaming catalogs routinely flatten. The values were appealing. The economics weren't strong enough — Nina said it couldn't find a sustainable revenue strategy at its size, and scheduled its site and app to go offline in July.
Then, on July 22, SoundCloud acquired Nina's editorial archive and genre map and opened an optional migration route for its users. SoundCloud is offering those artists a five-month Artist Pro trial, including distribution, audience, and monetization tools. (These details come from the companies' own announcements; the financial terms weren't disclosed, and TechCrunch reported the transaction on July 22.)
For Nina's community, that's a far better outcome than a dead login page and a forgotten archive. For everyone else, it's a useful warning.
Most artists only prepare to leave a platform after something goes wrong — a delayed payment, an unexpected takedown, support that stops answering, an alarming shutdown notice. By then they're reconstructing years of release data against a deadline. There's a healthier habit: make every music service replaceable before replacement becomes necessary.
Artist-friendly doesn't mean permanent
Nina did many of the things independent artists say they want. It emphasized ownership, direct sales, community, editorial discovery, and an alternative to one-size-fits-all streaming economics. Artists and labels including ML Buch, Yung Lean, Warp Records, and Hyperdub used it, according to Music Business Worldwide's July 22 report. None of that guaranteed commercial durability.
This deserves some honesty, because the instinct is to look for a villain and there isn't one. A music company can have thoughtful founders, fair terms, and real cultural credibility and still fail to reach sustainable scale. Subscription revenue can fall short. Marketplace activity can stay too small. Infrastructure, development, rights administration, and support all cost money even when a platform takes little or no commission.
So when you evaluate a service, you actually need two sets of questions. The first is the familiar one: Are the terms fair? Who owns the music? What does it charge? How are royalties calculated? The second is less comfortable, and most artists skip it: How does this company make enough money to keep operating? Can I export my data? What happens to my catalog, balance, and audience if it's sold or shut down?
A generous business model that survives is valuable. A generous business model with no path to survival is a migration project waiting to happen.
Ownership is only one kind of control
Nina used decentralized technology, including Arweave for permanent storage of files and metadata. That architecture may help preserve the underlying material — but it doesn't keep a functioning marketplace alive. A music file can technically go on existing while the storefront, search, customer accounts, editorial context, payment system, and everyday experience around it all disappear.
This matters because "you own your music" gets presented as though it answers every platform-risk question. It doesn't. There are at least four different kinds of control, and owning your masters only covers one of them:
- Rights control — who owns or licenses the master and the composition?
- Asset control — do you actually possess the final audio, artwork, videos, and release files?
- Data control — can you retrieve metadata, transaction records, statements, and audience information?
- Relationship control — can you reach your supporters without going through the platform that introduced them?
A contract can confirm you own the master while the only complete copy of the metadata lives in someone else's dashboard. A platform can allow downloads without giving you usable customer contacts. You can have thousands of followers and no lawful way to reach them anywhere else. Ownership matters enormously; portability decides how useful that ownership stays when things go wrong.
The Nina–SoundCloud deal is a rescue, not a rule
SoundCloud says Nina users can transfer their tracks and use Artist Pro tools for five months. Its migration page currently highlights unlimited uploads, audience insights, distribution, Fan Support, and Fan-Powered Royalties, and states that subscribers distributing through SoundCloud keep 100% of their royalties. Those are SoundCloud's own descriptions of its offer, not independent findings about what artists actually earn.
The transfer being optional is the important part — Nina's artists aren't automatically absorbed into another ecosystem just because some assets changed hands. But don't read this as a template. Most platforms that fail don't find a buyer at all, and there's no reason to assume the next closure comes with a friendly five-month trial attached. Plan for the version where nobody rides in.
Keep an exit package, not a pile of emails
The fix for most of this is unglamorous: keep an organized, current copy of everything that matters, so a shutdown is an inconvenience instead of an excavation. For every release, hold your own copy of:
- the final masters and instrumentals;
- artwork and video files;
- complete metadata, including ISRCs and UPC;
- ℗ and © information;
- split sheets, licenses, and ownership agreements;
- delivery confirmations;
- royalty statements and payment records;
- links to the live release on priority services.
Don't treat a streaming link as an archive. And don't assume your distributor will remain your permanent source for an ISRC you happened to receive through its upload form. For labels, one organized catalog sheet beats 200 confirmation emails scattered across former employees' inboxes.
Export your statements regularly, too. Royalty dashboards are operational tools, not permanent accounting records — keeping the original reports lets you reconcile later payments, document historical income, and identify which provider delivered a particular version.
Preserve the recording's identity during a transfer
If a distribution relationship ends, the safest move is an overlap, not a leap.
Deliver the unchanged masters through the new distributor using the existing ISRCs, titles, artist spelling, audio, track order, and original release dates, and supply the correct platform profile identifiers. Wait until the new delivery is live and properly connected before you ask the former distributor to take its version down.
Spotify says re-uploaded music can keep its play count through track linking when the audio and metadata match — including duration, title, and artist name — and you can confirm the link by checking whether both versions show the same play count. That's Spotify's current guidance, not a promise that every service preserves every form of engagement.
One trap to avoid: don't "clean up" the release halfway through a transfer. Changing the title style, swapping the artwork, altering the audio, and fixing several artist roles all at once can stop a platform from recognizing the incoming delivery as the same recording. Move first, verify, then handle nonessential improvements separately.
Artists using CREWPORT to prepare a catalog transfer should enter their legitimate existing ISRCs rather than generate replacements, and provide established artist-profile information wherever it exists. The same rule holds with any distributor: continuity depends on accurate source data. (The mechanics of why fresh codes break your history are in what is an ISRC.)
Your audience needs an exit too
Catalog continuity only solves half the problem. Nina wasn't just storage or delivery — it gave releases context through writing, curated hubs, and community. When a platform like that closes, artists can lose the place where their audience understood the work, not just the place where the audio played.
So build at least one direct channel you control:
- an email list collected with clear consent;
- an artist website;
- a customer database for direct purchases;
- an independent archive of your editorial coverage;
- a contact list for press, venues, and collaborators;
- local copies of photos, bios, and campaign materials.
A social follower is still useful. It's also just permission to appear inside someone else's product, governed by someone else's account rules and recommendation system. Direct relationships take maintenance — email addresses have to be collected lawfully, protected, and given a real reason to stay subscribed. An abandoned newsletter with one annual sales blast isn't much of a fallback; a simple list that gets thoughtful release notes, tour updates, or studio dispatches can be. The goal isn't to drag every fan off platforms. It's to make sure one company's closure can't erase the only path between you and your listeners.
Watch for operational warning signs
You rarely get to see a private platform's finances. You can still notice service quality slipping. Pay attention when:
- royalty statements arrive later than usual;
- withdrawals repeatedly fail;
- support stops answering substantive questions;
- delivery problems go unresolved;
- key features disappear with no replacement;
- terms change around catalog retention or account closure;
- staff departures become visible;
- the company starts pushing unusually aggressive lifetime offers;
- you're told to download data or verify balances urgently.
One late reply doesn't prove a business is failing. Treat these as reasons to tighten your records, re-read the agreement, and confirm your exit package is complete — not as material for public speculation. And review the contract while the relationship is healthy: look for termination rights, notice periods, post-termination takedowns, unpaid balances, assignment after a sale, data-export rights, and continuing access to statements. The exit clause is part of the product.
A hypothetical two-week exit
Consider a label with 60 releases on a niche direct-to-fan platform. The platform announces it will close in two weeks.
The label owns the masters — but only half of its original WAV files are organized. Customer activity lives inside the dashboard with no recent export. Several releases have no documented ISRCs, and the employee who created the accounts left last year. For the next 14 days, the team isn't developing artists. It's downloading files, hunting for agreements, matching payments, rebuilding product pages, and trying to explain the move to supporters.
Now change one fact: the label already keeps a quarterly catalog export with assets, identifiers, statements, and opted-in customer records. The closure still hurts. It just doesn't become an emergency dig.
That's what operational control looks like — and it usually resembles a folder nobody was excited to create.
Run a platform exit drill once a year
Pick one important service and pretend it goes inaccessible in 30 days. Can you answer these?
- Which releases, balances, and contracts are held there?
- Can you download every original asset and statement?
- Do you know the correct identifiers and live platform links?
- Who on the team controls the account and its two-factor authentication?
- Can the agreement be terminated, and what happens afterward?
- Which new provider could receive the catalog?
- How would fans be informed?
- What information can't be exported at all?
- Are there unpaid royalties or unresolved disputes?
- How would you prove what the dashboard used to show?
Fix the gaps while support still answers.
The real lesson
Don't reduce the Nina story to "Web3 failed" or "SoundCloud saved the catalog." Nina built meaningful infrastructure and culture, then hit a business-model problem it couldn't solve at its size. SoundCloud's acquisition may preserve valuable work and give artists a real next destination. The broader takeaway is quieter than either headline: use platforms enthusiastically, build communities inside them, take everything the tools offer — just keep your music, data, rights records, and audience relationships capable of surviving somewhere else.
Independence begins with ownership. It becomes real when you can leave.
Build a catalog that can survive any platform
You can't control which services stay in business. You can control whether their problems become yours. Keep your masters, metadata, statements, and audience in your own hands — and when you do move, move without breaking your streaming history or your identity.
CREWPORT keeps your ISRCs, UPC, and artist-profile IDs attached to every release and validates your metadata before delivery, so a transfer preserves your catalog instead of scrambling it.
Sources
- Nina Protocol — Wind-Down and Migration Information
- SoundCloud — Nina Protocol Migration Offer
- TechCrunch — SoundCloud Acquires Nina Protocol, July 22, 2026
- Music Business Worldwide — SoundCloud Acquires Nina Protocol, July 22, 2026
- Spotify for Artists — Re-uploading Music and Track Linking
- Symphonic — How to Switch Distributors Without Losing Streams, February 5, 2026