Moving your Mastodon account to a new instance requires more than just creating a new profile. Without proper setup, your followers cannot automatically transfer, and your old posts become disconnected from your new identity. Mastodon provides an account alias feature that links your old account to your new one so followers and profile metadata can migrate smoothly. This article explains how to set up account aliases on both the old and new Mastodon accounts to complete a full move.
An account alias is a declaration that your old account belongs to you and points to your new account. The Mastodon server uses this alias during the move process to reassign followers and preserve your posting history. Setting up the alias on both ends ensures the handshake is verified and no followers are left behind.
You will learn the exact steps to configure the alias on your old instance, then confirm it on your new instance. We also cover common pitfalls such as alias mismatches and timing issues that can break the migration.
Key Takeaways: Mastodon Account Alias Setup for Migration
- Preferences > Account > Move from a different account: Initiates the follower migration handshake to a new Mastodon account.
- Preferences > Account > Account aliases: Links your old account handle to your new profile so the server recognizes ownership.
- Old account handle format: Use the full @username@instance.domain format when entering the alias on your new account.
What Are Mastodon Account Aliases and Why You Need Both
An account alias is a server-side record that tells your old instance your new account handle. When you initiate the move from your old account, the alias is checked against the new account to confirm you control both profiles. Without the alias, the new instance cannot accept the follower transfer request.
The alias must be set on both accounts because the process is bidirectional:
- On your old account, you enter the new account handle as the destination for the move.
- On your new account, you add the old account handle as an alias to prove ownership.
If either side is missing, the migration fails silently. Followers see no notification, and your old profile remains active with no link to the new one.
Prerequisites for Setting Up Aliases
Before you begin, confirm the following:
- You have login credentials for both the old and new Mastodon accounts.
- Both accounts are on Mastodon instances that support account migration. Almost all public instances do.
- Your new account is at least 24 hours old. Mastodon enforces this waiting period to prevent abuse.
- You have not already moved from the old account. A move can only be performed once per account.
Steps to Set Up Account Aliases on Both Mastodon Accounts
Follow these steps in the exact order shown. Starting with the alias on the new account prevents the move from failing due to missing proof of ownership.
Step 1: Add the Alias on Your New Mastodon Account
- Log in to your new Mastodon account
Open your web browser and sign in to the instance where you created your new profile. - Open Settings
Click the gear icon in the top-right corner of the Mastodon interface. The Preferences page appears. - Navigate to Account Aliases
In the left sidebar, click Account. Then find the section labeled Account aliases. If you do not see this option, your instance may not support aliases or your account is too new. - Enter the old account handle
Type your old account handle in the exact format:@username@oldinstance.domain. For example,@johndoe@mastodon.social. Do not include any extra spaces or brackets. - Click the Add button
The alias is saved immediately. You should see the old handle listed under your aliases. If you receive an error, double-check the handle spelling and domain.
Step 2: Initiate the Move from Your Old Mastodon Account
- Log in to your old Mastodon account
Use your original credentials to sign in to the instance you are leaving. - Open Settings
Click the gear icon to access Preferences. - Go to the Move from a different account section
In the sidebar under Account, scroll down to Move from a different account. This option is visible only if you have not already performed a move. - Enter the new account handle
Type your new account handle:@newusername@newinstance.domain. For example,@johndoe@mastodon.online. - Enter your new account password
Mastodon requires your new account password to verify you own it. This is a one-time check. Your password is sent encrypted and is not stored. - Click Move Followers
The migration process begins. Mastodon sends a request to the new instance. If the alias you set in Step 1 matches the handle you entered here, the move proceeds. Followers on the old account receive a notification that you moved to the new account.
Step 3: Confirm the Migration on Your New Account
- Log in to your new account again
After the move completes, sign in to your new instance. - Check your follower count
Go to your profile page. The follower count should have increased by the number of followers who were migrated. Not all followers transfer automatically—those with privacy settings that block migration may remain on the old account. - Verify the alias is still active
Return to Preferences > Account > Account aliases. The alias you added earlier remains listed. Do not remove it. It stays as a permanent record that you owned the old account.
Common Issues When Setting Up Mastodon Account Aliases
Alias Not Accepted by the New Instance
If the new instance rejects the alias, the most common cause is a typo in the old account handle. Mastodon is case-sensitive for usernames and domains. Re-enter the handle using the exact format from your old profile page. Also confirm that your new account is at least 24 hours old. Instances block alias creation for accounts younger than that.
Move Followers Button Is Grayed Out
If the Move Followers button on your old account is unclickable, the alias on the new account may not be set yet. Go back to Step 1 and add the alias before attempting the move again. Another reason is that the old account has already performed a move. Mastodon only allows one move per account. If you already moved, you cannot redo it from the same old account.
Followers Did Not Transfer After the Move
Some followers may not transfer if their instance blocks migration or if they have manually disabled follower migration in their privacy settings. The move process sends a notification to each follower, but they must choose to follow your new account. Check your new account notifications for follower requests. You can also manually ask followers to re-follow if the automatic transfer failed.
Old Account Still Active After Migration
The old account remains active but is marked with a note that you moved. It does not get deleted automatically. You can choose to disable it by going to Preferences > Account > Delete account. However, keeping the old account as a redirect is recommended because it tells visitors and search engines where you moved.
| Item | Alias on New Account | Move from Old Account |
|---|---|---|
| Purpose | Proves you control the old account | Triggers follower transfer and profile redirect |
| Where to configure | Preferences > Account > Account aliases | Preferences > Account > Move from a different account |
| Handle format required | @oldusername@oldinstance.domain | @newusername@newinstance.domain |
| Password needed | No | Yes, new account password |
| Can be undone | Yes, remove the alias | No, move is permanent |
Setting up account aliases on both your old and new Mastodon accounts ensures a clean migration with minimal follower loss. The alias on the new account proves ownership, while the move command on the old account transfers followers and redirects your profile. After completing these steps, your followers see your new account in their feed and your old profile displays a link to your new location.
If you encounter errors during the process, double-check the handle format and account age. Most migration failures are caused by simple typos or missing alias entries. Once the move is complete, consider disabling your old account to prevent duplicate content, but leave the alias active so the server records remain valid.
For advanced users, you can also export your old account’s list of followed accounts from Preferences > Import and export > Export and import them on your new account. This preserves your home feed without relying on the automatic migration feature.