When you initiate a Mastodon account migration from an old instance to a new one, the process normally transfers your followers and profile settings. If the source account gets suspended after you start the migration, your followers may not complete the move. This situation leaves you with a partially migrated account and a locked source profile. This article explains why a suspension during migration blocks the transfer and provides the exact steps to recover your follower list.
You will learn how to identify the failure, contact the right instance administrators, and manually re-follow users from your new account. The core problem is that a suspended account cannot send the final migration confirmation packet to the new instance. Without that handshake, the new account never receives the follower list.
Understanding this mechanism helps you avoid permanent follower loss. By following the instructions below, you can restore your connections even if the source instance refuses to reinstate your old account.
Key Takeaways: Recover Followers After Source Account Suspension
- Preferences > Account > Move from a different account: Initiates the follower migration handshake from the new account to the suspended source account.
- Instance admin contact form or email: Request unsuspension or a manual data export of your follower list from the suspended account.
- Manual re-follow via CSV export: Upload a CSV of your old followers to a Mastodon-compatible tool or manually follow each user from the new account.
Why a Suspended Source Account Blocks Follower Migration
Mastodon account migration relies on a two-way handshake between the source instance and the target instance. When you start a migration from the source account, the source instance creates a migration record and sends a verification request to the new account. The new account then confirms the move, and the source instance pushes the follower list to the target instance.
If the source account is suspended after the initial migration request but before the final confirmation, the handshake breaks. A suspended account cannot send outbound API calls, including the final migration packet that contains the follower list. The target instance waits indefinitely for this packet, so the followers never appear on the new account.
Suspensions happen for several reasons:
- Violation of instance rules, such as posting prohibited content.
- Automated spam detection flags the account.
- The instance admin suspends the account during a routine moderation sweep.
In all cases, the migration process halts at the same point: the final confirmation step never completes.
Steps to Recover Followers After Source Account Suspension
Follow these steps in order. Do not skip any step, because each one builds on the previous result.
- Check the migration status on the new account
Log into your new Mastodon account. Go to Preferences > Account. Look for a section labeled “Move from a different account” or “Migration status.” If you see a message like “Waiting for confirmation from the old account,” the handshake is incomplete. If you see no migration entry at all, the initial request never reached the new instance. - Contact the source instance admin
Find the admin contact method for the instance where your old account was suspended. Most instances list an email address or a contact form on their About page. Send a polite message explaining your situation: you started an account migration, the account was suspended, and the migration cannot complete. Request either unsuspension for 10 minutes or a manual export of your follower list as a CSV file. If the admin agrees to unsuspend, go to step 3. If they provide a CSV, skip to step 5. - Log into the unsuspended source account
If the admin unsuspends your old account, log in immediately. Go to Preferences > Account > Move to a different account. Re-enter the migration alias (the handle of your new account) and click Submit. This action triggers a fresh handshake. - Confirm the migration on the new account
Switch to your new account. Go to Preferences > Account. Under “Move from a different account,” you should see a confirmation prompt. Click Accept or Confirm. The follower list will transfer within 5 to 10 minutes. If the admin re-suspends the old account after you confirm, the transfer still completes because the final packet was already sent. - Manually re-follow users from a CSV export
If the admin provides a CSV file of your followers, download it. The CSV contains the account handles (user@instance) of everyone who followed your old account. Use a third-party tool like Mastodon Followers Importer or manually copy-paste each handle into the search bar on your new account and click Follow. For large lists, use a script or browser extension that automates the process. Do not import more than 50 followers per minute to avoid rate limiting. - Delete the failed migration record
After you have manually re-followed everyone, go to your new account Preferences > Account. If the old migration entry still shows as pending, click Cancel or Remove. This clears the stale record and prevents future confusion.
If the Source Instance Admin Refuses to Help
Some instance admins will not unsuspend an account or provide a CSV export. In that case, you have two remaining options.
Re-follow from memory or external lists
If you remember the handles of your most important contacts, follow them manually from your new account. Use the Mastodon search bar and type their full handle (username@instance). This method works best for accounts with fewer than 100 followers.
Use a cached follower list from third-party services
If you used a Mastodon client app like Tusky, Fedilab, or Mona, check if the app cached your follower list. Some apps store follower data locally. Export that data as a CSV or text file and import it into your new account using the same manual or automated method described in step 5.
Comparison Table: Recovery Methods for Suspended Source Accounts
| Item | Admin Unsuspension | Admin CSV Export | Manual Re-follow |
|---|---|---|---|
| Success rate | High if admin cooperates | High if admin exports correctly | Low for large follower counts |
| Time required | 10 minutes after unsuspension | 30 minutes to 1 hour | 2 hours or more for 500+ followers |
| Follower loss risk | Minimal | Minimal | High if you forget handles |
| Admin dependency | Full | Partial | None |
If the admin unsuspends your account, the migration completes with no follower loss. If they only provide a CSV, you lose no data but must import it manually. Manual re-following without any admin help risks losing followers whose handles you cannot recall.
After you recover your followers, consider updating your new account profile with a link to the old account. This helps any followers who missed the migration find you. Also, export your new follower list regularly from Preferences > Import and Export > Export data to avoid losing data in future migrations.
One advanced tip: before starting any future migration, export your follower list from the source account first. Store the CSV file locally. If the source account gets suspended during the migration, you can import that CSV without relying on the admin at all.