Migrating Two Mastodon Accounts from Different Servers to a Single One: A Guide

Migrating two Mastodon accounts from different servers to a single instance requires careful planning because the platform does not automatically import historical posts, media, or follower lists during the transfer process. You must manually export your data, re-post content if desired, and rebuild your social graph by following users on the new server. This guide details the correct steps for moving your identity while preserving your network connections through manual interaction rather than automated data restoration.

Preparing Your New Account

Before initiating any migration, you need a stable home for your new identity. If you are moving both accounts to an existing server, ensure that server is accepting new registrations. If you are setting up a fresh instance, consult our guide on How to Control New User Approval on Your Instance to manage incoming requests effectively. Create your primary account on the destination server. This will be the account that retains your main username handle. It is crucial to verify that you have access to the email address associated with this new account, as you will need to confirm ownership before linking it to your old identities. Do not delete your old accounts yet; they serve as bridges for your followers to find you.

Exporting Data from Old Accounts

Mastodon provides a built-in tool for exporting your personal data, but it is important to understand what this includes. Navigate to Settings > Privacy > Data in your profile on each of the two source servers. Select "Download your data." This process generates a ZIP file containing your posts, media, favorites, and follows. However, note that this export is primarily for archival purposes. The JSON format contains your history, but there is no native feature to upload this JSON back into another account to restore posts or followers. The previous claim that Mastodon supports generic ActivityPub import for restoring full histories was incorrect. You cannot simply upload the data file to the new server to get your old tweets back. You must treat this export as a backup, not a migration tool for content.

Reposting Content Manually

Since automated import is not supported, you have two choices regarding your historical content: keep it archived locally or repost it on the new server. Most users choose to repost their most significant updates to maintain context for new followers. Log into your new account and begin copying your best posts. Use the "Boost" function if you want to preserve the original attribution, or create new posts that summarize your key messages. While tedious, this ensures that anyone visiting your new profile sees active, relevant content. Avoid spamming all posts at once; spread them out over several days to avoid triggering anti-spam filters on the new server.

Transferring Followers and Following Lists

The most critical part of migrating two accounts is transferring your social graph. Since you cannot import the follow list, you must rebuild it manually. Start by following the people you care about most on the new server. Search for their usernames (e.g., @user@newserver) and send follow requests. For your own followers, you need to notify them to move. Post a clear announcement on both old accounts explaining that you are consolidating into one account. Include your new handle prominently. Encourage your followers to follow you on the new server. As they do, you should reciprocate by following them back. This manual process can take time, especially if you have hundreds of connections, but it is the only reliable way to retain your audience. Consider using third-party tools like Migrate.Masto or similar community scripts that help automate the detection of who follows you across servers, but remember these tools only assist in identification; they do not perform the actual import of data. You still need to execute the follows and unfollows.

Consolidating and Finalizing

Once you have moved your essential followers and posted key content, you can decide whether to keep the old accounts active or deactivate them. If you keep them, set their bios to indicate the new location. If you deactivate, go to Settings > Your account > Deactivate account on each old server. Be aware that deactivation makes the username available to others after a grace period, usually 30 days. Ensure that your new account’s bio clearly states that it is the continuation of both previous accounts. This helps prevent confusion among those who were split between the two source servers.

Frequently Asked Questions

Can I use ActivityPub to merge two accounts automatically?

No, ActivityPub is designed for federated communication, not for merging user identities or importing historical data. There is no standard protocol that allows one account to absorb another’s posts or followers directly. You must handle the consolidation manually through user actions.

Will my likes and bookmarks transfer to the new account?

No, likes and bookmarks are tied to the specific account ID on the source server. They do not migrate. You will need to re-favorite items on the new server if they are important to you. The exported data file serves only as a local record of these interactions.

How long does the migration process take?

The technical setup takes minutes, but rebuilding your social graph depends on your follower count. For accounts with few followers, it may take a day. For larger accounts, it can take weeks to manually follow back everyone who moves to the new server. Plan for a gradual transition rather than an overnight switch.

What happens if I delete my old accounts too quickly?

If you delete your old accounts before notifying your followers, they will lose the ability to find you. Their follow requests will fail, and they may assume you abandoned the platform. Always wait until you have confirmed that a significant portion of your core audience has moved to the new account before deactivating the old ones.