Moving your Bluesky account to a new handle or a different server usually means starting over from zero followers. Bluesky offers a built-in account migration feature that lets you keep your follower list, your posts, and your moderation history. The key is using a custom domain as your handle before you migrate. This article explains how Bluesky account migration preserves your followers, what you need to set up beforehand, and the exact steps to move your account safely.
Key Takeaways: Bluesky Account Migration With Domain Handles
- Custom domain handle (e.g., user.example.com): Lets you move your account between servers without losing followers or content.
- Settings > Account > Handle > I have my own domain: The menu path to set up a custom domain handle before migration.
- DNS TXT record verification: Proves domain ownership and keeps your handle valid even after switching Bluesky servers.
How Bluesky Account Migration Preserves Followers
Bluesky uses a decentralized protocol called the AT Protocol. Under this system, your account identity is tied to a handle, not to a specific server. When you use a custom domain as your handle, your followers subscribe to that domain-based identity. If you move your account to a different Bluesky server, you update your domain’s DNS records to point to the new server. Followers see no change because they still follow the same domain handle. The server switch happens transparently in the background.
Without a custom domain, your handle is tied to the server where you first signed up. For example, user.bsky.social belongs only to that server. Moving to a new server would require creating a new handle and losing your follower graph. The custom domain approach decouples your identity from any single server.
The AT Protocol also stores your posts, likes, and follows in a personal data repository. When you migrate, you transfer this repository to the new server. Your followers’ servers automatically update their references to your new location. The entire process is designed so that followers do not need to take any action.
Prerequisites for Migrating Your Bluesky Account
Before you can migrate, you must meet these requirements:
- Own a custom domain. You need a domain name you control, such as example.com or yourname.com. Subdomains like user.example.com work as well.
- Access to your domain’s DNS settings. You must be able to add or edit DNS TXT records. This is usually done through your domain registrar or hosting provider’s control panel.
- Your current Bluesky account must be active. You cannot migrate a suspended or deleted account.
- A destination Bluesky server. You need a second Bluesky server where you will move your account. This can be a different server that supports the AT Protocol.
If you do not yet have a custom domain handle set up on your current account, you must complete that step first. The migration process does not work with default bsky.social handles.
Steps to Set Up a Custom Domain Handle on Bluesky
- Log in to your Bluesky account
Open Bluesky in your web browser or launch the app. Navigate to Settings > Account > Handle. - Choose ‘I have my own domain’
Click the option that says “I have my own domain.” Bluesky will display a DNS TXT record value. Copy this value exactly as shown. - Add a DNS TXT record to your domain
Go to your domain registrar or DNS hosting provider. Create a new TXT record for the subdomain you want to use. For example, if you want the handle user.example.com, add the TXT record to the subdomain “user.” Paste the value from Bluesky into the record content field. Save the record. - Verify the DNS record on Bluesky
Return to Bluesky and click “Verify DNS Record.” Bluesky checks that the TXT record matches. Verification usually completes within a few minutes. If it fails, wait up to 24 hours for DNS propagation and try again. - Confirm your new handle
Once verified, Bluesky changes your handle to the custom domain. Your existing followers and posts remain intact.
Steps to Migrate Your Bluesky Account to a New Server
- Create an account on the destination server
Sign up for a Bluesky account on the server you want to move to. Do not use the same handle. Use any temporary handle for now. - Initiate migration from the old account
On your original Bluesky account, go to Settings > Account > Handle. Click “Migrate Account.” You will be prompted to enter your password and confirm the migration. - Update your domain’s DNS record
After migration starts, your domain’s DNS TXT record must be updated to point to the new server. The new server provides a new TXT record value. Replace the old value in your DNS settings with the new one. - Verify the new handle on the destination server
Log in to your account on the new server. Go to Settings > Account > Handle. Click “Verify DNS Record” to confirm the updated TXT record. - Confirm the migration is complete
Your old Bluesky account will show a message that the account has been migrated. Your followers, posts, and lists now reside on the new server. You can delete the old account if you no longer need it.
Common Issues During Bluesky Account Migration
DNS record not propagating quickly
DNS changes can take up to 48 hours to propagate globally. If verification fails, wait a few hours and try again. Use a DNS checking tool like whatsmydns.net to confirm the record is visible worldwide.
Followers disappear after migration
If followers vanish, the DNS TXT record likely points to the wrong server. Double-check the record value matches what the new server provided. Once corrected, followers should reappear within a few hours.
Migration button is grayed out
The migration option is only available if your current handle is a custom domain. If you are using a bsky.social handle, you must first set up a custom domain handle. The button also requires that you have logged into the destination server with the same email address.
Old account still active after migration
After a successful migration, the old account becomes read-only. You cannot post or interact from it. If you want to fully remove it, go to the old server’s account deletion page and confirm deletion.
| Item | Custom Domain Handle | Default bsky.social Handle |
|---|---|---|
| Follower retention during migration | Yes, followers are preserved | No, followers are lost |
| Server portability | Full portability between AT Protocol servers | Locked to original server |
| DNS setup required | Yes, TXT record needed | No DNS setup needed |
| Handle change process | Update DNS and verify | Create new account |
You can now migrate your Bluesky account to any compatible server without losing your follower base. Start by setting up a custom domain handle if you have not done so already. For advanced control, consider running your own Personal Data Server which gives you full ownership of your data and identity.