How to Launch Music Under a New Artist Name
Decide whether a new alias should be separate, clear its identity, map rights and platform profiles, deliver a controlled first release, and transition fans without merging catalogs accidentally.
The short answer
Treat a new artist name as a separate identity unless the real intent is to rename the existing act. Clear the name and handles, document ownership of recordings, artwork, accounts, domains, and data, then decide whether prior catalog stays under the old identity, moves through a distributor-led rename, or connects through truthful credits and context. Deliver early with exact primary-artist metadata, claim every resulting profile, correct mapping before launch, build distinct visuals and contact paths, and tell existing fans what the alias changes without forcing them to follow.
Three things to know
- 01
Decide first whether this is a separate alias, a full rename, a side project, or a collaborative act because each requires different catalog and audience architecture.
- 02
Core platform artist names come from distributor or label metadata; profile visuals and bios cannot repair an incorrectly delivered primary-artist identity.
- 03
Secure rights, names, accounts, domains, recovery, contributor credits, mapping, and data boundaries before promoting the alias, then transition fans with honest context.
New artist-name launch timeline
Move from identity decision through clearance, ownership, delivery, fan introduction, and verified platform separation.
- 1
Choose the model
Define alias, rename, side project, or collaboration; assign catalog, audience promise, credits, governance, and future decision rights.
- 2
Clear and secure
Research confusing names, languages, domains, handles, rights, trademarks, visuals, ownership, accounts, recovery, and data boundaries.
- 3
Build the release
Lock music, rights, credits, artwork, story, contact, links, platform IDs, distributor instructions, timeline, and correction packet.
- 4
Deliver and claim
Create new primary-artist mapping, inspect every profile and catalog, claim access, fix namesakes, and verify all campaign URLs.
- 5
Introduce the difference
Show the sound and purpose, connect old fans selectively, make following optional, and establish distinct content and live proof.
- 6
Monitor separation
Audit mapping, metadata, search, credits, impersonation, links, access, analytics, fan questions, and support resolution after launch.
What kind of artist-name change is this?
Define one of four models. A new alias creates a distinct catalog and audience promise. A full rename changes the existing act and may require coordinated metadata updates across every release. A side project keeps the original act active while separating sound or story. A collaborative act creates a new entity owned and governed by several contributors. Write why the identity exists, which recordings belong to it, whether the old catalog remains active, how credits should connect the projects, and who makes future decisions. Do not choose a separate alias merely to escape weak metrics or an old profile without changing the artist proposition, and do not rename a catalog casually when existing rights, links, press, tickets, claims, and fan recognition depend on it.
How should the name and identity be cleared?
Search streaming services, social platforms, domains, app stores, music databases, performance-rights records, company registries, trademarks where relevant, event listings, search engines, and local scenes for confusingly similar names. Check spelling, pronunciation, translation, unintended meanings, accessibility, handles, domain, email, and how the name looks in artwork and small screens. A platform search is not a legal clearance. Record who created the name and visuals, licenses for fonts and images, trademark strategy, territories, and any coexistence concern. This is educational, not legal advice; use qualified trademark and music counsel before investing when similarity, ownership, band membership, contracts, or international use is material. Never imitate a known artist or manipulate metadata to capture their search traffic.
Who should own the alias assets and accounts?
Create an ownership and access register for the artist name, domain, website, email, social handles, distributor account, label relationship, masters, compositions, artwork, photos, logos, profiles, ad accounts, analytics, ticketing, merch, mailing list, phone numbers, password manager, recovery methods, and contracts. Use business-controlled email, individual logins, least privilege, strong authentication, and documented recovery. For a group, define exits, member changes, revenue, approvals, catalog control, data, and who can continue using the name. Do not let one contractor's personal email become the permanent owner or share one password across the team. Separate the new alias's fan consent and analytics from the old project unless the privacy promise and lawful basis support a connection.
How should the first release be delivered to new profiles?
Tell the distributor this is a new primary artist, provide the exact spelling and roles, and use any supported profile-ID or new-page request process rather than selecting a similarly named artist. Deliver early enough to discover the pages before campaign launch. Record the release ID, UPC, ISRCs, platform URLs, delivery date, territory, label, credits, language, explicit status, artwork, and distributor tickets. Spotify currently says artist names come from label or distributor metadata, while Apple tells artists to use the distributor for content-metadata corrections. Claim or request access to each new profile, then confirm catalog, name, image, bio, credits, links, team roles, and mapping. Do not promote a URL until the exact release and artist page have been checked on every priority service.
What should happen to the old catalog and audience?
Keep the old catalog under its original identity by default when the recordings were marketed, contracted, credited, and recognized that way. If the project is a true full rename, inventory every release, territory, distributor, profile, playlist, link, claim, video, lyric, press page, ticket listing, account, identifier, agreement, and partner before beginning the platform-specific name-change sequence. Spotify currently requires a label or distributor to request the name change and redeliver metadata after approval; that is different from launching a separate alias. For a new side project, connect identities through truthful bios, artist posts, features, websites, and announcements rather than moving unrelated recordings. Do not duplicate the same catalog under both names to manufacture a transition.
How should existing fans be introduced to the alias?
Explain the useful difference: sound, writing role, collaborators, visual world, language, performance format, or creative freedom. Give fans a direct sample and an optional next step instead of apologizing for change or predicting rejection. Use the old project's channels selectively when the audience relationship and consent support it, and make the sender and new destination clear. Prepare a concise origin story, pinned introduction, first-release link, recognizable artist photo, live or studio proof, and answers to likely questions about whether the old act continues. Let people decline without repeated cross-promotion. Measure profile visits, follows, saves, email choices, replies, and repeat listening, but allow the alias to develop its own audience rather than judging it only by migration percentage.
How should launch risk be monitored and corrected?
Create a launch matrix for profiles, URLs, catalog mapping, credits, search results, metadata, lyrics, images, social handles, impersonation, claims, domains, email, link routing, team access, recovery, analytics, and fan questions. Check before announcement, at release, and after platform updates. Prepare one correction packet with artist and release identifiers, wrong and correct URLs, screenshots, distributor delivery evidence, and the requested action. Watch for music landing on a namesake's page or the alias inheriting unrelated catalog. Do not create more duplicate profiles to fix mapping. Use the distributor and documented platform support routes, preserve tickets, and update every campaign link after the correct page is stable. No alias architecture assures discovery, audience migration, or a clean editorial reset.
What supports this identity workflow?
Practical notes
- Spotify says artist names cannot be changed manually and must be handled through a label or distributor request and metadata redelivery.
- Apple Music for Artists says core content metadata is delivered and corrected through the distributor, while profile content is managed separately.
Source notes
- Spotify for Artists Support: Changing your artist name, accessed July 18, 2026.
- Apple Music for Artists: Music metadata and Manage your artist content and profile, accessed July 18, 2026.
Frequently asked questions
- Is launching a new alias the same as changing an artist name?
- No. An alias normally creates a distinct identity and catalog, while a rename changes the metadata and presentation of the existing act.
- Should old releases move to the new artist profile?
- Only when this is a genuine full rename with rights, contracts, credits, distributor, and platform migration reviewed; otherwise preserve the original identity.
- Can an artist create a new Spotify profile manually?
- The release delivery normally creates or maps the profile through distributor metadata; claim and verify the resulting page rather than inventing a duplicate.
- Can one email list promote both artist names?
- Only when the original consent and privacy promise support that use; identify the new project clearly and give subscribers an easy choice.
- Should a new alias hide the creator's previous identity?
- That is a creative and privacy choice, but credits, ownership, contracts, collaborators, platform rules, and truthful public claims still need accurate handling.