Mastodon Old Posts Not Carrying Over After Migration: Workaround

When you move your Mastodon account to a new instance, your followers, profile picture, and header image transfer automatically. But your old posts — toots, replies, boosts, and media — stay behind on the original server. This is a deliberate design choice by Mastodon. The platform does not move post history between instances because of data portability and server storage limitations. This article explains why old posts do not transfer and provides a practical workaround to preserve your content on the new account.

Why Mastodon Does Not Transfer Old Posts Between Instances

Mastodon’s migration feature is designed to move your identity — followers, profile, and settings — not your content. Each post is stored on the instance that originally hosted it. When you migrate, the old account is redirected to the new one, but the old server retains all toots, media, and interactions. This architecture exists because Mastodon instances are independent. Moving millions of posts across servers would require the source server to reconstruct and resend every toot, which is not part of the ActivityPub protocol. The protocol only supports moving the account pointer, not the post history.

Additionally, Mastodon’s data export feature generates a downloadable archive of your posts. This archive is intended for personal backup, not for re-importing into a new instance. Mastodon does not offer an import function for old posts. The platform assumes that your new account starts fresh, and your old content remains accessible through the redirect link on your old profile.

Workaround Steps to Preserve Old Posts on Your New Mastodon Account

No official method can move old posts into your new account’s timeline as if they were originally posted there. However, you can manually re-publish your most important old posts using a third-party tool or a manual export-and-import process. The following steps describe the most reliable workaround using the Mastodon-to-Mastodon post migration tool by pruvisto.org. This tool reads your old account’s public posts and re-posts them to your new account via the Mastodon API.

Prerequisites

Before starting, ensure the following:

• Your old Mastodon account is still accessible. The tool needs to fetch public posts from it.
• Your new Mastodon account is set up and you have its API access token.
• You are prepared to have old posts appear as new posts on your timeline. They will have the current date, not the original date.
• You have backed up any private or followers-only posts. The tool only migrates public posts.

Step 1: Export Your Old Account’s Archive

1. Log in to your old Mastodon account.
   Open the instance URL in your browser and sign in with your old credentials.
2. Navigate to Preferences > Import and export > Export.
   You see a list of downloadable data formats.
3. Click the Download link next to “Your archive.”
   Mastodon generates a ZIP file containing your posts as CSV, media files, and other data. This step is for backup only — the archive is not used by the migration tool but ensures you have a local copy.

Step 2: Generate an API Access Token for Your New Account

1. Log in to your new Mastodon account.
   Use the instance where you want old posts to appear.
2. Go to Preferences > Development.
   This page lists your existing applications.
3. Click “New application.”
   Enter a name for the application, for example “Post Migration Tool.”
4. Under Scopes, select “write:statuses.”
   This grants permission to post to your timeline.
5. Click “Submit.”
   The application appears in the list.
6. Click the application name to view its details.
   Copy the “Your access token” string. Keep it private.

Step 3: Use the Mastodon-to-Mastodon Migration Tool

1. Open the migration tool website.
   Go to pruvisto.org/tools/mastodon-migration/ in your browser.
2. Enter your old account’s Mastodon handle.
   Type it in the format @username@oldinstance.social.
3. Enter your new account’s API base URL.
   This is the URL of your new instance, for example https://newinstance.social.
4. Paste the access token from Step 2 into the token field.
   Double-check that you copied the full token.
5. Select the date range for posts to migrate.
   Choose a start and end date. The tool only fetches public posts within this range.
6. Click “Start migration.”
   The tool reads each public post from your old account and posts it to your new account. A progress bar shows the status. The process may take several minutes depending on the number of posts.

Step 4: Verify the Migrated Posts

1. Open your new account’s profile page.
   Scroll through your timeline to confirm old posts appear.
2. Check that each post includes a note about the original date.
   The migration tool appends a line like “Originally posted on [date]” to the post body. This is the only way to indicate the original timestamp.
3. Delete any duplicate posts manually.
   If the tool was run more than once, you may see duplicates. Remove them from your new account’s timeline.

Common Issues With the Post Migration Workaround

Migration Tool Fails to Fetch Posts

The tool requires your old account’s posts to be publicly accessible. If your old account is set to private or if it has been deleted, the tool cannot retrieve posts. Ensure your old account’s privacy setting is set to “Public” before migration. Also, if the old instance is down or unreachable, the tool cannot connect. Wait until the instance is back online.

API Token Errors During Migration

If you see an “Invalid token” or “401 Unauthorized” error, the token you pasted may be incomplete or expired. Generate a new token in Preferences > Development on the new account. Ensure the scope includes “write:statuses.” Some instances require you to confirm the application after creation. Check your new account’s notifications for a confirmation prompt.

Posts Appear With Wrong Timestamps

The Mastodon API does not allow setting a custom timestamp when posting. The migration tool posts each toot with the current time. The original date is added as text in the post body. This is not a bug — it is a limitation of the Mastodon API. If you need exact original timestamps, consider linking to your old profile instead.

Media Attachments Not Migrated

The migration tool does not re-upload images or videos from your old posts. It only migrates the text content. Media files remain on the old instance and are not transferred. To preserve media, download your archive from the old account (Step 1) and manually re-upload important images to your new posts.

Mastodon Post Migration vs. Manual Re-posting

Item	Automated Tool Migration	Manual Re-posting
Time required	Minutes to hours, depending on post count	Hours to days for many posts
Post count limit	Unlimited, but tool may time out after 500 posts	No technical limit, but user patience is the limit
Media preservation	Not supported	You can re-upload each media file
Timestamp accuracy	Original date shown as text in post body	Original date shown as text in post body
Privacy control	Only public posts	Any visibility level you choose

The automated tool is best for migrating a large volume of public posts quickly. Manual re-posting gives you full control over visibility, media, and editing before republishing. If you have fewer than 20 important posts, manual re-posting may be faster and more accurate.

You can now preserve your Mastodon post history after migrating to a new instance using the migration tool or manual re-posting. For most users, the automated tool at pruvisto.org handles the bulk of public posts efficiently. After migration, consider pinning a post on your new profile that links to your old account for full historical access. As an advanced tip, use Mastodon’s “Redirect” setting on your old profile to let visitors automatically land on your new account page.