Migrating a Telegram bot to MAX

Porting a Telegram bot to MAX is an adaptation job, not a rebuild. Dialog flows, texts, and CRM hooks move over as they are; what changes is the transport layer (API methods, limits, payment rails) and the publishing step, since bots in MAX are released by a verified Russian legal entity. The code takes days; the overall timeline is set by publishing and by moving your audience.

A messenger shift worth knowing about

MAX, the messenger built by VK, became the largest messenger in Russia by monthly audience: 86.2 million users in June 2026 against Telegram’s 75.7 million (Mediascope via Habr). For the first time, a market that built its bot culture on Telegram has a bigger pool next door.

The bot market inside MAX is nearly empty. The catalog listed 53 bots in mid-August 2026 (max-catalog.com) for an audience of 86 million; you can scroll the whole thing in an evening. Early entrants get visibility that latecomers will pay for. Demand follows the audience: seven fresh MAX-bot orders appeared on the Kwork freelance marketplace in one week by 22 August 2026, from simple ports to a CRM-linked build budgeted at 70,000 rubles, while studios anchor the top of the market at 50,000 rubles for a basic bot, 100,000 to 200,000 with CRM, and 300,000 for a mini-app (RBC Companies, March 2026).

When the move makes sense

The port pays off in a narrow set of cases, and it is better to name them plainly.

• You serve Russian customers and part of the base has drifted to MAX, where you currently have nothing running.
• You need payments inside a Russian messenger. Telegram’s rails are not the local standard; MAX takes payment through SBP, the Russian fast payment system.
• You hedge platform risk with one business logic and several messenger adapters, so switching a channel is configuration, not a rewrite.

If none of these describe you, a Telegram bot that works is worth more than a MAX bot nobody needs.

What ports over unchanged

Everything not tied to the specific messenger survives the move untouched: the dialog logic (branches, step order, conditions, menu behavior), the texts and broadcast content, the external integrations (CRM, booking calendar, spreadsheets, payment gateways outside the messenger), and the hosting and data the bot already runs on.

If the original bot kept its business logic separate from the transport, the port is mostly a swap of that transport. MAX runs an open Bot API with documentation and an SDK, so the path is marked.

What changes in the port

• API methods. The MAX Bot API resembles Telegram’s in spirit, but the methods, event formats, and rate limits differ. Copying the code and swapping the token does not work.
• Payments. Telegram’s payment mechanics do not apply; inside MAX the standard is SBP, so a selling bot gets its payment branch rebuilt under local rules.
• Mini-apps. Telegram WebApp and MAX mini-apps are different platforms, so the interface is adapted separately from the bot itself.
• Broadcasts. The mechanics carry over, but delivery rules and limits are the platform’s, so broadcast flows get tested on a live base.

All of this is adaptation work, not a new project.

The rule that decides your timeline

Publishing a bot or a mini-app in MAX requires a verified Russian legal entity, a requirement in force since late summer 2025. For a foreign company this is the part to settle before any code is written.

• The developer builds and prepares the bot, but publication happens under a Russian entity you control or partner with; the platform cabinet belongs to your organization.
• Verification and moderation on the platform side add time that neither you nor the developer controls.
• If no Russian entity is available, settle the publishing path before the work starts; part of the route runs through the MAX Partner Platform, which has its own terms.

Checking this point costs nothing and saves weeks, which makes it the first line of any migration checklist.

Moving the audience

Subscriber bases do not transfer between messengers, so the audience moves by hand: a link to the new bot in the channel header and the pinned post, a broadcast to the old base explaining the move, QR codes at cash desks and in documents, and an auto-reply in the old bot pointing at the new one.

Both channels run in parallel until activity in the old one drops to occasional messages, which takes weeks or months. Pushing harder does not help; audiences move when they decide to.

Realistic timelines

Code is not the long part. A developer who has already built Telegram bots rewrites the transport in days, since the logic is known and only the adapter changes. The tail is everything around it: entity verification, platform moderation, audience migration, and the parallel-run period.

The short version

Migrating a Telegram bot to MAX means adapting the logic to another API, publishing under a verified Russian legal entity, and walking your audience over with links. The code takes days; the platform part and the migration take longer. I build Telegram bots and WhatsApp bots on the same adapter architecture; the bots catalog lists the flows. If you run a bot for Russian-speaking customers and want the same flow in MAX, tell me about it.