API-first migration workflow for moving YouTube Music liked songs into Spotify Liked Songs with a review step instead of blindly accepting fuzzy matches.
Developed by Sammy The Femboy Puppy · creator/development portfolio
SyncifyX combines:
- Google OAuth for YouTube Data API access
- Spotify OAuth for library and playlist operations
- Postgres persistence
- title/artist parsing
- Spotify track search
- confidence scoring
- a review UI
- batched imports
Current UI capabilities include:
- selectable YouTube sources
- selectable Spotify destinations
- theme presets
- adjustable batch sizes
- all-mode matching
- queue sorting
- optional AI-assisted parsing
- per-song best-match refresh
Install dependencies:
npm installCopy:
.env.example
to:
.env.local
and configure the required OAuth and Postgres values.
Enable the YouTube Data API v3 in Google Cloud Console and add this local callback:
http://127.0.0.1:3000/api/auth/google/callback
Add this callback in the Spotify Developer Dashboard:
http://127.0.0.1:3000/api/auth/spotify/callback
npm run devFor OAuth credential creation, GitHub push steps, and deployment notes:
Release history:
Planned migration and matching work:
YouTube Music does not expose a complete standalone public API for every Music-specific feature. SyncifyX uses authenticated YouTube Data API playlist data, includes the LM liked source, and can list the authenticated user's YouTube playlists as selectable sources.
That limitation is part of the design and should be considered when evaluating coverage.
Accepted matches can be saved directly to Spotify Liked Songs using user-library-modify.
The current workflow:
- saves liked tracks in batches of 50
- can optionally export to a playlist
- can create
Imported YouTube Likes - can add to an existing playlist
- batches playlist additions in groups of 100
- includes retry handling for
429responses
Migration tools can silently make a large library worse when confidence is treated as certainty.
SyncifyX is designed around:
source item
-> parse
-> search
-> confidence
-> review
-> accepted destination item
The review layer is intentional.
Do not commit OAuth client secrets, access tokens, refresh tokens, database credentials, or .env.local.
Production deployments should use properly configured callback origins, durable secret storage, and the least OAuth scope required for the selected workflow.
SyncifyX is developed by Sammy The Femboy Puppy (@foulfoxhacks).
The broader developer/creator portfolio is available at akasammythepuppy.me/work/.