Portability
Moving between Mastodon servers
Mastodon supports account redirects and follower migration, but a move is not a perfect copy. Plan it while both accounts and servers are still available.
Create and prepare the destination
First create an account on the new server and read its policies. From the new account, set up an alias that points back to the old account. Then initiate the move from the old account by identifying the destination and confirming credentials. The exact interface can change, so follow the current official account migration documentation.
Know what follows you
A move can direct visitors from the old profile to the new one and request that followers follow the destination. Following relationships can take time to update across servers. The old account becomes marked as moved, but it still matters as the verifiable origin of the migration.
Posts and media do not automatically become posts on the new account. Other settings and relationships may require separate CSV exports and imports. Lists, blocks, mutes, bookmarks and follows have different handling, and software versions may affect available options. Read the import screen before assuming an export category will merge exactly as expected.
Export before an emergency
Use Mastodon’s data export tools periodically, not only after closure is announced. Keep copies somewhere you control and inspect what each file contains. Exports improve resilience but are not a complete, portable clone of a social identity.
If the old server is already gone
A formal migration usually cannot be completed without access to the old account. You may create a new account and announce it through channels you still control, but followers must verify and reconnect manually. Avoid claiming that an unrelated replacement profile is an official continuation without proof.
Server choice and backups reduce the impact of closure, but decentralisation does not make individual services immortal. Portability works best as a routine practice.