Home · How to replace ManyChat in Russia and how to transfer bots: step-by-step plan
How to replace ManyChat in Russia and how to transfer bots: step-by-step plan
ManyChat is built around the social networks Meta* and WhatsApp, and payment from Russia has become a separate problem. “Russian analogue” in search means three things: rubles, interface and support in Russian, messengers used here. CHBT closes Telegram, MAX, VKontakte and chat on the site, and places its main emphasis on trading: the AI seller responds according to your product catalog, and Wildberries and Ozon connect using the seller’s key. There are no Meta* channels in it and there won’t be - this is a solution. Below is what is transferred, what is not, and a step-by-step plan.
What is portable and what is not?
The main table of this page. Everything below is comments to her lines.
| Entity in ManyChat | Transferred? | How does it work in CHBT |
|---|---|---|
| Telegram bot and its subscribers | Yes, completely | The same @BotFather token in “Channels” → “Connect Telegram” - subscribers, t.me link and QR remain |
| Flows (scripts) | Manual | Blocks “Message”, “Condition”, “Data collection”, “Pause”, “Action”, “Operator”; draft - via “AI script” |
| Tags | Yes | The “CSV Import” block in “Contacts” (insert CSV text, column uid - Telegram ID) or the “Add tag” action in the script |
| Custom fields | Partial | Name, phone, e-mail - import; everything else is collected again by the block “Data collection” → “Own field” / “To variable” |
| Keywords, Default reply | Yes | Triggers "Keywords" (exactly / contains / regex) and “Any message” |
| Growth tools: links, QR | Yes, recreated | Deep link trigger with payload, section “QR campaigns”, a widget on the site with the “Open Widget” trigger |
| Social network audience Meta* | Directly - no | Translated by links and QR in Telegram/MAX |
| Product catalog, prices, availability | Appears in CHBT | Uploading the store via the link, Wildberries seller file or key - AI seller (from Basic) responds with your price and availability |
| Broadcasts | Yes, with reservations | Distribution section: text with {{name}}, by tags, delayed start; without media and buttons |
| Sequences (drip chains), Smart Delay | Yes | flow: “Pause” + “Condition” by tag + “Message” - see. section below |
| Live Chat | Yes | “Conversations”: all channels in one list, the “Operator” block transfers the conversation to a person, Web Push and PWA |
| Integrations (Zapier, Make) | Yes | Action “HTTP request” - POST JSON in Make, n8n, Albato; incoming webhook runs script from outside |
| History of conversations | No | Save upload ManyChat |
| Payments in bot | No | The “Payment” block and the shop in your bot: payment on your provider’s page |
| WhatsApp, Meta messengers*, SMS, e-mail | No | Does not connect; channels CHBT - Telegram, MAX, VKontakte, widget on the website |
Why do they leave and what does CHBT give in return?
The reasons are similar for everyone: it is difficult to pay for a subscription from the Russian Federation, the main ManyChat channels in Russia are either blocked or not used by business, the interface and support are in English, and personal data of clients must be stored in Russia.
What CHBT gives instead: payment with a Russian card via CloudPayments, Plans 0 / 650 / 1290 ₽ per bot per month with auto-renewal, which is disabled in the “Payment” section; Telegram, MAX, VKontakte and widget on the site from one script; office in Russian; servers in the Russian Federation. There is a “Conversations” inbox, “CRM” kanban, tag broadcasts and an AI agent for the knowledge base.
And there is something that ManyChat does not have at all: product catalog. Uploading a store via a link (YML, Google Merchant, CSV - Bitrix, InSales, Ecwid, Tilda and other engines), file or Wildberries seller key - and the AI seller (from the Basic plan) names the price, availability and characteristics itself. Using the seller’s key, Wildberries and Ozon are connected: from them you receive a summary of new orders and reviews, from Wildberries you also receive a catalog with prices; Yandex Market, Kaspi.kz and Uzum Market - only a directory file. Each key displays a matrix of seven sections; the catalog and prices in it are marked “not verified” until the first download takes place.
What is not and will not be: Meta* and WhatsApp channels, SMS and e-mail newsletters, marketplace chats. The cash register remains yours: the “Payment” block and the shop in your bot send a link to the provider’s page, and money, receipts and refunds are on the payment service’s side; in Telegram you can also accept Telegram Stars. Why we don't make bots for Meta* is explained in separate article.
Sequences → “Pause” + “Condition”: how to translate a drip chain
The most common difficulty when moving is not Flows, but Sequences: in ManyChat this is a separate entity with subscription and unsubscription, in CHBT there is no separate entity, the chain lives inside the script. Translation step by step using the example of “3 emails after the lead magnet”:
- Subscribe to Sequence → in CHBT nothing: the chain continues the same flow after the material is issued. Click “Action → add tag”
magnetto see who entered it. - Delay 1 day → “Pause” block for 1 day. Make a message before the “Pause” without buttons: the script is waiting for a timer, not a press.
- Condition “if you haven’t bought” → “Condition” block: there is a tag
lead- the “yes” branch completes the chain; “otherwise” - the following “Message”. - Unsubscribe from Sequence → the same tag: the lead puts
lead, and each subsequent “Condition” lets the person through. Separate unsubscribe - trigger “Keywords” on “stop” → “delete tag”. - Smart Delay “during business hours” → “Condition” by time of day before the message: from 23 to 8 - another “Pause” for several hours.
Branching is available in both editor modes; with three or more branches, “Canvas” (Basic plan) is more convenient. Analysis of timings and typical schemes - in the article about trigger chains, ready-made template - template "Auto Funnel".
Moving checklist
- Audit. Write down scripts, entry points (keywords, links, QR), tags and fields, integrations; Opposite each flow is the goal and number of operations per month. Don’t move dead branches, leave 8–12 working tags (how to build a tag system).
- Screenshots of the branchesthat remain - blocks are collected from them.
- Scripts in CHBT. Welcome - trigger “Command /start” and “Message” with buttons; answers to words - “Key words”; phone collection - “Data collection” with format checking; branching - “Condition”; reheating - “Pause”; manager - "Operator". Draft – “AI script”, check – “Check script”. Replace bulky FAQ branches with the “AI agent” block.
- Deeplinks. Create “Deeplink” triggers for payloads from old links
t.me/bot?start=…so that advertising and QR continue work. - Tags and contacts. Upload subscribers from ManyChat to CSV and paste the text into “Contacts” → “Import CSV” (heading
name,email,phone,channel,uid,tags,uid- Telegram ID, tags separated by semicolons). Correspondence history and custom fields are not transferred; subscribers without a Telegram ID will appear in the database the first time they message a new bot. - Token. “Channels” → “Connect Telegram” with the same @BotFather token: subscribers and the link remain, the bot in ManyChat stops responding - the bot has one webhook. Switch after checking the scripts; simple - minutes. Where to get a token - help.
- New channels. MAX - token from business.max.ru (channel page), VKontakte - the “Connect via VK” button or a community key, CHBT will set up the Callback API itself, website - one line widget. The flow is the same.
- Audience from social networks, which are not in CHBT. Subscribers cannot be unloaded - only invited: deep link
?start=socwith a source tag, a lead magnet as a reason to click, a link in the profile header and stories, a QR from the “QR campaigns” section, two buttons - “Telegram” and “MAX”. The mechanics are detailed in the article about the translation of subscribers. - Catalog. If you are selling something, connect the products in the “Marketplaces” section before the first advertisement on the new bot: a link to upload the store or a Wildberries seller key. Products will arrive in drafts - view and publish, one at a time.
- Mailings. Reassemble in the “Mail broadcasts” section by tags, send the first one to a small segment.
- Command and verification. Operators are invited to “Access”, Web Push is enabled in “Conversations”; each flow was completed from someone else’s account; all external links lead to the new bot.
A simple bot moves in 1-2 hours, an account with 5-10 flows - in an evening or two; Most of the time is spent not on blocks, but on transferring the audience from social networks. Comparison with other Russian designers - in the article about chatbot constructors in Russia, Plans - on the page price.
Start transfer for free - Free plan, all channels, no card needed.
*Meta is recognized as an extremist organization and is banned in the Russian Federation.
FAQ
How to pay for CHBT from Russia?
Russian card via CloudPayments in the “Payment” section: 650 ₽ (“Basic”) or 1290 ₽ (“Business”) per bot per month. Auto-renewal is disabled there; cancellation does not expire the paid period. Free plan - no card required.
What to do with automations in Meta* social networks - replies to comments and in private messages?
There won’t be any in CHBT: we don’t make chatbots for Meta services and we don’t promise any deadlines. Leave in your profile a link and QR to the bot in Telegram or MAX with a deep link and source tag; the automation itself moves to the messenger, where the bot responds to the catalog and collects leads.
How to translate Sequences and Smart Delay?
Inside the script: “Pause” for the required period, then “Condition” by tag (for example, there is no “lead” tag - send the next message), “Condition” by time of day instead of Smart Delay. Subscribing and unsubscribing from a chain are tags that are set and removed by the script.
Where do Custom Fields go?
Name, phone and email are imported CSV into the contact card. The remaining fields are collected anew by the “Data Collection” block with the “Custom Field” type - the value is stored in the card and, when “In Variable” is enabled, is available to the “Condition” and the {{имя}} substitution.
Do I need to disconnect the bot in ManyChat before connecting to CHBT?
No. When the token is connected, CHBT reinstalls the webhook on itself, and ManyChat stops receiving messages automatically. First build and test the scripts in CHBT, then connect the token.
PlansTemplates CHBTComparison of constructorsTelegram botMAX botReplacing Carrot quest and Jivo