You want to move your Mastodon account from one instance to another without losing followers or being offline for hours. The migration process requires careful timing because your old instance must remain accessible for up to 30 days to redirect followers. This article explains how to prepare your new account, schedule the move, and handle data transfer so your timeline stays intact and your followers follow you seamlessly.
Key Takeaways: Mastodon Migration Planning
- Preferences > Account > Move from a different account: Initiates the follower migration handshake to your new Mastodon account.
- Export data from old instance before starting: Archives your posts, media, and lists so you can import them after the move.
- Keep old profile active for 30 days: Prevents follower loss during the redirect window.
Why Mastodon Migration Requires Planning
Mastodon is a decentralized network where each instance is independently operated. When you move your account, you are not transferring a database entry. Instead, you create a new account on a different server and then establish a redirect from your old profile to the new one. Followers who follow you on the old instance will see a notice that you have moved and can choose to follow your new account. The old account must remain active and readable for at least 30 days to allow this redirect to work. If you delete the old account immediately, followers will see a 404 error and will not be redirected.
Downtime during migration is caused by three factors: the time it takes to export and import data, the time followers take to switch their follow, and the time it takes for you to reconfigure third-party apps and services. With proper planning, you can reduce the actual offline period to under 15 minutes. This article covers the exact steps to export your data, set up the new account, execute the move, and minimize disruption for your followers.
What Data Can You Move?
Mastodon allows you to move your profile, followers, and following list. You can also export and then import your posts, media, bookmarks, and lists. Direct messages cannot be moved because they are stored only on the sender’s and recipient’s instances. Your old posts will remain on the old instance unless you delete them manually. The new account will start with zero posts unless you import your archive.
What Data Cannot Be Moved?
The following items cannot be transferred between instances: direct messages, account blocks, domain blocks, mute settings, and custom emoji that are exclusive to the old instance. You will need to reconfigure these manually on the new instance. Also, any boosts or favorites you gave to other accounts will not carry over.
Steps to Execute a Mastodon Migration With Minimal Downtime
Phase 1: Prepare Your New Instance Account
- Create your new account on the target instance
Go to the instance you want to join and sign up with the same username if possible. If the username is taken, choose a close alternative. Complete the registration and verify your email address. Do not post anything yet. - Export your data from the old instance
On your old account, open Preferences > Import and Export > Export. Download the following files: followers.csv, following.csv, lists.csv, bookmarks.csv, and the archive of your posts and media. The archive may take a few minutes to generate. Save all files to a secure location on your computer. - Import data into the new account
On your new account, open Preferences > Import and Export > Import. Upload the following files in order: lists.csv, bookmarks.csv, following.csv, and the archive. Do not import followers.csv yet because follower migration is handled by the move process, not the import tool. Wait for each import to complete before proceeding to the next.
Phase 2: Execute the Follower Migration
- Set up the redirect on your old account
On your old account, open Preferences > Account > Move from a different account. Enter the username and password of your new account. This tells the old instance to redirect all profile visitors to your new profile. The old instance will also send a notification to all your followers asking them to follow your new account. - Confirm the move on your new account
On your new account, open Preferences > Account > Move to a different account. Enter the username of your old account. This authorizes the handshake. The move process may take up to 10 minutes to propagate across the fediverse. - Update your profile and start posting
After the move is confirmed, update your new profile with a biography, avatar, and header image. Post a pinned toot explaining that you have moved and linking to your new account. This reassures followers who may not have received the automatic notification.
Phase 3: Reconfigure Third-Party Apps and Services
- Update your Mastodon apps with the new account credentials
Open each third-party app you use (Tusky, Fedilab, Mastodon for iOS, etc.) and log out of the old account. Log in with your new account credentials. If the app supports multiple accounts, add the new account and remove the old one. - Reconnect cross-posting services
If you use services like Crossposter or Moa to cross-post to Twitter or other platforms, update the Mastodon account token in each service. Generate a new access token from Preferences > Development on your new instance. - Update your website and social media links
If you have a personal website, a link-in-bio page, or a newsletter that points to your Mastodon profile, update the URL to your new profile. Use the format https://newinstance.social/@username.
If the Migration Stalls or Fails
Followers Not Receiving the Move Notification
Some followers may not see the automatic notification because their instance is offline or has a delay. To reach them directly, post a pinned toot on your old account with a link to your new account. Keep the old account active for 30 days. Followers who visit your old profile during that time will see a banner that says “This account has moved to [new profile].”
Archive Import Shows Errors
If the import of your archive fails, the file may be too large. Most instances limit uploads to 50 MB. If your archive exceeds this limit, split it into smaller files using a zip utility. Contact your new instance admin to ask if they can increase the upload limit temporarily.
Old Instance Admin Deletes Your Account Before 30 Days
Some instances have a policy of deleting inactive accounts after a short period. Before you migrate, check the instance rules. If the grace period is less than 30 days, send a message to the admin explaining that you need the account to remain active for follower redirect. If the admin refuses, export a CSV of your follower list and manually send each follower a direct message on the old account with your new profile link before the account is deleted.
Mastodon Migration Methods: Manual vs Automated
| Item | Manual Migration | Automated Migration (Move Tool) |
|---|---|---|
| Follower notification | You post a toot and hope followers see it | Instance sends a direct notification to each follower |
| Profile redirect | You update your bio with a link | Old profile shows a permanent redirect banner |
| Data transfer | You manually export and import each file | Same manual export and import required |
| Downtime | Several hours while you manually notify followers | Under 15 minutes of active work |
| Follower loss | High, because many followers miss the announcement | Low, because the instance handles the notification |
You can now move your Mastodon account with confidence by following the three-phase plan: prepare the new instance, execute the follower migration, and reconfigure your apps. Keep your old account active for 30 days to ensure all followers have time to switch. For a smooth migration, export your data before the move and import it after the new account is created. The built-in Move tool at Preferences > Account handles follower redirection automatically, which is the fastest way to minimize downtime.