PlaylistXfer field manual · 15 minute read

The practical Spotify to Apple Music transfer guide.

Start with a public Spotify link, understand every Apple Music match, fix common problems, and verify what actually arrived.

What can move?

Normal public Spotify playlist and song links, matched against the Apple Music catalog.

What happens first?

A read-only preview and match report. Spotify login is not requested.

When can it write?

Only after you review the report and explicitly connect Apple Music.

01 · Start

Start a transfer without creating anything yet

  1. Copy a normal Spotify URL. Open the public playlist or song in Spotify and choose Share → Copy link.
  2. Preview the source. Paste the link on PlaylistXfer and confirm the title and readable track count.
  3. Choose the analysis scope. Full playlist is the normal choice. The 50- and 150-track modes are intentionally limited tests.
  4. Run the Apple Music match report. PlaylistXfer analyzes the selected rows without asking for Apple Music write permission.
  5. Review uncertain and missing rows. Approve only candidates you trust. Unsafe substitutions stay out.
  6. Connect Apple Music and create. Authorization appears beside the action that writes the new playlist.
  7. Verify the destination. Compare the receipt, order, versions, omissions, and playback inside Apple Music.
Review modeUse it forWhat can be created
Full playlistThe actual transfer, up to the current 500-row web limitAll analyzed and approved rows
First 150 tracksA representative catalog and workflow testOnly those first 150 analyzed rows
First 50 tracksA fast link, storefront, and match-quality checkOnly those first 50 analyzed rows

For a source larger than 500 transferable rows, split it into clearly named sections in Spotify and transfer each section separately. The large-playlist guide covers scope, recovery, and splitting strategies in depth.

02 · Product boundaries

How the transfer works

Public preview

PlaylistXfer validates the submitted Spotify URL and reads public source metadata. It cannot edit the Spotify playlist.

Catalog matching

Each source row is compared with Apple Music using identifiers, title, artist, album, duration, edition markers, and storefront context.

Human review

Strong matches are Ready. Ambiguous candidates require Review. Unsafe or absent candidates stay Missing.

Authorized creation

Only then does PlaylistXfer request Apple Music access, add approved catalog tracks in order, and return a receipt.

Ready

Evidence is strong enough for automatic inclusion.

Review

A likely candidate exists, but the version needs your judgment.

Missing

No candidate passed the safety threshold, so nothing is substituted.

StageData usedNot required
Spotify previewSubmitted public URL and public metadataSpotify password or account authorization
MatchingTrack metadata, catalog candidates, and confidence signalsApple Music write permission
ReviewTemporary report and your row decisionsEmail or profile information
CreationApple Music authorization and approved catalog IDsControl of the Spotify account

For the deeper technical explanation of ISRC, duration, album editions, storefronts, and confidence, read how playlist matching works.

03 · Readiness

Check the Spotify source before matching

  • Use a playlist or track URL. Supported links normally contain open.spotify.com/playlist/ or open.spotify.com/track/.
  • Test signed-out access. Open the exact link in a private window where Spotify is not signed in. The title and tracks should remain visible.
  • Copy from Share. Profile, artist, album, search, queue, and personalized home pages do not identify a transferable source.
  • Expect count differences. A Spotify headline total can include local files, podcasts, unavailable rows, or items without usable public metadata.
  • Respect private content. Change visibility only if you own the playlist and are comfortable making its title and track selection publicly readable.
  • Keep the destination account ready. Use the Apple Music account and storefront where the new private playlist should appear.
The practical privacy test

If the link works only because your normal browser already has Spotify access, the anonymous preview may fail. PlaylistXfer does not bypass private access or ask for Spotify credentials.

Local audio, podcasts, audiobooks, likes, follows, collaborative membership, listening history, and Spotify account relationships do not become Apple Music catalog tracks. PlaylistXfer transfers approved catalog references, not audio files.

04 · Troubleshooting

Fix a Spotify link that will not load

Preview errors happen before Apple Music is involved. Work through these checks in order instead of changing destination permissions.

Retry safely

  1. Keep one browser tab and paste a freshly copied URL.
  2. Confirm the preview before starting Apple Music matching.
  3. If the error names the API, wait a minute and retry once.
  4. Test one other known-public playlist to separate a link-specific problem from a broader outage.
  5. Do not authorize Apple Music to solve a preview error; authorization is relevant only at creation.
Reporting a reproducible issue

Include the failed step, exact visible error, browser and device, approximate time, and whether the link passed the signed-out test. Never send passwords, cookies, Apple tokens, or private browser-storage values. Contact support →

05 · Catalog differences

Understand missing or incorrect matches

A missing result does not always mean the song is absent from Apple Music. It means PlaylistXfer could not find a candidate safe enough to select under the current evidence.

1
Local files or non-song media

