Mastodon offers a built-in profile move feature that lets you migrate followers from one Mastodon account to another on a different instance. This decentralized handshake works because both servers speak ActivityPub. Threads, Meta’s microblogging platform, also supports ActivityPub federation but does not implement the full profile move protocol. As a result, you cannot use Mastodon’s standard migration tool to move followers to a Threads account. This article explains exactly which parts of the migration fail and why, and what you can do instead.
Key Takeaways: Mastodon to Threads Migration Limits
- Preferences > Account > Move from a different account: This Mastodon feature does not work with Threads because Threads does not support the Move activity type.
- Manual follower re-follow: The only way to bring followers to Threads is to ask them to unfollow your Mastodon account and re-follow your Threads profile.
- Profile redirect: You can update your Mastodon bio and profile link to point to your Threads profile, but Mastodon will not automatically redirect followers.
Why the Decentralized Profile Move Fails Between Mastodon and Threads
The Mastodon profile move feature works because both the source and target servers understand a specific ActivityPub activity called Move. When you initiate a move on your Mastodon account, your server sends a Move activity to the target server. The target server must verify the request and then tell all followers of the source account to follow the new account instead. Threads does not process the Move activity at all. It ignores the incoming Move request and does not instruct its servers to transfer followers.
This is not a bug. Threads intentionally does not implement the full ActivityPub Move protocol. Threads focuses on basic federation features like posting, replying, and boosting. The Move activity is a more advanced feature that Mastodon developed after the ActivityPub standard was published. Since Threads uses its own interpretation of ActivityPub, it omits the Move handler entirely. No amount of configuration on your Mastodon side can force Threads to accept a migration.
What the Move Activity Requires That Threads Lacks
The Move activity involves a three-way handshake. The source server sends a Move activity to the target server. The target server must then send a Follow activity back to the source server to confirm it owns the new account. Finally, the source server notifies all its followers to update their follow targets. Threads does not implement the second and third steps. It can receive the initial Move request but will not respond with the required Follow activity. Without this handshake, the migration cannot proceed.
What Happens When You Try to Move to Threads
- Open Mastodon Preferences
Log into your Mastodon account and click the Preferences link in the navigation menu. - Go to Account settings
In the Preferences sidebar, click Account. - Find the Move from a different account section
Scroll down until you see the heading Move from a different account. - Enter the Threads profile URL
In the field labeled Handle of the new account, type the full ActivityPub address of your Threads account. For example, @username@threads.net. - Provide the confirmation code
Mastodon will generate a confirmation code. You must post this code as a public post on your Threads account. Copy the code and paste it into a new post on Threads. Make sure the post is public and visible to everyone. - Click Move Followers
After you post the code, return to Mastodon and click Move Followers. Mastodon will attempt to send the Move activity to Threads.
After you complete these steps, you will see an error message like Move failed or Target server did not respond. Your Mastodon followers will not be transferred. Your Mastodon profile will not be redirected to Threads automatically. The only change is that your bio may still show the old handle unless you manually update it.
What You Can Do Instead of a Full Migration
Since the automated move does not work, you have three alternative approaches. Each has its own trade-offs.
Manual Follower Migration via Announcements
Post a public announcement on your Mastodon account stating that you are moving to Threads. Include your Threads profile URL and ask followers to unfollow your Mastodon account and follow your Threads profile instead. This method is manual and will not reach followers who do not check your feed regularly. To maximize reach, pin the announcement to your profile and repeat it periodically.
Profile Link and Bio Update
Edit your Mastodon profile to add your Threads URL in the bio or the Website field. This gives visitors a direct link to your new account. However, Mastodon does not redirect existing followers automatically. They must click the link and follow you again on Threads.
Cross-posting Instead of Migration
If your goal is to maintain a presence on both platforms, use cross-posting tools. Mastodon has built-in options to automatically share your toots to Twitter, but not to Threads. Third-party services like Crossposter for Mastodon can relay your Mastodon posts to Threads. This keeps both accounts active without moving followers.
If the Move Still Fails or You Encounter Other Problems
Threads Account Not Federating at All
If your Threads account is not visible from Mastodon, check that your Threads profile is set to public. Threads accounts that are private cannot be found or followed from Mastodon. Go to Threads settings and switch your profile to Public. Also verify that your Threads account has a valid ActivityPub address. If you joined Threads before December 2024, your account may not have federation enabled. In that case, you need to update the Threads app to the latest version and enable ActivityPub in your Threads privacy settings.
Mastodon Shows Target Server Did Not Respond
This is the standard error when the target server does not understand the Move activity. It is not a network problem. No amount of retrying will change the outcome. Accept that the Move activity is not supported and use one of the manual alternatives described above.
Followers Lost After Manual Re-follow
If you delete your Mastodon account after asking followers to move, any followers who have not yet re-followed you on Threads will lose access to your content. Keep your Mastodon account active until you are certain that your important followers have made the switch. After you delete the Mastodon account, the old posts are gone and cannot be recovered. Consider archiving your posts before deletion.
| Item | Mastodon to Mastodon Migration | Mastodon to Threads Migration |
|---|---|---|
| Protocol support | Full ActivityPub Move activity | Move activity not implemented |
| Follower transfer | Automatic, followers re-follow new account | Not possible, manual only |
| Profile redirect | Old profile shows redirect notice | No redirect, old profile stays unchanged |
| Confirmation code | Posted on target account, verified automatically | Code posted but verification fails |
| Time to complete | Minutes | Not applicable |
Mastodon’s decentralized profile move feature is designed for transfers between Mastodon instances that fully support the ActivityPub Move activity. Threads does not implement this protocol, so the automated migration fails completely. You can still direct followers manually by updating your profile and posting announcements. For a permanent move, you must ask each follower to unfollow your Mastodon account and follow your Threads profile individually. If you want to keep both accounts active, cross-posting tools let you maintain a presence on both platforms without losing your Mastodon audience. Before deleting your Mastodon account, verify that your key followers have already followed you on Threads to avoid losing them entirely.