You started moving your Mastodon account to a new instance, but the process shows “Pending” and never completes. This usually happens because the old instance cannot confirm the new account ownership or the new instance rejects the migration request. The move account feature requires a handshake between two servers: the old instance must verify a redirect URL, and the new instance must accept the alias. This article explains why the move gets stuck and provides step-by-step fixes to complete the migration.
Key Takeaways: Fixing a Stuck Mastodon Account Move
- Preferences > Account > Move from a different account: Initiates the follower migration handshake on the new instance.
- Preferences > Account > Account settings > Move to a different account: Sets the redirect on the old instance.
- Check server logs or contact admin: If the status remains pending for more than 48 hours, server-side rejection is likely.
Why the Move Account Status Gets Stuck on Pending
Mastodon’s account move feature uses a two-step verification process. First, you set a redirect on the old account pointing to the new account. Second, you confirm the move on the new account by providing the old account’s username and domain. The new instance then fetches the redirect URL from the old account to verify ownership.
If the status shows “Pending” for more than a few minutes, one of these conditions is failing:
- The old instance cannot serve the redirect URL because the account settings were not saved correctly.
- The new instance cannot reach the old instance due to network restrictions or server downtime.
- The old account has privacy settings that block public redirects.
- The new instance rejects the alias because the old account is already moved or deleted.
The process is not instant. It can take up to 24 hours for all followers to migrate, but the initial handshake should complete within minutes. If it stays pending longer than one day, the move will likely never finish without manual intervention.
Steps to Fix a Pending Account Move on Mastodon
Follow these steps in order. Do not skip any step. Each step addresses a specific failure point in the migration handshake.
- Verify the old account redirect is set correctly
Log into your old Mastodon instance. Go to Preferences > Account > Account settings. Scroll to the section labeled “Move to a different account.” Make sure the text field contains the full handle of your new account in the format @username@newinstance.example. The handle must include both the username and the domain. Click “Save.” Wait 5 minutes for the redirect to propagate. - Confirm the new account alias is active
Log into your new Mastodon instance. Go to Preferences > Account > Move from a different account. Enter the full handle of your old account in the format @oldusername@oldinstance.example. Click “Confirm.” The new instance will fetch the redirect from the old account. If the old redirect is correct, the status should change to “Completed” within a few minutes. - Check the old account’s public profile
Open a private browser window and navigate to the old account’s public profile URL (for example, https://oldinstance.example/@oldusername). Look for a banner or notice that says “This account has moved to @newusername@newinstance.example.” If you do not see this banner, the redirect was not saved. Repeat step 1 and ensure you click “Save.” - Disable any privacy extensions or VPNs
If you use browser extensions that block cross-site requests or a VPN that changes your IP region, the handshake may fail. Temporarily disable all privacy-related extensions. Try the move again from a browser without these tools. - Retry the move after 24 hours
If the status remains pending after one day, cancel the move on the new instance. Go to Preferences > Account > Move from a different account. Click “Cancel.” Then repeat steps 1 and 2. Sometimes the old instance needs time to cache the redirect. - Contact the old instance admin
If none of the above works, the old instance may have server-side restrictions that block redirect fetches. Send a direct message to the admin of the old instance. Ask them to check the server logs for errors related to the account move. Provide your old username and the new account handle.
If Mastodon Still Shows Pending After the Main Fix
“The old account does not have a redirect set” error even after saving
This error means the new instance cannot find a valid redirect URL on the old account. The most common cause is a typo in the handle or the old instance not saving the setting due to a server error. Log out and log back into the old instance. Set the redirect again. If the error persists, try using a different browser or clearing your browser cache before setting the redirect.
Move status shows “Completed” but followers did not transfer
When the move completes, Mastodon sends a notification to each follower’s instance. Some instances may process this notification slowly. Wait up to 48 hours. If followers still have not migrated, check that your new account is not set to private. A private new account can block the follower migration. Temporarily set your new account to public until the migration finishes.
“Alias already in use” error on the new instance
This error occurs when the old account handle was already used in a previous move or alias. Cancel the current move. On the old instance, go to Preferences > Account > Account settings and remove any existing redirect. Save. Then start the move process again from step 1.
Mastodon Account Move vs Manual Follower Migration
| Item | Move Account Feature | Manual Migration |
|---|---|---|
| Follower transfer | Automatic after handshake | You must ask each follower to re-follow |
| Old account redirect | Permanent redirect banner | No redirect; followers see old account as inactive |
| Time to complete | Up to 48 hours | Depends on your outreach |
| Posts migration | Posts do not move | Posts do not move |
| Risk of stuck status | Yes, if handshake fails | No automated process to get stuck |
The Move Account feature is the only way to automatically transfer followers and set a permanent redirect. Manual migration does not trigger a stuck pending status but requires significant effort. If the Move Account feature fails repeatedly, manual migration is the fallback.
You can now fix a pending account move by verifying the redirect URL and retrying the confirmation. If the issue persists, cancel the move and restart the process after 24 hours. For a long-term solution, ensure your new instance is compatible with the old instance’s software version. Some older Mastodon versions require manual alias approval by the new instance admin.