Mastodon Migration Cooldown Period: How Long to Wait Between Moves

When you move your Mastodon account from one instance to another, you trigger a follower migration handshake. After the move completes, you cannot perform another account migration immediately. Mastodon enforces a cooldown period to prevent abuse and give the federation time to propagate the changes. This article explains exactly how long the cooldown lasts, what actions are blocked during that time, and how to check your remaining cooldown time.

Why Mastodon Enforces a Migration Cooldown

Mastodon uses a follower migration mechanism that relies on the ActivityPub protocol. When you move your account, your old instance sends update messages to every server that follows your old account. Those servers then update their local records to point to your new account. This process can take hours or even days to complete across the entire fediverse.

Without a cooldown, a user could move their account repeatedly, causing a flood of update messages across the network. This would increase server load, slow down federation, and confuse other users who see frequent account changes. The cooldown also prevents malicious actors from rapidly cycling through accounts to evade blocks or suspensions.

The cooldown is enforced at the account level, not the instance level. This means the same account cannot be moved again within 30 days, but you can still create a new account on a different instance and move from that new account immediately.

How Long the Cooldown Lasts

The standard cooldown period is 30 days. This duration is hardcoded in Mastodon’s source code and cannot be changed by instance administrators. The 30-day countdown begins at the exact moment you confirm the move, not when the migration process finishes.

During the cooldown, the following actions are blocked:

• Initiating a new move to a different account from the same source account.
• Deleting the old account if it still has pending follower migration tasks.
• Changing the redirect setting on the old profile.

After the 30-day cooldown expires, you can move the same account again. However, if you move to a third instance, the original old account remains redirected to the first destination. To break that chain, you must delete the original old account after the cooldown ends.

Steps to Check Your Cooldown Status

1. Open Preferences
   Log in to your Mastodon account on the web interface. Click the gear icon in the right sidebar to open the Preferences menu.
2. Go to Account settings
   In the left navigation panel, click Account. This opens the main account settings page.
3. Scroll to the Migration section
   Scroll down until you see the Move to a different account section. If you have an active cooldown, the button will be grayed out and show a message like You can move again in X days.
4. View migration history
   Below the move button, click View migration history. A list of all previous moves appears with timestamps. The most recent move shows the date when the cooldown started. Add 30 days to that date to find when the next move becomes available.

What Happens If You Try to Move Too Early

If you attempt to initiate a new move while the cooldown is active, Mastodon displays an error message: You have recently moved your account. Please wait 30 days before moving again. The move button remains disabled until the cooldown expires. There is no workaround to bypass the cooldown. Even if you delete your account and create a new one, the cooldown is tied to the account ID, not the username or email.

Common Scenarios and Their Solutions

Accidentally initiated a move to the wrong account

If you started a move but realized the destination account is incorrect, you cannot cancel the move. The cooldown still applies. You have two options:

• Wait 30 days and then move to the correct account.
• Delete the destination account, which breaks the migration chain. After deletion, your old account remains redirected but you can create a new destination account and wait for the cooldown to expire.

Need to move again before 30 days

If you must change instances urgently, create a brand new account on the target instance. Then, instead of moving, simply update your profile on the old account to point to the new one. This does not migrate followers, but it avoids the cooldown. Your followers will see the new profile link in your bio and can follow you manually.

Instance shutdown before cooldown ends

If your old instance shuts down while the cooldown is active, you cannot complete the follower migration. The move was already initiated, but the update messages may not have been sent. After the cooldown expires, you can move from the new account to another instance. The old instance’s data is lost, so followers who did not receive the update must be re-followed manually.

Mastodon Migration Cooldown vs Other Platforms

Item	Mastodon	Pleroma	Misskey
Cooldown duration	30 days	No cooldown	No cooldown
Follower migration	Yes, via ActivityPub	Yes, via ActivityPub	No native migration
Cooldown bypass	Not possible	Not applicable	Not applicable
Error message for early move	Yes, explicit	None	None

Pleroma and Misskey do not enforce a cooldown, but they also lack the same level of follower migration reliability. Mastodon’s cooldown ensures that the federation has enough time to process the move without overwhelming servers.

Now you know the exact cooldown duration and how to check your status. If you plan to move your Mastodon account again, mark your calendar 30 days from the last move. For urgent situations, consider updating your profile link instead of performing a full migration. Always verify your migration history before attempting a new move to avoid the error message.