Tech Migrations the Spotify Way: A Three‑Step Strategy to Reduce Fragmentation

Technical upgrades often start fast but can stall, leaving legacy fragments behind. Spotify reflects on this problem and outlines its thinking and upcoming actions.

Engineering culture matters. With over 300 engineers organized into squads worldwide, Spotify emphasizes motivation over punishment and uses creative communication to highlight the efficiency gains from migrations.

Historical context. In 2017, internal teams sent mass emails about deprecations, causing information overload and confusion, prompting a reassessment of the migration process.

Three‑step migration strategy.

1. Prioritize. Create a migration map of all systems, collaborate with the Technical Architecture Group (TAG) to rank priorities, assess costs, identify impacted people, and set clear deadlines. This reduces unnecessary workload and replaces noisy emails with an open‑source tool that shows current and future migration plans.

2. Productize migration.

Assign a dedicated product manager to each migration (responsibility owner), conduct alpha/beta testing before adding to the map, provide targeted training, and communicate benefits from productivity, cost, and scalability perspectives. Collaboration with PMMs ensures clear value messaging.

Understand users to tailor plans, and visualize progress via a plugin (Tech Insights) that shows tribe‑ and squad‑level migration status.

3. Automate. Aim for maximal automation so engineers rarely notice underlying component changes; where full seamlessness isn’t possible, generate automatic PRs for review and merge.

The ultimate goal is to hide 99% of infrastructure migrations from engineers, providing higher‑level tools that keep the tech stack clean and reduce long‑term technical debt.

Original article: https://engineering.atspotify.com/2020/06/25/tech-migrations-the-spotify-way/