The accounts worked, then stopped after the migration. The files are usually fine — the problem is that a move looks like a hijack to Telegram.
What Telegram sees
A sudden change of address, country and connection characteristics on the same session: the classic signature of a stolen account. The response ranges from a code request to terminating every session, and the further the new address is geographically, the likelier the termination.
How to migrate properly
- Keep the proxy. If the exit address stays the same, nothing changed from Telegram's point of view — it never sees your server.
- Not all at once. In batches, with a status check after each.
- Never run two copies. An old instance still running invalidates the new one, and vice versa.
If a session is already gone
The file cannot be restored; you need to re-authorise with a code. After that, give the account a few quiet days on soft limits: a fresh authorisation raises the same scrutiny as a new account.
Avoiding a repeat
Pin the proxy to the account rather than to the server. Then infrastructure moves stop being events for Telegram: the machine changes, the exit point does not. What else feeds account trust is on the automation page.