I imported a flow, but the bot is still following the old funnel
Importing a flow between bots or from a personal account to Standard transfers the funnel structure — steps, branches, and texts. But some settings are tied to a specific bot and are not transferred a
Importing a flow between bots or from a personal account to Standard transfers the funnel structure — steps, branches, and texts. But some settings are tied to a specific bot and are not transferred automatically — you need to review them manually after the import.
What you need to check manually
Steps Change flow — transfer to another flow — the link to the flow is tied to an ID. After import, the new bot does not have this ID, and the step shows “not selected”. Open each Change flow and select the target flow again.
Steps Condition — conditional branching (Custom condition) — conditions that reference Custom Fields, tags, and statuses. After import, the fields may not exist in the new bot — check each condition and, if necessary, create the missing ones in Custom Fields — custom fields.
Steps Send message — sending a prepared message with Inline Buttons or Reply Keyboard — buttons are saved as a structure, but callback-data and links may lose the context of the specific bot. Open each message with buttons and check that the buttons are set up correctly.
Steps Operator — assigning an operator — assigning an operator is tied to the team of a specific bot. After import, check that the selected operator exists in the team of the new bot; otherwise, the step will not work.
Steps Webhook — Sending Data Out — the URL and headers are transferred, but if they work through a bot-specific token, you need to check and update the token.
What is transferred without loss
Message texts (Send Message), step delays (Delay), tag changes (Change tag), sale status changes (Change sale status), AI Reply / AI Routings — the structure of prompts and conditions. In other words, the core of the scenario usually migrates cleanly; refinements are needed only in places with a local binding.
What to do after import
Review all steps in the list
In Flow Settings open the imported flow. Check by step type: first Change flow, then Condition, then Send Message with buttons. These are the most common points where bindings are lost.Check Custom Fields and Tags
If conditions use Custom Fields (Custom Fields — custom fields) and Tags (Tags — tags for segmentation) — make sure all of them have already been created in the new bot. If necessary, create the missing ones before testing the flow.Run a test pass
Open the bot in Telegram from a test account and go through the funnel. At each branch, check that you end up where you planned. If the bot follows the “old” path, it means some branch still has an unlinked step. Most likely, an old Change flow is referencing the original flow by ID.
To prevent this from happening again
When migrating, always keep a description of which Custom Fields and Tags are needed for the flow to work. Create them in the new bot before importing the flow — then the conditions will be linked by name during import, and there will be less manual work.
Frequently asked questions
Related
Was this article helpful?





