Post migration service for federated social networks
Built for fediverse users switching instances.
“#177 – Support Account Migration – was closed after implementing follower migration, but this is only one small part of a true migration. To really be able to c…”
The receipts — real demand
“#177 – Support Account Migration – was closed after implementing follower migration, but this is only one small part of a true migration. To really be able to change instances, you need to be able to take your posts with you. There was some good discussion on this over there; I'm opening a new issue to make it clear that this is a separate concern from that issue, which seemed to evolve into only being about follower…”
Full dossier
Unlock the full dossier — free
Every corroborating quote, the source receipts, and the community echo. One email, no payment.
Why this is a gap
Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.
The market
Fediverse users switching instances need post-migration support (data, followers, metadata transfer). Zero search volume reflects a tiny, niche user base; adoption depends entirely on fediverse growth.
Competition & the opening
1/10 competition with no named solutions means the space is open, but existing platforms (Mastodon, etc.) handle basic follower migration—the gap is in migrating posts, DMs, and metadata across federation boundaries.
What's hard to build
Different fediverse implementations use different data schemas and federation protocols; guaranteeing data integrity and consistency across ActivityPub servers, handling rate limits, and managing state during migration is architecturally hard.
Why now
Mastodon and ActivityPub adoption is accelerating lock-in concerns, making true data portability a user expectation.
How you'd monetize
per-migration $9-29 or premium instance $5/mo