Moving your Mastodon account from one instance to another allows you to keep your followers and profile history without starting from scratch. The migration process uses Mastodon’s built-in account relocation feature, which transfers your followers, profile metadata, and a redirect notice to your new account. This article explains the prerequisites for migration, provides step-by-step instructions for the move, and covers common pitfalls to avoid.
You will learn how to export your data, set up a new account, and initiate the follower transfer from your old account. The process takes about 30 minutes to complete and requires access to both accounts.
Key Takeaways: Mastodon Account Migration
- Preferences > Import and Export > Export: Download your followers list, lists, and mute/block data before leaving the old instance.
- Preferences > Account > Move from a different account: Initiate the follower migration handshake after setting up the new account.
- Old account profile redirect: After migration, the old profile displays a notice pointing visitors to your new account for 30 days.
What Happens During a Mastodon Account Migration
Mastodon migration transfers your followers, profile display name, bio, avatar, and header image from the old account to the new one. Your old posts, direct messages, and media files do not move. The old account remains accessible but shows a redirect banner to your new profile for 30 days. After that period, the old account can be deleted or left as a static archive.
The migration works by creating a handshake between the two accounts. The old account sends a relocation request to the new account, which then sends follow requests to all followers on the old account. Followers on the same instance as the old account are automatically moved. Followers on other instances must approve the follow request manually if their instance requires approval.
Prerequisites for Migration
Before you start, you need:
- A new Mastodon account on a different instance. The new account must have a different username than the old one.
- Access to the email address associated with the old account to receive confirmation messages.
- The old account must not be suspended or limited by its instance admin.
Steps to Migrate Followers Between Mastodon Instances
Follow these steps in order. Do not skip the export step, as it preserves your lists and blocks.
- Export your data from the old account
Log in to your old Mastodon account. Go to Preferences > Import and Export > Export. Click the Export button for each category: Follows, Lists, Mutes, Blocks, and Domain Blocks. Save each CSV file to your computer. - Set up your new account
Create a new account on your chosen instance. Complete the signup process and verify your email address. Set your display name, bio, avatar, and header image to match your old account if desired. - Import data into the new account
On the new account, go to Preferences > Import and Export > Import. Upload the Follows CSV file. The import will send follow requests to every account in the file. Repeat for Lists, Mutes, Blocks, and Domain Blocks CSV files if you want to preserve those settings. - Generate the migration key on the new account
On the new account, go to Preferences > Account > Move from a different account. Click Generate a migration key. Copy the displayed key. This key expires after 30 minutes. - Enter the migration key on the old account
Log back into the old account. Go to Preferences > Account > Move to a different account. Paste the migration key into the field. Enter your old account password and click Move followers. The old account immediately shows a redirect notice on its profile. - Confirm the migration
Check the new account after a few minutes. You should see a notification that followers have been moved. Followers on the same instance as the old account appear automatically. Followers on other instances may take up to 24 hours to arrive, depending on how fast their instance processes the follow request.
If Mastodon Migration Stalls or Fails
Migration Key Expired Before You Could Use It
If the migration key expires, the old account will reject the move request. Generate a new key on the new account and repeat step 5 within 30 minutes. The old account does not need to undo anything before trying again.
Followers Did Not Transfer After Migration
Followers may not transfer if the new account has a different username than the old one. Mastodon requires the username to match for automatic follower migration. If the usernames differ, you must manually ask your followers to follow the new account. Also check that the old account is not set to private or locked, as locked accounts prevent the migration handshake.
Old Account Shows Error During Migration
An error on the old account usually means the migration key was mistyped or expired. Clear the field and refresh the page. Generate a fresh key on the new account and paste it carefully. If the error persists, contact the old instance admin to verify that account relocation is enabled on that server.
| Item | Old Account | New Account |
|---|---|---|
| Posts and media | Stay on the old instance | Not transferred |
| Followers | Sent follow requests to new account | Receive followers from old account |
| Profile redirect | Shows notice for 30 days | No redirect needed |
| Lists and blocks | Must export manually | Import CSV files |
After migration, your old account remains active but shows a redirect banner. You can delete the old account after 30 days by going to Preferences > Account > Delete account. Before deleting, verify that all your followers have moved. Use the new account’s follower list to confirm the count matches your expectations.
For a smooth migration, generate the migration key only when you are ready to complete the move immediately. The 30-minute expiry window prevents accidental or unauthorized migrations. If you manage multiple accounts, repeat the entire process for each account separately.