Device audio, podcasts, audiobooks, and video items are not Apple Music catalog songs.

2
Regional availability

Music rights vary by country, so the destination storefront may not contain the Spotify recording.

3
Replaced releases

A label can republish a recording with a new album, artwork, date, metadata, or catalog identifier.

4
Alternate editions

Only a remaster, compilation appearance, clean edit, radio edit, live take, or remix may be available.

5
Ambiguous metadata

Generic titles, inconsistent artist credits, and missing identifiers can produce several equally plausible candidates.

CandidateMain riskVerify before approving
Compilation appearanceDifferent packagingArtist, ISRC when available, and duration
RemasterDifferent masteringYear, edition label, and runtime
Clean or explicit editLyrics differContent rating and title suffix
Radio editShortened arrangementDuration and release name
Live, acoustic, or remixDifferent performanceVersion words, album, artist, and duration
  1. Confirm the complete source title, artist credit, album, and version markers.
  2. Search Apple Music manually with artist plus core title, then inspect alternate releases.
  3. Compare duration, content rating, featured artists, and version labels.
  4. Approve an alternate edition only when it fits the playlist’s purpose.
  5. Leave the row out when the evidence is weak; add it manually later if a correct recording becomes available.
Accuracy beats completeness

A smaller honest playlist is easier to repair than a complete-looking playlist filled with convincing but incorrect versions.

06 · Verification

Check what actually arrived in Apple Music

A successful creation response confirms that a destination exists. It does not prove perfect catalog equivalence. Check the new playlist while the report and source are still easy to compare.

CountWhat it means
Spotify totalEverything Spotify reports, including rows that may not be publicly readable or transferable
Readable tracksMusic rows available to the public preview
Analyzed tracksRows included in Full, 150-track, or 50-track scope
Ready + approved ReviewRows eligible for playlist creation
Created tracksApple Music catalog items accepted into the destination
  1. Keep the receipt. Record transferred, skipped, and missing totals before closing the browser tab.
  2. Compare the right counts. Do not compare only Spotify’s headline number with Apple Music’s final total.
  3. Spot-check versions. Prioritize live, acoustic, remix, remaster, clean, explicit, radio edit, soundtrack, and compilation rows.
  4. Verify order landmarks. Compare the first songs, a recognizable middle group, and the final songs.
  5. Keep intentional duplicates. Repeated source rows can be meaningful and should not be removed blindly.
  6. Repair omissions cautiously. Search manually and listen before adding an alternate edition.
  7. Test playback. Use the destination device and account to catch unavailable, restricted, or greyed-out catalog items.

If creation stopped after matching, restore the saved report in the same browser, reconnect Apple Music, and retry creation. Start a new analysis only when the source, scope, storefront, or report evidence was wrong.

07 · Common questions

Frequently asked questions

Does PlaylistXfer require a Spotify login?

No. The web flow reads normal public Spotify playlist and song links without asking for Spotify credentials.

Can PlaylistXfer read private Spotify playlists?

Not reliably. If a playlist cannot be viewed in a signed-out browser, the public-link flow usually cannot read it. Change visibility only if you own the playlist and are comfortable making it public.

When is Apple Music permission requested?

Only at the create step, after the public preview, catalog matching, and human review are complete.

Does PlaylistXfer modify the Spotify playlist?

No. It reads public source metadata and creates a separate Apple Music playlist after authorization. It cannot edit, delete, reorder, follow, or unfollow Spotify content.

Why are some songs missing?

Catalog availability, local files, regional rights, different editions, or ambiguous metadata can prevent a safe automatic match. Missing rows stay out instead of receiving a forced substitute.

Can I transfer more than 500 tracks?

One current web analysis handles up to 500 rows. Split a larger source into clearly named sections and transfer each section separately.

Will PlaylistXfer preserve order and exact versions?

Approved tracks are created in source order, with gaps closed around skipped rows. Exact recording versions still require review and a post-transfer spot check.

What data is stored?

Temporary reports and review decisions can be stored so a session survives a refresh. Anonymous reports normally expire after about seven days and in-progress jobs sooner. Apple Music user tokens are not designed to be stored in the transfer database. See the Privacy Policy.

Is PlaylistXfer affiliated with Spotify or Apple?

No. PlaylistXfer is an independent interoperability project. The service names describe the source and destination only.

How do I contact PlaylistXfer support?

Use the contact page. Include the failed step, visible error, approximate time, browser, and whether the Spotify link worked while signed out. Do not send account credentials or tokens.

08 · Evidence

Production evidence and deeper reading

These pages remain separate because they document reproducible tests or a distinct technical method rather than repeating the general workflow.

PlaylistXfer is independent and is not affiliated with, endorsed by, or sponsored by Spotify or Apple. Catalog availability, account features, and service terminology are controlled by their respective providers.