How to Resolve Mastodon ‘Profile Not Found’ After Migration

After migrating your Mastodon account from one instance to another, you may see a “Profile Not Found” error when someone tries to view your old profile or when your old profile redirects improperly. This issue typically occurs because the migration handshake between the old and new instances did not complete fully or because DNS and server-side caching have not refreshed. This article explains the exact causes of this error and provides step-by-step fixes to restore proper redirection from your old profile to your new one.

Why “Profile Not Found” Appears After a Migration

When you migrate a Mastodon account, the old instance needs to store a permanent redirect (HTTP 301) from your old username to your new profile. This redirect is not automatic—it requires the old account to have an alias set to the new account, and the new account must confirm the move. If either step is skipped or fails, the old instance will return a 404 or “Profile Not Found” error instead of redirecting visitors.

Additionally, Mastodon instances cache profile data aggressively. Even after a successful migration handshake, your old instance’s cache may still serve stale data, showing the profile as missing. DNS propagation for any custom domain you have set up can also delay the redirect.

The Role of Account Aliases

An account alias is a statement stored on your old instance that says “This old account now points to this new account.” Without this alias, the old instance has no knowledge of where to redirect visitors. The migration process in Mastodon creates this alias automatically only when you use the official “Move from a different account” feature. If you simply created a new account and deleted the old one, no alias exists, and the old profile becomes a dead 404 link.

Steps to Fix Profile Not Found After Migration

Follow these steps in order. If your old account is still accessible (even if it shows a placeholder), you can repair the redirect. If the old account was deleted entirely, you must contact the old instance’s admin.

1. Log into your old Mastodon account
   You need access to the old account to set or verify the alias. If you cannot log in, use the password reset option on the old instance. If the account was deleted, skip to Step 5.
2. Navigate to Preferences > Account > Move from a different account
   This page shows the current alias settings. If you see your new account listed under “Moving from this account,” the alias is already set. If not, you must initiate the move again.
3. Enter the handle of your new account
   Type your new handle in the format @username@newinstance.social. Mastodon will send a confirmation request to the new instance. Log into your new account and approve the migration request in the notifications panel.
4. Wait 15 minutes for cache refresh
   After approving the move, the old instance needs time to update its database and cache. Visit your old profile URL after 15 minutes. It should now show a redirect notice with a link to your new profile.
5. If the old account was deleted, contact the old instance admin
   Only the instance admin can manually add a redirect record in the Mastodon database. Send an email to the admin of your old instance with your old username, your new handle, and a request to set a 301 redirect. Most admins will comply if you can prove ownership of the old account.

Clear Your Local DNS Cache

If you use a custom domain for your Mastodon profile, outdated DNS records may cause a “Profile Not Found” error on your end while others see the redirect correctly. Clear your local DNS cache:

1. On Windows 11 or Windows 10
   Open Command Prompt as administrator. Type ipconfig /flushdns and press Enter. You will see a confirmation message.
2. On macOS
   Open Terminal and type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Press Enter and enter your admin password.
3. On Linux
   Open Terminal and type sudo systemd-resolve --flush-caches or sudo resolvectl flush-caches, depending on your distribution.

If the Profile Still Shows Not Found After the Main Fix

Old Instance Still Returns 404 After Alias Is Set

Sometimes the old instance’s web server has its own caching layer (like Varnish or Nginx cache) that ignores Mastodon’s internal redirect. In this case, the redirect works for API calls but not for browser visits. Contact the instance admin and ask them to purge the web server cache for your old profile URL.

Federated Links Still Broken After Migration

Posts from your old account that were boosted or linked by other instances may still point to the old profile. Those remote instances cache the old URL and may take days to update. You cannot force this update. Instead, pin a post on your new profile that announces your move and includes a link to your old profile. Visitors who click the old link will see the redirect and then your pinned post.

Custom Domain Not Redirecting to New Instance

If you use a custom domain like social.yourname.com that pointed to your old instance, you must update the DNS A or CNAME record to point to the new instance’s IP address. Even after the DNS change, the old instance may still serve cached content. Wait up to 48 hours for global DNS propagation. During this window, some visitors will see the old instance’s “Profile Not Found” error while others will reach the new instance correctly.

Mastodon Migration Methods: Official Move vs Manual Account Creation

Item	Official Move Feature	Manual Account Creation
Profile redirect	Automatic 301 redirect from old profile	No redirect; old profile becomes a dead link
Follower migration	Followers are moved to new account	Followers are not moved; you must notify them manually
Account alias requirement	Required and set automatically	Not available; alias cannot be added after deletion
Old account deletion	Can be done after move, but redirect remains	Deletion breaks all links permanently

The official move feature is the only way to preserve a working redirect from your old profile. If you already deleted your old account without using this feature, your only option is to ask the instance admin to manually add a redirect in the Mastodon database. Most admins will do this if you provide proof of ownership, such as a signed post from the old account or a confirmation from your new instance.

After you have successfully set the alias and cleared caches, test the redirect by opening your old profile URL in a private browser window. It should display a notice saying “This account has moved to @username@newinstance.social” with a clickable link. If you still see “Profile Not Found,” the issue is server-side caching on the old instance. Contact the admin and ask them to purge the cache for your old username path.