A working Circlus server
The new server is installed, updated to the current version, and connected in the app under Server Management.
Circle migration guide
Move your Circle to another server.
This procedure moves an existing Circle with its members and supported data. The destination Circlus server and its HTTPS addresses must be ready first.
What must be ready before the move
Do not create a new empty Circle with the same name. The destination administrator creates a one-time import permission; the existing Circle appears there after activation.
A new address
The new Circle domain points to the new server and has HTTPS set up.
A trusted coordination channel
The destination administrator can securely pass the one-time migration details to the Circle owner.
A downtime window
Messages, calls, and settings changes are temporarily unavailable while the Circle’s data is transferred and verified.
No destination server yet? Follow the self-hosting guide first. The server README remains the source of truth for deployment commands.
What happens to your data
Before the move, the app checks the new server, shows a report, and asks the owner to confirm what will be lost.
Transferred
The Circle, participant profiles and their roles, connections, settings, messages and keys, encrypted profile backups, guest links, and the Circle’s public page.
Not transferred
Existing server attachments, message archives, call history and call links, active invites, and system events. Messages older than the new server’s retention period are not moved either.
The check report in the app shows the exact data scope for your Circle.
For the destination administrator
The destination side authorizes an import. It does not create a replacement empty Circle.
Open Server Management
From the administrator profile of the server that will receive the Circle.
Select “Allow a Circle transfer to this server”
Open it under Actions, then enter the new Circle domain, display name, retention limits, and destination policies. The service endpoint comes from the selected server.
Create the migration permission
The server verifies the addresses and creates a permission ID, one-time migration code, and service endpoint.
Send the details to the Circle owner
Use a trusted channel. The one-time migration code is not shown again in the permission list.
Monitor the import
After the owner starts the move, Server Management shows the destination status and import report.
For the Circle owner
These actions begin on the current source server after the destination administrator has sent the import permission.
Open Circle settings → Move Circle
Start from the existing Circle on its current source server.
Enter the destination details
Use the service endpoint, permission ID, one-time code, and new domain supplied by the destination administrator.
Run the destination check
The app checks the permission, the address, the server version, limits, and data scope. The Circle keeps running meanwhile.
Review the report and warn participants
Accept non-transferable data only after reviewing the report and arranging the downtime window.
Sign and schedule the move
The owner signature binds the destination, domain, and accepted data-loss policy.
Stop the Circle and transfer
While data is exported, transferred, and checked, the Circle on the old server is read-only.
Confirm cutover
After a successful move, activate the new server. It becomes the primary one, and for a while the old server tells participants’ apps the new address.
The check stops nothing. The Circle becomes unavailable only after the separate “Stop Circle and transfer” action.
After the move
Complete the operational checks before treating the destination as fully settled.
- Open the Circle at its new address and verify core chats and members.
- Save the migration report and review import warnings.
- Save a new recovery package — it must contain the new Circle address.
- Let participants know: the app will show them “Circle moved to a new server” and ask them to tap “Verify and switch”.
- Keep the old server and domain online until participants have switched to the new address.
- Check push delivery, calls, new attachments, and public-site publication.