Mastodon Export Versus Account Migration: When to Choose Each

When you need to leave a Mastodon instance or reorganize your account, two tools are available: data export and account migration. Many users confuse these options or pick the wrong one for their situation. Export creates a downloadable archive of your posts, media, and lists. Account migration transfers your follower relationships and profile information to a new instance. This article explains the exact differences between export and migration, and helps you decide which action to take based on your goals.

What Each Feature Does in Mastodon

Mastodon provides two distinct mechanisms for leaving or reorganizing an account. Understanding their scope and limitations is essential before you act.

Mastodon Export: What It Captures

The export feature creates a downloadable archive of your data from the current Mastodon instance. The archive is a single ZIP file that contains:

• Your statuses (posts and boosts) in JSON format
• Media attachments associated with your posts
• Your follow list, follower list, block list, mute list, and domain blocks
• Your lists and bookmarks

The export does not include direct messages. Mastodon deletes direct messages from the server after they are delivered. The export also does not include account-level settings such as profile bio, avatar, header image, or privacy preferences. You can use the exported JSON files to reimport follows, blocks, and lists into a new account using the Import feature in Preferences > Import and Export > Import.

Mastodon Account Migration: What It Transfers

Account migration is a server-to-server process that moves your social graph from your old Mastodon account to a new one. It does not transfer your posts, media, or direct messages. Migration initiates a handshake between the old instance and the new instance. After the handshake completes, the following items are transferred:

• Your followers — each follower receives a notification and is prompted to follow your new account
• Your profile display name and bio text (copied from the old account)
• A redirect notice on your old profile that points to your new account

Your old account is not deleted. It remains as a forwarding placeholder. You can delete it manually after the migration settles. Migration does not transfer your followed accounts, lists, blocks, mutes, or domain blocks. You must re-follow accounts manually or use the import feature with the exported follow list.

When to Run an Export and When to Run a Migration

The choice depends on your primary goal. Use the table below as a quick reference, then read the detailed scenarios.

1. Choose export when you want a full backup of your content
   If you plan to leave Mastodon entirely, or if you want a local copy of your posts and media for archival purposes, run an export. The exported ZIP file is your only way to preserve your text and images outside of the instance.
2. Choose migration when you want to keep your followers and move to a new instance
   If you are moving to a different Mastodon server or creating a new account on the same server, use account migration. Your followers will be automatically prompted to follow your new account. Your old profile will redirect visitors to the new one.
3. Run both when you are moving permanently
   First export your data. Then initiate migration. After migration completes, import your follow list, blocks, and lists into the new account using the Import feature. This combination gives you the best outcome: your content is backed up, your followers are moved, and your social graph is restored.

Detailed Scenario: Leaving Mastodon Completely

If you want to delete your Mastodon account and never return, run an export. Migration is pointless because you have no destination account. After downloading the export, you can delete your account from Preferences > Account > Delete account. The export preserves your posts for your own reference, but they will no longer be accessible on the fediverse.

Detailed Scenario: Moving to a Different Instance

Create your new account first. Then on your old account, go to Preferences > Account > Move to a different account. Enter the handle of your new account. The old instance sends a verification request to the new instance. After both sides confirm, the migration proceeds. Followers see a notification on their home feed. After migration, export your old account data and import the follow list into the new account.

Detailed Scenario: Reorganizing on the Same Instance

If you want a fresh start on the same Mastodon server, create a second account on that instance. Then run migration from the old account to the new one. Because both accounts are on the same server, migration is instantaneous. After migration, you can delete the old account. Export is optional but recommended if you want to keep old posts for personal reference.

Common Misunderstandings and Limitations

Migration Does Not Transfer Posts

This is the most frequent confusion. Many users expect that account migration will move their entire timeline to the new account. It does not. Mastodon is not an email system. Posts are stored on the instance where they were created. Migration only moves the follower relationship and profile metadata. Your old posts remain on the old instance and will be lost if you delete the old account.

Export Does Not Preserve Follower Relationships

The export file contains a list of your followers, but that list cannot be reimported to re-establish follow relationships. Mastodon does not allow an account to force-follow another account. The exported follower list is informational only. If you want to keep your followers, use migration instead.

Export Format Is Not Human-Readable by Default

The exported statuses are in JSON format. Opening the file in a text editor shows raw data. To view your posts in a readable format, you need to use a third-party tool such as Mastodon Archive Viewer or write a script to parse the JSON. Mastodon does not provide a built-in viewer for exported archives.

Migration Requires Both Accounts to Be Active

You cannot migrate from a deleted account. If you already deleted your old account, your followers have no target to redirect to. You must create the new account first, then initiate migration from the old account while both are active. The old account remains as a placeholder after migration until you manually delete it.

Export vs Migration: Quick Feature Comparison

Item	Export	Account Migration
Primary purpose	Archive posts, media, and lists for backup	Move followers and profile to a new instance
Transfers posts	Yes — JSON format with media files	No — posts stay on the old instance
Transfers followers	Exports a list but cannot reimport it	Yes — followers receive a redirect notification
Transfers follow list	Yes — can be reimported into a new account	No — must be reimported separately
Transfers lists and blocks	Yes — can be reimported	No — must be reimported separately
Requires destination account	No	Yes
Leaves old account active	Yes — account unchanged	Yes — becomes a redirect placeholder

Use export when your priority is preserving your content. Use migration when your priority is preserving your social graph. For a complete move, run export first, then migration, then import the exported follow list and blocks into the new account.

Now you can decide between export and migration based on your specific situation. If you are moving instances, start by exporting your data from Preferences > Import and Export > Export Data. Then create your new account and initiate migration from Preferences > Account > Move to a different account. After migration completes, import your follow list and blocks into the new account using the Import feature. This three-step process gives you the most comprehensive transition with minimal loss.