After migrating your Mastodon account to a new instance, you might discover that the new server does not meet your expectations. The old account gets disabled during migration, and the process cannot be reversed through the user interface. This article explains the limitations of Mastodon account migration and the practical steps to regain access to your original account or restore your online presence. You will learn what happens to your old and new accounts during and after migration, and how to recover your original identity without losing followers.
Key Takeaways: Reversing a Mastodon Account Migration
- Preferences > Account > Move from a different account: Initiates the migration handshake from the new instance back to the old one.
- Redoing the migration in reverse: The only supported method to transfer followers back to the original account.
- Manual server intervention: Required only if the old instance deleted your disabled account after a 30-day grace period.
Why Mastodon Migration Cannot Be Undone Like a Backup
Mastodon migration is a one-way handshake between two instances. When you initiate a move, your old account posts a redirect notice to its followers. The old profile is locked and marked as moved. You cannot simply click an undo button because the migration protocol is designed to prevent account theft and spam. The old account is not deleted immediately, but it becomes read-only. You can log in to it only if you have not set a new password on the new instance that overrides the old login. The migration does not transfer posts, media, or direct messages. It only moves follower relationships and a short redirect notice.
The only way to reverse a migration is to perform a second migration from the new account back to the old account. This is technically identical to the first migration, but in the opposite direction. The original account must still exist and be accessible. If the old instance has already deleted your account after the default 30-day grace period, you cannot reverse the migration through normal means. You would need to contact the old instance admin to restore the account from a database backup.
What Actually Happens During a Migration
When you start a migration from Account A to Account B, Account A posts a special activity to its followers. Followers on other instances see a notice that you moved to Account B. Account A then becomes locked. You can still log in to Account A, but you cannot post or change settings. Account B becomes your active account. If you ever want to move back, you must start a new migration from Account B to Account A. The old Account A must be unlocked and writable again. Mastodon does not have a rollback feature because the migration is designed as a permanent transfer of trust.
Steps to Reverse a Mastodon Migration by Redoing It
To roll back a migration, you must perform a standard migration from the new instance back to the original instance. This works only if the original account is still available and not deleted. Follow these steps exactly.
- Log in to your original account on the old instance
Open the old instance URL and sign in with your original username and password. If you cannot remember the password, use the Forgot Password link on the old instance login page. The old account is locked but still accepts logins. - Generate a migration alias on the original account
Go to Preferences > Account > Move from a different account. Click Generate an alias. Copy the alias string. This step tells the original instance that you plan to move followers from another account to this one. - Log in to your new account on the new instance
Open the new instance URL and sign in with the account you migrated to. This account is currently active. - Initiate the reverse migration from the new account
Go to Preferences > Account > Move to a different account. Paste the alias you copied from the original account. Enter your original account password. Click Move Followers. The new instance will post a migration notice to your followers, telling them you are moving back to the original account. - Wait for the migration to propagate
Follower migration can take several minutes to a few hours. Your old account will become unlocked and writable again. Your new account will be locked and marked as moved. You can now use your original account normally.
If the Reverse Migration Fails or the Original Account Is Deleted
Original Account Was Deleted After the Grace Period
Mastodon instances automatically delete accounts that have been disabled by migration after a configurable grace period, typically 30 days. If the old instance removed your account, you cannot log in to it. You cannot reverse the migration. You must contact the admin of the old instance and ask them to restore the account from a database backup. Most instances keep backups for a limited time. Provide your original username and the approximate date of migration. The admin can re-enable the account and reset the password. After restoration, follow the steps above to migrate back.
New Instance Blocks the Reverse Migration
Some instances block outgoing migrations to prevent abuse. If the new instance does not allow moving to a different account, you cannot initiate the reverse migration from that account. You must contact the new instance admin and request an exception. Explain that you need to move back to your original instance. The admin can temporarily lift the block or manually transfer followers using the admin panel. If the admin refuses, you cannot reverse the migration through normal means. You can create a new account on the original instance and manually ask followers to follow you again, but this is not a true rollback.
Migration Alias Expired or Was Not Created
The migration alias is a one-time token. If you generated an alias on the original account but did not use it within a short time, the alias might expire. Regenerate a new alias by repeating step 2 above. If you never created an alias on the original account before migrating, you cannot reverse the migration. The alias must exist on the original account before the new account can initiate the move. Without an alias, the new instance will reject the migration request. You must create the alias on the original account first, then start the reverse migration from the new account.
Mastodon Migration vs Manual Account Recovery
| Item | Reverse Migration | Manual Account Recovery |
|---|---|---|
| Follower transfer | Automatic through ActivityPub | Manual, followers must refollow |
| Post history | Not transferred in either direction | Not preserved unless the old instance kept the content |
| Original account state | Must exist and be unlocked | Can be deleted, but you lose followers |
| Time required | Minutes to hours | Days to weeks |
| Admin involvement | Only if the account was deleted or migration is blocked | Required to restore deleted account |
Manual account recovery means creating a brand new account on your original instance and asking each follower to follow the new profile. This is the fallback when reverse migration is impossible. It requires you to post a pinned message with your new account link and wait for followers to notice. This method is slow and unreliable compared to a proper reverse migration.
To avoid this situation in the future, test a new instance by creating a secondary account before committing to a migration. Use the secondary account for a few weeks to evaluate the instance rules, moderation, and uptime. Then perform the migration only when you are confident the new instance meets your needs. The reverse migration process is the same as the original migration, but you must always have access to the original account and its password. Keep your original account password saved in a password manager even after migration. If you change the password on the new instance, the original account password remains unchanged and can still be used for future reverse migrations.