Switch from Manychat to vkit: a careful migration checklist

Check whether switching solves your actual problem

Write the reason for moving in a sentence. Perhaps you want your Instagram replies closer to your content calendar, or you want unlimited contacts without per-contact charges. vkit Pro includes both. A clear reason gives you a test; a long list of possible features does not.

List the capabilities your current campaigns rely on: channels, trigger types, conditions, contact fields, integrations and human handoffs. Mark each as essential, useful or unused. Confirm the essential items in the new product before planning a cutover. Do not interpret a similar product label as proof of identical behaviour.

Manychat may remain the better fit when its established flows or wider messaging setup are central to your business. Use the vkit versus Manychat comparison for a product-level decision. The rest of this checklist assumes you have selected a simple Instagram workflow that both your account and the new setup can support.

Save an inventory you can actually rebuild

For every active campaign, record the original post URL, trigger phrase, reply text, button label and destination. Include exceptions: excluded words, different replies, handoff instructions and any connected system. A screenshot helps, but readable text makes rebuilding and reviewing easier.

Capture the current status and a baseline from whatever reporting you already use. Note which campaigns are still receiving comments and which ones can wait. Save the inventory somewhere your team can access if an account connection becomes temporarily unavailable.

Keep the record proportionate. A campaign inventory does not require a copy of every follower conversation. If you export customer data, use supported export controls and your existing privacy rules. Moving data and being allowed to contact someone are separate questions; an export does not create a new messaging permission.

• Campaign instructions

  Save the post, keyword, approved message and intended destination.

• Dependencies

  Record conditions, external tools and the person responsible for exceptions.

• Recovery information

  Record the old configuration and the steps needed to restore it if the test fails.

Rebuild one clear promise in vkit

Pick a low-risk campaign: one keyword delivering one useful resource. Avoid the highest-volume launch as your first attempt. Connect the professional Instagram account through the product’s supported authorization flow and confirm that you selected the intended account.

Follow the vkit setup guide: choose the trigger, post, keyword and message, then review. Copy the reviewed message and destination, then check the final link independently. Do not assume a contact tag, branch, webhook or email step has followed you simply because the first DM looks the same.

If a required step is missing, stop that campaign’s migration. Keep it on its current provider while you assess an alternative. The purpose of the first rebuild is to prove compatibility, not to force a working system into a smaller set of controls. Use the Instagram comment-to-DM overview to keep the basic journey clear.

Test the follower experience before the switch

Run the test on a designated post and account setup before changing a public campaign. Check a matching comment, a non-matching comment, message delivery and the destination on mobile. Use fresh eligible test interactions rather than assuming repeated comments from one account will behave like new audience activity.

Check what happens when the recipient does nothing, opens the destination or writes back. A click to a website and a reply to a message are different interactions. The first delivered reply should not be treated as permission for an unlimited follow-up sequence.

Test failures need an owner. Record what happened, which account was used and what you changed. The Auto DM launch test sheet provides a repeatable checklist. Do not promise your audience that a campaign is active until the tested path delivers the resource correctly.

Give each live trigger one owner

Plan a short change window when someone can watch the campaign. Record which provider owns the post’s trigger before and after the switch. Avoid leaving two overlapping automations active and hoping the platform chooses the one you intended.

Pause the old campaign before enabling the replacement for that same trigger. Confirm the new connection and test the intended public path. If reconnecting an account affects other integrations, assess those dependencies before proceeding; changing a provider can involve more than toggling a single rule.

If the new path fails, pause it and restore the prior setup using your saved record, then verify again. Keep a manual way to help people who requested the resource during the gap. Do not attempt to compensate with a bulk message to historic commenters. A migration is an operational change, not a reason to bypass messaging eligibility.

Review results, then retire the old setup

Watch actual requests after the switch. Compare delivery and destination behaviour with the baseline, read questions that need a human answer and check for duplicate replies. Low-volume campaigns may need more time to produce useful observations; a quiet dashboard alone does not prove the setup works.

Move the remaining compatible campaigns in small batches. Keep a record of completed, deferred and unsupported workflows so nobody assumes the whole account moved because one post succeeded. Only remove old permissions and subscriptions once their active dependencies have been checked.

Budget decisions belong at this point too. Use the Auto DM cost worksheet to compare the subscription and operating effort after the trial. Success is a campaign your audience can use and your team can maintain, not merely an old account you managed to cancel.

Frequently asked questions