Move an AT Protocol account between hosts
A move to a compatible host can preserve your DID. Prepare repository records, referenced files, identity updates and recovery material before retiring the old host.
By Link Jar. Updated 31 October 2026.
Does Link Jar offer a one-click migration?
There is no guided migration wizard promised in the current hosting beta. For help moving into or out of linkjar.social, contact hello@linkjar.io. Do not create a second identity and assume its data or followers will merge with the first.
You can use Link Jar with an existing Bluesky account without changing hosts. Sign in with that account if saving links is all you need.
What stays the same when I move?
An AT Protocol migration can preserve the account’s permanent DID. The
current host is recorded in its identity document. A provider-owned handle,
such as a name ending in .linkjar.social, may need to change when you leave.
The destination must accept the account and support its data. Do not assume all app-specific settings, private messages or other data live in the PDS. Some state is held by other services.
What should I prepare?
- Confirm the destination accepts migrations and ask for its current instructions.
- Keep access to the current host and the account’s identity controls.
- Export the repository and its referenced files. A repository CAR file alone does not contain file bytes.
- Keep your Private Jar Recovery Kit separately. Moving encrypted records does not recreate their keys.
- Decide which handle to use and who controls its domain.
The official migration guide describes the protocol stages. It is technical guidance, not a claim that each provider offers the same interface.
What happens during the move?
The high-level process creates the destination account for the existing DID, copies repository records and files, changes the identity’s host and signing information, then activates the new host and deactivates the old account. Follow the destination’s current procedure for the exact sequence.
This is different from Link Jar’s readable JSON export. That export is useful for reading selected library data; it is not a complete account-migration package.
What should I check afterward?
- The DID resolves to the new host and the chosen handle resolves to that DID.
- Repository records and referenced files are present.
- You can sign in and create a new record in the apps you use.
- Your Private Jar unlocks with your existing recovery material.
- Your important app settings and separately hosted data remain available.
Some clients need you to sign out and back in. Caches can delay recognition of the new host. Do not delete the source account or discard its exports until you and the destination provider have checked the result.
What if my old host is unavailable?
Recovery depends on the identity controls and backups you have. A portable protocol does not make lost records, missing files or lost keys reappear. Ask for help before making identity changes you cannot reverse. The account specification describes the underlying migration and lifecycle rules.