Switching DM tools sounds scarier than it is. The fear is always the same: that you'll flip a switch, drop a bunch of conversations on the floor, and spend a week cleaning up. So let's defuse that first — you don't cut over until HyperDM is already answering your real DMs correctly in preview. Nothing goes live blind.
This guide is the whole route: what to take with you, what to leave behind, and the order to do it in. Budget an afternoon. Most of it is waiting for a couple of connections to confirm.
Before you start: what actually needs to move
The instinct is to migrate everything. Don't. Most of what lives in a ManyChat account is scaffolding you won't need once an agent is doing the talking. Here's the honest sort:
- Keep — your product catalog, pricing, shipping and returns policies, sizing info, brand voice, and any canned answers your team trusts. This becomes HyperDM's knowledge.
- Keep — your high-intent triggers: the keywords and comment-to-DM phrases that actually drive replies (“LINK,” “PRICE,” a launch codeword).
- Leave — most of your flowchart logic. You're not rebuilding the maze; you're describing the business and letting the agent navigate.
- Leave — dead contacts. There's no reason to import a list of people who messaged once a year ago; HyperDM doesn't bill by contact, so there's nothing to gain by hauling them over.
Step 1 — Export your knowledge from ManyChat
Open ManyChat and pull the substance, not the structure. Copy your catalog details, FAQ answers, shipping and returns text, and the keyword list that matters. If your answers live inside flow nodes, just lift the text — you're harvesting facts and phrasings, not screenshots of the tree. A plain doc is fine; you'll paste from it in Step 3.
While you're in there, note which channels are actually connected (Instagram, WhatsApp, your Facebook page) and which phone number or IG account each one uses. You'll re-point those, not rebuild them.
Step 2 — Connect your channels to HyperDM
Create your HyperDM account and connect a channel. This is the part people brace for and it's the most boring step in the whole process — it's an official OAuth handshake, two clicks, no passwords handed around and no unofficial access:
- 1Pick your first channel. Most brands start with Instagram because that's where the comment-to-DM volume is.
- 2Authorize through the official Meta login. You'll approve HyperDM for messaging the same way you approved ManyChat — through Meta, not around it.
- 3Add WhatsApp too if you use it. WhatsApp runs on the official Business API, so your number and templates carry over cleanly.
On the free tier you can have one channel live at a time, which is plenty for a migration — get Instagram right, then add the rest. The pricing page spells out when you'd want every channel running at once.
Step 3 — Teach HyperDM your business
This is the step that replaces hours of flow-wiring with a few minutes of writing. Paste in the knowledge you exported in Step 1: catalog, policies, sizing, voice. Then describe how you want it to behave in plain sentences — the same way you'd brief a new hire on their first day:
- “Always offer free shipping over $75 when someone's close to the threshold.”
- “If someone asks about wholesale, send them the form and tag the chat for the team.”
- “Match our tone — warm, a little playful, never pushy.”
You're not anticipating every question here. You're giving the agent its source of truth and its manners, then trusting it to answer whatever comes in. If you want the reasoning behind this approach, our piece on why you shouldn’t have to choose makes the full case.
Step 4 — Preview against your real DMs
Here's the safety net. Before HyperDM sends anything on its own, you watch it draft replies to your actual incoming messages. Read them like a manager reviewing a new rep's first shift. Where it nails the answer, great. Where it's thin, go back to Step 3 and add the missing fact or adjust the instruction.
Spend real time here — an hour of preview saves a week of cleanup. You're looking for two things: that the facts are right, and that the voice sounds like you. When both are true across a dozen varied conversations, you're ready.
Step 5 — Go live, and turn ManyChat off
- 1Flip HyperDM to live on your first channel. It now answers new DMs on its own, handing off to your team when it should.
- 2Watch the first day. Keep an eye on the inbox, jump in on anything edge-casey, and feed corrections back into the knowledge.
- 3Pause auto-replies in ManyChat. Don't delete the account on day one — just stop it from replying so two tools aren't talking over each other.
- 4After a clean week, cancel ManyChat. Your bill stops growing with your audience, and you keep your contacts where they belong — in conversations, not on an invoice.
The three questions everyone asks first
Will I lose my conversation history?
No. Your DM history lives on Instagram and WhatsApp, not inside ManyChat — it's tied to the account, so it's all still there when HyperDM connects. You're changing who answers, not where the messages live.
Do I have to rebuild my keywords and comment-to-DM triggers?
You re-create the few that matter, and it takes minutes, because a trigger in HyperDM is just a phrase plus an instruction — no node graph behind it. Most brands find they had a dozen flows but only three or four triggers that actually drove revenue; you bring those over and drop the rest.
Can I go back if I don't like it?
Yes, trivially — that's the whole reason you pause ManyChat instead of deleting it on day one. Nothing about connecting HyperDM is destructive, so the migration is fully reversible right up until you cancel your old plan. There's no lock-in to fear.
The honest version
The technical migration is genuinely easy — connecting channels and pasting knowledge takes an afternoon. The part that takes care is the preview: resisting the urge to flip it live the moment it's connected, and instead reading enough real replies to trust it. Do that, and you'll never have a “we dropped all our DMs” horror story.
When you're ready, the switch page walks you straight into a free migration — same steps, with the channel connection built in. No card, no risk, and ManyChat stays right where it is until you decide otherwise.
Run the automations. Let the AI close.
Comment-to-DM, keyword replies, follow gates — set up in minutes, then the AI answers from your real catalog. Free on one channel, 50 conversations a month, no card.