When you try to move your Mastodon account to a new instance, the platform may show the error message “Could not move account” and stop the migration process. This error usually occurs because the old account’s API token has expired, the new account was created on the wrong server, or the migration handshake between the two instances failed. In this article, you will learn the exact steps to resolve this error and complete the follower migration successfully.
Key Takeaways: Fixing the ‘Could Not Move Account’ Error in Mastodon
- Account Settings > Move from a different account: Initiates the follower migration handshake from the new instance to the old account.
- Old account profile page: The new instance must have access to the old account’s public profile to verify the alias.
- API token refresh: Logging out and logging back in on the old instance often resolves token expiration issues.
Why Mastodon Displays ‘Could Not Move Account’ During Migration
The “Could not move account” error appears when the Mastodon API cannot complete the account move process. The account move feature requires a secure handshake between the old instance and the new instance. This handshake verifies that you control both accounts. When any part of this verification fails, Mastodon cancels the move and shows the error.
The most common root cause is an expired or invalid API token on the old account. Mastodon uses OAuth tokens to authenticate API requests. If you have not used the old instance in a while, the token may have been revoked or expired. Another frequent cause is entering the wrong old account handle. The handle must include the full format @username@instance.example.com. A third cause is that the new instance cannot reach the old instance’s API endpoint because the old server is offline or blocking the request.
How the Account Move Handshake Works
The account move process follows three steps. First, you set up an alias on the old account by adding your new account handle in the old account’s settings. Second, you initiate the move from the new account by entering the old account handle. Third, Mastodon’s API checks the alias on the old account. If the alias matches the new account, the move proceeds. If any step fails, the system stops and shows the error.
Steps to Resolve ‘Could Not Move Account’ Error
- Log out and log back in on the old account
Open the old instance in your browser. Go to Preferences > Account > Log out. Then log in again with your credentials. This refreshes your API token and clears any temporary session issues. - Set up the account alias on the old account
On the old account, navigate to Preferences > Account > Move to a different account. Click the button labeled “Create an account alias.” Enter the full handle of your new account in the format @username@newinstance.example.com. Click “Save.” This tells the old instance that you want to move to the new account. - Verify the alias was saved correctly
Go back to the old account’s profile page. Look for a line that says “Moving to: @username@newinstance.example.com.” If you do not see this line, repeat step 2 and make sure you saved the alias. - Log in to the new account
Open the new instance and log in to your new Mastodon account. Go to Preferences > Account > Move from a different account. - Enter the old account handle
In the field labeled “Old account handle,” type the full handle of your old account: @username@oldinstance.example.com. Double-check the spelling. The instance domain must match exactly, including subdomains like social.example.com if applicable. - Provide the old account password
Mastodon asks for the old account password to verify your identity. Enter the password you used on the old instance. If you have forgotten the password, use the password reset feature on the old instance before starting the migration. - Click ‘Move Followers’
Click the button labeled “Move Followers.” Mastodon will attempt the handshake. If the alias matches and the API token is valid, the move proceeds immediately. You will see a success message and a list of followers that will be transferred. - Wait for the migration to complete
The migration may take a few minutes to a few hours depending on the size of your follower list. Mastodon sends a notification to your new account when the move finishes. Do not delete the old account until the migration is complete.
If Mastodon Still Shows the Error After the Main Fix
Old account handle is incorrect or missing the full domain
The handle must include the full instance domain. For example, if your old account is on mastodon.social, the handle is @yourname@mastodon.social. Omitting the domain or using a partial domain causes the handshake to fail. Go back to the new account’s migration page and re-enter the handle with the full domain.
Old instance is offline or blocking the API
If the old instance is down for maintenance, shut down, or has rate-limited your IP address, the new instance cannot verify the alias. Check the old instance’s status page or try accessing the old instance in a browser. If the instance is permanently offline, you cannot migrate followers through the automatic handshake. In that case, you must manually ask your followers to follow your new account.
API token revoked due to inactivity
Some Mastodon instances revoke API tokens for accounts that have been inactive for more than 30 days. Logging out and logging back in, as described in step 1, generates a new token. If that does not work, contact the admin of the old instance and ask them to re-activate your account or issue a new API token.
Follower count does not update after the move
After a successful move, followers are transferred slowly to avoid overloading the instances. Mastodon typically transfers 10 to 20 followers per minute. If your follower count does not increase after several hours, check the old account profile to see if the “Moving to” line is still present. If it is, the move is still in progress. If the line is gone and followers did not transfer, repeat the entire migration process from step 1.
Account Move vs Manual Re-follow: Migration Method Comparison
| Item | Account Move (Automatic) | Manual Re-follow |
|---|---|---|
| Description | Mastodon API transfers followers from old account to new account | You ask followers to manually follow the new account |
| Time required | A few minutes to a few hours | Days or weeks depending on follower response |
| Follower retention | High — most followers transfer automatically | Low — many followers may not see the request |
| Prerequisites | Both accounts must be accessible and the old instance must be online | No technical prerequisites |
| Error handling | May fail if API token is expired or alias is missing | No API errors, but relies on follower action |
Use the automatic account move method whenever possible. It preserves your follower count and requires minimal effort from your followers. Manual re-follow is only necessary when the old instance is permanently unavailable or the API handshake fails repeatedly.
After resolving the “Could not move account” error, you can now migrate your Mastodon followers to a new instance. Next, update your profile bio on the new account to include a link to your old profile. This helps search engines and federated instances recognize the move. For advanced control, consider setting up a custom domain for your Mastodon account to make future migrations easier.