Mastodon Account Migration Alias Not Recognized: Fix

When you try to move your followers from an old Mastodon account to a new one, the new instance may reject the alias you set on the old account. This error prevents the migration handshake from completing and leaves followers stranded on the old profile. The issue typically occurs because the alias record on the old instance does not match the format required by the new instance or because of a mismatch in the account migration process. This article explains why the alias fails to be recognized and provides step-by-step instructions to fix the problem.

Why the Alias Is Not Recognized During Mastodon Account Migration

Mastodon account migration uses a two-way verification handshake between the old instance and the new instance. The old account must first publish an alias record that points to the new account. The new account then uses that alias to verify ownership by checking the old account’s public key. If the alias is not correctly formatted, if the old instance cannot be reached, or if the keys have not yet propagated, the new instance will show an error that the alias is not recognized.

The alias must be the full URL of the new account, including the protocol (https://) and a trailing slash. For example, https://mastodon.social/@newusername is correct, while newusername@mastodon.social will fail. The same applies when entering the old account URL on the new instance: it must be the full URL of the old account profile page.

Another common root cause is timing. After you set the alias on the old account, the instance needs time to update its public key and alias information. If you immediately switch to the new account and attempt the move, the new instance may query the old instance before the alias is available. A delay of 5 to 10 minutes is often necessary.

Steps to Fix the Alias Not Recognized Error

1. Log into your old Mastodon account
   Open the instance where your old account is hosted. Go to Preferences > Account. Scroll to the section labeled Moving from a different account or Transferring your account. The exact label depends on the Mastodon version.
2. Set the alias to the new account
   In the field labeled Alias for your new account, enter the full URL of your new account profile. The format must be https://instance.domain/@username with a trailing slash. Example: https://mastodon.social/@janedoe. Click Save Changes. A confirmation message appears that the alias has been set.
3. Wait at least 5 minutes
   Do not proceed to the new account immediately. The old instance needs time to propagate the alias and public key to its ActivityPub endpoints. A 5- to 10-minute wait is recommended. Use this time to check that the alias appears on your old profile page by visiting it in a browser.
4. Log into your new Mastodon account
   Open the instance where your new account is hosted. Go to Preferences > Account. Look for the section labeled Move from a different account.
5. Enter the old account URL
   In the field provided, enter the full URL of your old account profile. Use the same format as before: https://instance.domain/@oldusername with a trailing slash. Click Continue.
6. Confirm the migration
   The new instance will query the old instance for the alias. If the alias matches, you will see a success message and a prompt to confirm the move. Click Confirm to start the follower migration. Followers will move over the next several hours.
7. Verify the alias on the old account if the error persists
   Return to the old account and check that the alias field still contains the correct URL. Sometimes the instance may strip the trailing slash or add unexpected characters. Edit the alias if needed and save again. Wait another 5 minutes and retry the move on the new account.

If Mastodon Still Shows the Alias Not Recognized Error

Old account uses a different domain than the instance URL

Some Mastodon accounts are hosted on a custom domain that differs from the instance domain. For example, your instance may be mastodon.example.com but your profile URL is https://example.com/@username. In this case, you must use the instance domain in the alias, not the custom domain. Check your old account’s profile URL by viewing it in a browser. Use that exact URL in both the alias field and the move field.

Old or new instance is running an outdated Mastodon version

Mastodon version 3.5.0 and later support the standard alias handshake. Older versions may require a different process or may not support cross-instance migration at all. Check the version of both instances by visiting /about/more on each instance. If either is below 3.5.0, contact the instance administrator to request an upgrade.

Private or locked account prevents alias verification

If your old account is set to private or locked, the new instance may not be able to read the public key and alias information. Temporarily unlock the old account by going to Preferences > Account and unchecking the box for Lock account. Set the alias again, wait, and then attempt the move. You can relock the account after the migration completes.

Firewall or instance block between the two instances

If the old instance blocks the new instance or vice versa, the handshake will fail. Check the instance’s domain blocks at Preferences > Administration > Domain Blocks (admin access required). If a block exists, you cannot migrate between those instances. You must use a different new instance or request the block to be removed.

Item	Correct Format	Incorrect Format
Alias on old account	https://newinstance.social/@newuser	newuser@newinstance.social
Old account URL on new account	https://oldinstance.social/@olduser	olduser@oldinstance.social
Wait time before moving	5 to 10 minutes	0 minutes
Account privacy setting	Public (unlocked)	Private or locked

After the alias is recognized and the migration completes, your old account will automatically post a final status pointing to your new account. Followers who follow the old account will see a notice to follow the new account instead. The old account will no longer accept new followers. You can then choose to delete the old account or leave it as a redirect.

To verify that the migration succeeded, check the old account’s profile page. It should display a banner at the top indicating that the account has moved to the new URL. You can also check the new account’s followers list after a few hours to confirm that followers have started arriving.

If you frequently switch instances, consider using a Mastodon client that supports multiple accounts, such as Tusky or Ivory. This allows you to keep both accounts active simultaneously without needing to migrate each time.