Bounce launches tool to migrate Bluesky accounts to Mastodon

Bounce brings cross‑protocol migration to the open social web

Bounce, created by the nonprofit A New Social, launches a public beta that finally lets users move follow graphs from AT Protocol-based Bluesky to ActivityPub networks such as Mastodon and Pixelfed. The tool addresses a long-standing portability gap between competing decentralized social standards.

Under the hood, Bounce reuses technology from Bridgy Fed to create a bridged account that lives across the two ecosystems. It first migrates a Bluesky identity onto that bridge and then transfers the follow graph onto the user's ActivityPub account, translating relationships and visibility between different protocols.

At launch Bounce supports only Bluesky→Mastodon/Pixelfed moves. The limitation comes from Bluesky’s current tooling, which allows moving off a PDS but not back on. Practically, that means once you leave Bluesky you can no longer use your Bluesky credentials to sign into AT Protocol services until Bluesky enables inbound migrations.

The timing is notable: Bluesky recently blocked access for users in Mississippi rather than comply with a state age‑assurance law it deemed invasive. For impacted users, Bounce offers a practical escape hatch to preserve social graphs and continuity when platform access is cut off by policy or geoblocking.

Early adopters should proceed with caution: test the migration flow, back up account data where possible, and understand that some linked services or credentials may break after the move. The beta is aimed at enthusiasts and developers who can provide feedback as the tooling matures.

What Bounce means for apps, organizations, and dev teams:

• Portability becomes practical: users can preserve follower networks when switching platforms.
• Protocol translation is feasible but partial: expect one‑way moves until upstream platforms add symmetric migration APIs.
• Policy shocks matter: geobans or regulation can make account portability a user safety feature, not just convenience.

For product teams and platform operators, Bounce is a reminder to design for data portability and to publish migration endpoints before users are forced to flee. For developers, the tool is a practical example of translating identity and graph data between incompatible protocols—useful reference code for future interoperability work.

QuarkyByte’s approach to scenarios like this is analytical and operational: we map the follow graph transformations, simulate credential and session fallout, and produce migration runbooks that limit downtime. Whether you’re a media brand preserving followers or a public agency assessing legal exposure, these actions reduce risk and maintain reach.

Bottom line: Bounce makes an important piece of the open social web usable in practice by giving users a way to move their social graphs across protocol boundaries. It’s a beta and imperfect, but it signals momentum toward user control, portability, and a more resilient decentralized social ecosystem.

If you’re considering a move, treat the migration like a project: inventory linked accounts, test with a non‑critical identity, and plan for irreversible steps before you commit.