How to move from Manychat to Wagent: a staged migration checklist

List active entry triggers, lead-magnet delivery, tags, follow-up sequences, human handoffs and calendar links. Record which automations are still useful and which problem you want the new setter to solve.

Keep your existing configuration and any necessary exports according to the tools’ supported options. Connecting Wagent should not be treated as a transfer of all contacts, consent records, tags or chat history.

Prepare the programme description, real price and terms, fit questions, exclusions, approved objections and booking link. Add clear instructions for unknown information and requests for a human.

Use the connection flow available in your Wagent dashboard. Requirements can vary by channel and account. Review the connection method and platform conditions; no automation vendor can promise that a platform will never restrict an account.

Use controlled accounts to verify the complete path from enquiry to reply, qualification, booking link and confirmed appointment. Test a voice note, an image, an unsuitable lead and human takeover.

Check for overlapping replies and queued messages from the old setup. If you still need Manychat for triggers, validate the handoff instead of disabling a working entry campaign blindly.

Start with a manageable scope and a human available for exceptions. Review offer accuracy, repeated questions, missed handoffs and confirmed appointments. Update the instructions and rerun failed scenarios.

Decide whether to retain, pause or remove the old automations only after the replacement meets your requirements. The migration duration depends on the complexity of your current setup, not a universal fifteen-minute promise.