When you move your Mastodon account from one instance to another, your email address does not migrate with your followers and profile data. The target instance keeps the email you used when you signed up there. This mismatch can cause confusion if you expect your old email to carry over automatically. This article explains why the email stays behind and how to update it on the new instance to keep your account secure and accessible.
Key Takeaways: Updating Your Email After a Mastodon Account Migration
- Preferences > Account > Change email: The only official way to update your email on the target Mastodon instance after migration.
- Email verification link: Mastodon sends a confirmation message to the new address before the change takes effect.
- Two-factor authentication: If enabled on the source account, it does not transfer; you must set it up again on the target instance.
Why Your Email Address Does Not Carry Over During Mastodon Migration
Mastodon’s account migration feature is designed to transfer your public-facing data: followers, profile information, and a redirect from your old profile. The migration process does not touch authentication credentials, including your email address and password. This design prevents a malicious actor from taking over your target account by simply initiating a migration from a compromised source account. The email address remains tied to the target instance’s original registration. You must update it manually through the target instance’s settings.
Additionally, Mastodon instances are independent. Each instance stores its own user database. When you create a new account on the target instance, even as part of a migration workflow, that instance records the email you provided at sign-up. The source instance has no authority to overwrite that data. This separation is a core security feature of the Fediverse.
Steps to Update Your Email Address on the Target Mastodon Instance
- Log in to the target instance
Open your web browser and sign in to the Mastodon instance where you created the new account. This is the instance you intend to keep as your primary account after migration. - Open Preferences
Click the gear icon or your profile avatar in the top-right corner of the Mastodon interface. From the dropdown menu, select Preferences. - Navigate to Account settings
In the left sidebar of the Preferences page, click Account. This section contains all settings related to your profile, email, and password. - Locate the Change email field
Scroll down to the Change email section. You will see a text box labeled New email. Enter the email address you want to use for this Mastodon account. Make sure it is an address you can access. - Save the new email
Click the Save changes button below the email field. Mastodon will display a confirmation message stating that a verification link has been sent to the new address. - Check your new email inbox
Open your email client and look for a message from the Mastodon instance. The subject line will be something like “Confirm your email address for [instance name].” If you do not see it within a few minutes, check the spam or junk folder. - Click the confirmation link
Open the email and click the Confirm email change button or the link provided. This action completes the update. Mastodon will redirect you to a page confirming the email change.
After you confirm the new email, Mastodon uses that address for all future account-related notifications, password resets, and login verification if you enable two-factor authentication.
Common Issues When Updating Your Email After Migration
Email Verification Link Does Not Arrive
If the confirmation email does not appear in your inbox, first verify that you entered the address correctly in the Preferences page. A typo in the email field prevents delivery. If the address is correct, check your spam folder. Some email providers flag automated messages from new instances. Add the instance’s domain to your contacts or safe senders list. If the email still does not arrive, contact the instance’s moderation team through a direct message on Mastodon or their support email.
Two-Factor Authentication Does Not Transfer
Mastodon migration does not copy two-factor authentication settings from the source account to the target account. After you update your email on the target instance, you must set up two-factor authentication again if you want that protection. Go to Preferences > Account > Two-factor Authentication and follow the prompts to link an authenticator app or security key.
Password Reset Requests Go to the Old Email
If you attempt a password reset before updating your email on the target instance, Mastodon sends the reset link to the original email used during sign-up. This address is likely different from the one on your source account. To avoid this confusion, update your email immediately after completing the migration. If you already triggered a reset and cannot access the old email, contact the instance administrator to verify your identity manually.
| Item | Old Source Instance | New Target Instance |
|---|---|---|
| Email address | Stays unchanged; not migrated | Must be updated manually via Preferences |
| Password | Stays unchanged; not migrated | Must be set during sign-up or reset later |
| Two-factor authentication | Stays active on the old account | Must be set up again from scratch |
| Followers | Redirected to new profile | Follow request sent; no manual action needed |
You can now update your email on the target Mastodon instance after a migration. The process takes less than two minutes and ensures you receive account notifications and can reset your password if needed. As a next step, consider enabling two-factor authentication on the target instance for stronger account security. For advanced protection, use a hardware security key with WebAuthn support instead of a one-time password app.