Portal Migration

Migrate to Spotify Portal without disruption

Spotify Portal is the SaaS, Spotify-managed edition of Backstage, built and operated by the same engineers who created and open sourced Backstage.

Accelerate developers without managing infrastructure full-time

We handle the migration and the unglamorous operational work, so your platform team can stay focused on building new developer experiences and adopting the capabilities Spotify uses internally.

Backstage without the maintenance

Running Backstage at scale is hard: upgrades break, plugins drift, and security patches never stop. Spotify Portal handles it, so your team can focus on higher-impact work.

Upgrades on autopilot

Always aligned with upstream open source Backstage

No infrastructure to run or scale

We handle reliability, security, and availability

Stable by design

No breaking changes, no fire drills, no rollbacks

How the industry builds like Spotify

Having engineers on the ground actually be your supporters and say, 'Yeah, I adopted this and it has totally changed the game for me' — hearing those messages from two different angles and from two different perspectives is really huge.

Brian Wolowicz

Director of Experience Design, Capital One

I did an evaluation on the open-source Backstage before choosing Portal. We use Portal. We wanted to deliver the value of Backstage rather than Backstage itself. And that’s where Portal clicked in for us.

2K Games

This platform is allowing us to actually surface information that hasn’t been possible in the past, which is super exciting, all within the context of their applications and their components.

Brian Wolowicz

Director of Experience Design, Capital One

Your platform, professionally operated

Spotify Portal is run in a dedicated single-tenant environment, so your plugins and integrations work as expected. We migrate what you already have into a supported setup — you keep your platform team, just not the burden of running the platform.

A Venn diagram connecting Backstage and Spotify Portal for Backstage

Custom plugins stay first-class

Your plugins remain real, versioned code that you own, not extensions trapped behind a UI.

Portal Studio as your foundation

We migrate your existing custom plugins into your private Portal Studio mono-repo, giving you a clean, supported home going forward.

Same flexibility, fewer pitfalls

You keep control over how your platform evolves, without carrying infra, upgrade, or compatibility risk.

What the migration actually looks like

Our engineers do the heavy lifting across each step. Your team stays productive and can start focusing on what’s next, not the migration itself.

  1. Identity & access (foundation)

    01

    We set up SSO, teams, and users so Portal reflects your org from day one.

    • IDP integration
    • Team and ownership mapping
    • Access validated early to avoid surprises
  2. 02

    We migrate your Backstage catalog and connect it to your identity model.

    • Services, APIs, components, data, and metadata preserved
    • Ownership and relationships maintained
    • Familiar experience the first time engineers log in
  3. 03

    We port and validate the open-source plugins you already rely on.

    • Plugin configs migrated from your OSS
    • Integrations tested (CI/CD, SCM, cloud, observability, etc.)
    • Gaps flagged early with clear remediation paths
  4. Secure connectivity (Private Connect)

    04

    Need access to tools behind your firewall? We set up Portal Private Connect.

    • Deploy a secure, scoped agent
    • Whitelist only the network access you explicitly approve
    • Validate connectivity end-to-end
  5. Custom plugin migration

    05

    We migrate your custom plugins into Portal Studio.

    • Plugins extracted from your existing Backstage repo
    • Moved into your private Studio mono-repo
    • Built, deployed, and validated in Portal

Clear ownership, no lock-in

Spotify Portal stays aligned with open source Backstage, so you always retain an exit path.

You own

  • Plugins and source code
  • Catalog and data
  • Integrations and identity model

We own

  • Infrastructure and scaling
  • Upgrades and compatibility
  • Security, reliability, and availability

What your team can focus on instead: “The Spotify Way”

While we handle migration and operations, your team can start adopting the same tools we use internally at Spotify without waiting for the move to finish.

Ready to hand over the grunt work?

Let Spotify run the infrastructure so your team can focus on building “the Spotify way.”