Seamless Account Portability Across Servers

This is Bluesky’s clearest break from traditional social networks, because the account is not the server. A user’s posts live in a personal repository, and the account’s long term identifier points to whichever Personal Data Server currently hosts that repository. When the user moves servers, the DID stays the same, the repo can be reimported, and the wider network can keep treating that person as the same account rather than a new profile.

• The technical trick is that identity and storage are split apart. The PDS stores the repo, but the DID document is the source of truth for where that repo lives. Updating that pointer lets the same account identity follow the user to a new host.
  1 atproto 3 atproto
• This is stronger portability than Mastodon offers today. Mastodon can move followers to a new account, but it does not move posts or media, and users still have to create a replacement account first. Bluesky is designed so the account itself migrates, not just the audience.
  4 joinmastodon
• In practice, Bluesky is still early in making this seamless. Official documentation says migration has worked between non Bluesky hosts and away from Bluesky’s PDS, and as of September 26, 2025 users can also migrate back to Bluesky’s PDS. That matters because portability only changes behavior when users trust it will work both ways.
  2 bsky 5 bsky

Over time, this pushes social apps toward competing on product quality instead of account lock in. If more PDS hosts, clients, and media companies adopt AT Protocol, Bluesky’s network can become more like email, where switching providers is painful but possible, and much less like X, where leaving usually means starting over from zero.