TL;DR: As part of our efforts to streamline service management and improve developer experience, our engineering org migrated from a legacy service catalogue to the Backstage Software Catalog. In this post, I'll share what we learned from that journey --- including how to build an automated script to migrate services from an existing internal service catalogue to a modern internal developer portal (IDP) like Backstage. I'll also outline strategies to help drive adoption across your organization, along with tips for addressing both the cultural and technical roadblocks you might encounter along the way.

Backstage

A comprehensive guide detailing the migration from legacy service catalogs to Backstage, covering automated migration scripts using GitHub Apps, JWT authentication, and Base64 processing. The post explores adoption challenges including team resistance and lack of understanding, along with strategies like clear roadmaps, personalized demos, and feature additions such as Tech Radar and linter plugins. Key technical aspects include creating catalog-info.yaml files, using entity providers, and implementing scaffolders for streamlined service management.

Migrating legacy services to a modern developer portal: A technical guide to Backstage integration

Why and How a Modern Developer Portal Was Rolled Out ​

GitHub Requests Architecture for Migration ​