Two ways onto your own server
The AT Protocol lets an account live on a personal data server, or PDS, other than Bluesky's own. A developer who runs a PDS has two ways to get an account there: create a new one directly on the server, or migrate an existing account, including one first hosted on bsky.social.
Choosing an account from the category only makes sense on the second route, and only when something about the existing account matters to the project: its handle, its age, or posts that should stay attached to the same identity. If none of that matters, the new-account route is simpler and avoids every risk described below. Write down which of those three properties your project needs before you open a single listing; if the answer is none, stop there.
What migration moves and what it needs
The AT Protocol's migration guide describes the steps. The repository is copied from the old server as a CAR file, media files are downloaded and uploaded again one by one, and private preferences are exported. The account keeps the same identity, its DID, on the new server, while the handle is the one requested there.
The decisive step is updating the DID so that it points at the new server. The old server signs that change only after an email challenge: a token sent, by default, to the account's confirmed email address. Without access to that mailbox, an account hosted on bsky.social cannot be moved, however well you control its password.
Migration also leaves some things where they are. The guide notes that some preferences and state can live in external services rather than on the old server, so feeds, labelers or apps that keep their own data about the account need checking separately after the move.
The risk Bluesky itself names
Bluesky's PDS repository warns that migration is a potentially destructive operation. Part of it signs away the old server's ability to update the DID, and if something goes wrong the account can be permanently locked out, with Bluesky unable to help recover it. The same document recommends against migrating a main account without understanding how PLC operations work.
Read that warning as a fit criterion. Migrating an account you have just received, whose recovery you have only just taken over, stacks two sets of risk on one identity. Rehearse the procedure with a throwaway account on a test server first, and keep the account's email and password under your own control throughout.
Write the rehearsal down as a short runbook: which server, which handle, where the email token arrives and who enters it. A runbook turns a one-time risk into a step you have already performed once on an account you could afford to lose.
When a bought account is worth migrating
It is worth considering when the account's existing handle or age genuinely matters to the project, the listing delivers mailbox access, and you can move the account email to an address you control before you start. A listing that says the address is unconfirmed works too, because Bluesky lets you replace an unconfirmed email directly and then confirm your own.
It is not worth it when the listing delivers a login only and the email is confirmed to a mailbox you cannot open, when the account's earlier posts would be out of place on your server, or when what you mainly want is an identity under your own domain. In those cases, create the account on your PDS and set a domain handle there.
A worked comparison for a club app
A hypothetical developer runs a small PDS for a cooking-club app and wants a club account on it. Option one is to create a new account directly on the server with a handle under the club's domain. Option two is to choose a bsky.social account with a pleasant handle from a listing and migrate it.
Option two changes little that matters. The handle will be requested again on the new server, and the club's domain handle is what members will recognise anyway. Meanwhile it adds an email challenge and a step Bluesky calls destructive. The developer creates the account on the PDS and keeps the category for a different need: a bsky.social test account for checking how the club's posts look to people on Bluesky's own hosting.
The comparison would come out differently for a club that already uses an established handle on bsky.social and wants to keep it. Then the email line decides whether migration is possible at all, and the rehearsal decides whether it is wise.
Terms, the order and the email first
Bluesky's Community Guidelines list selling, transferring or sharing accounts as prohibited practices, so follow Bluesky's terms for any account from the category, whether it stays on bsky.social or moves elsewhere. rStock is an independent marketplace and has no tie to Bluesky.
The delivered login and any mailbox details appear as a delivery record on your order page. Check the email state first, since migration depends on it, and open a dispute within the window shown on the order page if promised mailbox access is missing. Plan a migration only once the email is yours and confirmed. Compare Bluesky accounts on rStock by their email access line before you choose one for a server move.