When a Mastodon instance shuts down unexpectedly, users lose access to their account, followers, and data. The standard migration process requires both the old and new instances to be online to transfer followers through the ActivityPub handshake. If the old instance goes offline before you complete the migration, your followers cannot be automatically moved. This article explains how to recover your Mastodon presence when the old instance is no longer accessible, including manual steps to rebuild your network and export whatever data remains.
Key Takeaways: Recovering Mastodon Account After Instance Shutdown
- Export account archive before the instance goes dark: Contains your posts, media, and follow lists — the only offline backup Mastodon provides.
- Announce new account from a trusted profile: Use a friend’s post or a pinned toot on the old profile if the instance still responds.
- Manually re-follow users from the archive: No automated migration is possible when the old instance is offline — you must rebuild your follow network by hand.
Why Automatic Follower Migration Fails When the Old Instance Is Offline
Mastodon’s follower migration feature relies on a two-way communication handshake between the old instance and the new instance. When you initiate a move from Preferences > Account > Move from a different account, the new instance sends a verification request to the old instance. The old instance must respond with a confirmation that the account exists and that you control it. If the old instance is offline, this handshake cannot complete, and the migration fails silently.
Additionally, Mastodon does not cache follower lists or account data on the new instance before the migration completes. There is no queue or retry mechanism for pending migrations. Once the old instance stops responding, the new instance discards the migration request entirely. The only way to recover is to manually rebuild your network.
Instance shutdowns happen for several reasons: the admin stops paying the server bill, the server hardware fails, or the admin abandons the project. Unlike centralized platforms, Mastodon instances are independently operated, and no central authority can force data recovery. Users must take proactive steps to preserve their data before the instance disappears.
Steps to Recover Your Mastodon Account After Instance Shutdown
The recovery process depends on whether you still have any access to the old instance — even read-only access. The steps below assume the old instance is completely offline and unreachable. If the instance still loads a static page or read-only timeline, adapt accordingly.
Step 1: Export Your Account Archive If the Instance Still Responds
- Log in to your old instance
If the instance is still online but about to shut down, log in immediately. Go to Preferences > Import and Export > Export. Click Request your archive. Mastodon generates a .tar.gz file containing your toots, media, and follow lists. Download this file to your local computer. - Save your follow lists separately
While still logged in, open Preferences > Import and Export > Export. Click CSV next to Following list. This downloads a CSV file with the account URLs of everyone you follow. Save this file — it is the only way to know whom to re-follow later. - Copy your profile URL
Write down or copy the full URL of your old profile, for examplehttps://oldinstance.social/@yourusername. This URL is essential for announcing your new account and for others to verify your identity.
Step 2: Create a New Account on a Different Instance
- Choose a stable instance
Select an instance with a proven uptime record and active moderation. Avoid single-admin instances. Popular choices include mastodon.social, fosstodon.org, and hachyderm.io. Sign up for a new account. - Set up your new profile
Fill in your display name, bio, and avatar to match your old profile. In your bio, add a line like Formerly at @yourusername@oldinstance.social so people can verify your identity.
Step 3: Announce Your New Account
- Post from a friend’s account
Ask a trusted friend on Mastodon to post a toot announcing your new account. Include your old profile URL and your new profile URL. This creates a verifiable link between your identities. - Pin a toot to your old profile if possible
If the old instance still accepts new toots but is about to shut down, log in and pin a toot with your new account URL. Pinned toots appear at the top of your profile and are visible to anyone who visits the old page. - Use the Web Archive
If the old instance is completely offline, check the Wayback Machine at archive.org. If someone archived your profile page, you can use that archived URL as proof of your old identity.
Step 4: Rebuild Your Follow Network Manually
- Import your following CSV
If you saved the CSV file earlier, go to Preferences > Import and Export > Import on your new instance. Under Import type, select Following list. Upload the CSV file. Mastodon will attempt to follow each account listed. Accounts that no longer exist or are on defunct instances will be skipped. - Re-follow manually for missing accounts
Accounts that failed to import may still be active on other instances. Use the search bar on your new instance to find each account by its full handle (for example,@friend@otherinstance.social). Follow them individually. - Notify your followers
There is no way to automatically notify your old followers that you have moved. Post a toot from your new account explaining the situation. Ask your friends to boost the toot. Over time, your followers will find you through boosts and mentions.
If Mastodon Migration Still Fails After Instance Shutdown
Followers Lost After Instance Goes Offline
When the old instance disappears, your followers on that instance also lose their accounts. They cannot follow you to the new instance because their own accounts are gone. If you know some of your followers personally, contact them through other means — email, another social platform, or a shared community — and tell them your new Mastodon handle.
Cannot Export Archive Because Instance Is Already Offline
If the instance is completely offline and you never exported your data, all your toots, media, and follow lists are lost. There is no way to recover them. The only option is to start fresh with a new account. To prevent this in the future, set a recurring calendar reminder to export your archive every 30 days.
Old Instance Returns After Migration Attempt
In rare cases, an instance may come back online after a temporary outage. If you already created a new account and the old instance returns, you can then perform a standard follower migration. Log into the old instance, initiate the move to your new account, and the handshake will complete. Your followers will be transferred automatically.
Mastodon Migration Options: Online vs Offline Instance
| Item | Old Instance Online | Old Instance Offline |
|---|---|---|
| Follower migration | Automatic via Move from a different account | Not possible — followers must be manually notified |
| Data export | Full archive available | No export possible |
| Follow list transfer | CSV export and import | Only if CSV was saved earlier |
| Identity verification | Automatic handshake | Manual via friend posts or archived profile |
| Time required | Minutes | Days to weeks |
When the old instance is online, the entire migration process takes less than 10 minutes. When it is offline, recovery can take days or weeks because you must manually rebuild your network and notify each follower individually.
To protect yourself from future instance shutdowns, always keep an up-to-date export of your account archive and follow list. Store the CSV file in a cloud drive or on your local machine. Set a monthly reminder to re-export. If you run your own instance, enable automatic backups through your server administration panel.
After you have rebuilt your network on the new instance, consider joining a larger, well-funded instance with multiple administrators. These instances are less likely to shut down unexpectedly. You can also self-host your own instance using a reliable hosting provider and configure daily database backups to an external storage service.