If you created a Mastodon account through a bridge service that imported your Twitter profile data, you are not using a native Mastodon account. These bridged accounts often lack full control over federation, profile editing, and account migration features. You may also face issues when Twitter changes its API policies or when the bridge service shuts down. This article explains how to identify a bridged Mastodon account and migrate it to a fully native Mastodon account on the same or a different instance.
Key Takeaways: Migrating From a Bridged Twitter Account to Native Mastodon
- Preferences > Account > Move from a different account: Initiates the follower migration handshake to a new native Mastodon account.
- Export CSV from old Mastodon account: Exports your following and block lists so you can re-import them into the new account.
- New native Mastodon account registration: Create a fresh account on a Mastodon instance that does not rely on Twitter bridge services.
Why a Bridged Twitter Account Works Differently on Mastodon
A bridged Mastodon account is one that was created using a third-party service that pulls your Twitter profile picture, display name, bio, and sometimes your tweet history into a Mastodon-compatible format. These services include tools like Twitodon, Mastodon Bridge, or automated import scripts. The account is technically a Mastodon account, but its identity is linked to your Twitter handle. When Twitter changes its authentication or API rules, the bridge can break, leaving your Mastodon profile frozen with outdated data.
A native Mastodon account is one registered directly on a Mastodon instance using an email address and password. You own the account fully. You can change your display name, bio, avatar, and header at any time without depending on an external API. Native accounts also support the full Mastodon account migration feature, which lets you move followers, follow lists, and block lists to a new instance.
Signs That Your Mastodon Account Is Bridged
Look for these indicators. Your profile shows a Twitter handle in the username field. You cannot edit your display name or bio from Mastodon settings. Your avatar and header image are read-only. You logged in using Twitter OAuth instead of an email and password. If any of these apply, your account is bridged.
Steps to Migrate From a Bridged Account to a Native Mastodon Account
- Create a new native Mastodon account
Go to the Mastodon instance of your choice. Click Create account. Provide a valid email address and a strong password. Confirm your email by clicking the verification link sent to your inbox. Do not use any Twitter bridge service during registration. - Export your data from the old bridged account
Log into your bridged Mastodon account. Open Preferences > Import and export > Export. Download the CSV files for follows, blocks, mutes, and domain blocks. Save these files to a secure folder on your computer. - Initiate account migration from the old account
In your bridged account, go to Preferences > Account > Move from a different account. Enter the username of your new native account in the format @username@instance.social. Click Send request. Mastodon will generate a confirmation code. - Confirm the migration on the new account
Log into your new native Mastodon account. Open Preferences > Account > Move to a different account. Paste the confirmation code from the previous step. Click Confirm. The old account will display a redirect notice. Followers on the old account will see a prompt to follow your new account. - Import your CSV files into the new account
In your new native account, go to Preferences > Import and export > Import. Select the CSV file for follows and choose Merge to add those accounts to your new follow list. Repeat for blocks, mutes, and domain blocks. Click Upload and wait for the import to finish. - Update your profile on the new account
Go to Preferences > Appearance > Edit profile. Change your display name, bio, avatar, and header image. Set a new profile URL if you want. Save changes. - Notify your followers about the migration
Post a public toot from your new account announcing the move. Include a link to your old bridged profile so followers can verify the migration is legitimate. Ask followers to unfollow the old account if the redirect notice does not work for them.
What to Do If the Migration Fails or Parts Are Missing
Old bridged account does not show the Move option
Some bridged accounts have restricted settings because the bridge service locked the profile. If the Move from a different account option is missing, you cannot use the automated migration. Instead, export your CSV files and manually inform your followers. Post a pinned toot on the old account with a link to your new native profile. Ask followers to follow the new account directly.
Follower count drops significantly after migration
Mastodon migration is a request, not a forced transfer. Each follower must manually accept the follow request on the new account. Some followers may ignore the prompt. To minimize loss, ask followers in a separate toot to check their pending follow requests. You can also direct message your most engaged followers with the new account handle.
CSV import fails or shows errors
The CSV export from a bridged account may contain outdated or malformed entries. Open the CSV file in a text editor or spreadsheet and remove any rows with strange characters or missing data. Ensure the header row matches Mastodon’s expected format: Account address, Show boosts, Notify on new posts, Languages. Re-upload the cleaned file.
Native Mastodon Account vs Bridged Twitter Account: Key Differences
| Item | Native Mastodon Account | Bridged Twitter Account |
|---|---|---|
| Account ownership | Full control via email and password | Dependent on Twitter API and bridge service |
| Profile editing | Edit display name, bio, avatar, header anytime | Often locked to Twitter data |
| Migration support | Full Move feature available | Move feature may be missing or restricted |
| Data export | Full CSV export of follows, blocks, mutes | May export partial or broken CSV files |
| Instance choice | Register on any Mastodon instance | Usually tied to the bridge service’s instance |
Migrating from a bridged Twitter account to a native Mastodon account gives you full ownership and flexibility. The automated Move feature handles follower transfer when available. If the bridge blocked that option, manual CSV export and direct communication with followers are reliable fallbacks. After completing the migration, delete your old bridged account or leave it as a redirect. Update your profile on the new account to reflect your current identity without Twitter dependencies.