How to Switch DM Automation Tools Without Losing Your Flows or Contacts

Most of a migration is fine. The two things that go wrong are predictable, and both happen in the first hour.

By Anthony Casauria · · 8 min read

Share
Smiling woman in black cargo pants tapes a moving box shut in a bright office, checking the phone in her hand.

Key takeaways

  • Contacts, tags and custom fields move between DM automation tools by CSV export and import, but flows have to be rebuilt by hand.
  • Platform-scoped contact IDs, open 24-hour messaging windows and permission to message anyone on Instagram stay behind when you switch, and importing a username grants nothing.
  • The contact export should happen while the old subscription is still active, because access to the old tool usually ends with billing.
  • Both tools can run side by side for a few days on different posts, but never on the same post, because Meta allows one private reply per comment.
In this article
  1. What actually moves, and what doesn't
  2. Why platform IDs and open windows stay behind
  3. How to switch DM automation tools in seven steps
  4. Is switching safe for your Instagram account?
  5. What a contact export really contains
  6. A clean way to switch DM automation tools

Nobody loses their audience when they switch DM automation tools. What people lose is an afternoon, a few open conversations, and occasionally their nerve on the day two tools reply to the same comment.

The migration itself is mostly clerical: export a list, rebuild a handful of automations, reconnect Instagram through Meta's login. The parts that genuinely cannot move are narrow and knowable. Once you know what they are, the job stops feeling risky.

Below: the order to do it in, what transfers and what does not, and how to run both tools side by side for a few days without annoying the people who comment on your posts. The sequence is tool-neutral and works whichever direction you are going.

Short answer: contacts, tags and custom fields move by CSV export and import. Flows do not: no tool imports another's flow format, so you rebuild your top automations by hand. Open 24-hour messaging windows and platform-scoped IDs stay behind. Reconnecting Instagram is an OAuth change; it does not by itself put the account at risk.

What actually moves, and what doesn't

A migration has three buckets, and confusing them is what causes the panic.

ThingMoves?How
Contacts and handlesYesCSV export, then CSV import
Tags and custom fieldsYesExtra columns on the same CSV
Email addresses and consentUsuallyA column per address, with where and when permission was given
Flows and automationsNoRebuilt by hand in the new builder
Message historyNoExports hold contact records, not message bodies
Platform-scoped contact IDsNoMeta issues a different ID to each app
Open 24-hour messaging windowsNoThe window belongs to the conversation, not the tool
Permission to message someone on InstagramNoImporting a username grants nothing

The last three are the ones worth sitting with. The others are a spreadsheet problem.

Why platform IDs and open windows stay behind

Meta issues each approved app its own scoped ID for the same person, so the identifier your old tool stored is meaningless to your new one. Your new tool matches Instagram contacts by username instead, which works, with one honest limitation.

In HyperDM, an imported username that belongs to someone who has already messaged you merges into their existing contact. A username nobody has messaged you from is added as a record marked Unverified, because Instagram only permits messages to people who messaged you first. The import stores the person so you have the tags and the history of the relationship; it does not create permission to DM them. The same rule applies to open conversation windows. Under Meta's messaging policy, a business can reply to a person for 24 hours from that person's last message, and that clock belongs to the conversation on Meta's side, not to the software. Anyone mid-window when you switch does not carry over as a reachable contact; they come back the next time they message you, and their thread arrives as its own contact. If you want HyperDM's exact matching rules before you build the file, they are in the import contacts guide.

How to switch DM automation tools in seven steps

Do these in order. The sequence matters more than the speed, and the only irreversible step is the last one.

Step 1: Inventory what you are actually running

Open your current tool and list every live automation, not every automation you built. Most accounts have between three and eight that do real work and a drawer full of experiments. For each live one, write down the trigger (which post, which keyword, which story), the exact message text, any links, and the tags it applies. Screenshot the flow canvas. This document, not the export file, is what you will rebuild from, and it takes about twenty minutes.

Step 2: Export your contacts, tags and fields

Pull a CSV out of the old tool while the subscription is still active, because access usually ends with billing. Check it contains the handle, the tags and any custom fields you actually use in messages. If you export ManyChat contacts, do it before you downgrade rather than after, and keep the raw file as a backup alongside whatever you reshape for import. Our step-by-step switching walkthrough shows the column mapping in detail.

Step 3: Reshape the file for the new tool

Rename the columns to match what the new importer expects and drop the ones it cannot use. Where importing is turned on for your workspace, HyperDM's importer takes a CSV with column names in the first row, separated by commas, semicolons or tabs, up to 5,000 rows, 50 columns and 2 MB, so a big list needs splitting into several files. Run the dry run before the real import: it lists every problem row and lets you fix them in the spreadsheet rather than in the database.

Step 4: Rebuild your top three automations

Not all of them, three. The comment-to-DM on your best-performing post, your main keyword trigger, and your story reply if you run one. Rebuilding is where the time goes, and three is enough to prove the new tool works with your actual audience. The rest can be rebuilt over the following fortnight while the old tool is still handling them.

Step 5: Connect Instagram and test on one live post

Connect through Instagram's own login and authorise the permissions. Then test on a post with real traffic rather than a dummy post nobody sees, because a dead post cannot tell you whether replies deliver. Comment from a second account, watch the DM arrive, click the link, and check the contact appears with the right tags.

Step 6: Run both tools for a few days, on different posts

Keep the old tool live on its existing posts and point the new one at new posts only. Never both on the same post. Meta allows one private reply per comment, so if two tools race for the same comment one of them simply fails, and you learn nothing except that something is broken. Separating by post gives you a clean comparison of delivery and reply rates.

Step 7: Disconnect the old tool

Once the new automations have handled a few hundred real comments, turn the old tool's automations off first, wait a day, then disconnect the channel and cancel the subscription. In HyperDM, disconnecting is More actions (⋯) → Disconnect on the connected Instagram row, with a confirm dialog that asks you to type the account name; it drops the stored token and stops inbound DMs until you reconnect. Expect the same shape of control in any official-API tool.

Is switching safe for your Instagram account?

Yes, with one condition: both tools must be official-API tools. Reconnecting is an OAuth change, and Instagram treats it as routine.

When you connect an official tool, Meta issues it an access token scoped to the permissions you approved. Revoking that token and issuing another to a different approved app is an ordinary thing accounts do. It produces no signal of inauthentic behaviour, because nothing is logging in as you. Your follower count, your message history on Instagram's side and your account standing are untouched.

The risk sits entirely with password-based tools. If the tool you are leaving holds your Instagram credentials rather than a token, change your password and end all active sessions as part of the switch: deleting your account on the vendor's website leaves those credentials working. Our migration checklist covers the account-hygiene steps in order.

What a contact export really contains

Set expectations before you open the file, because a contact export is thinner than most people picture.

Where export is turned on for your workspace, HyperDM's export gives one row per contact: id, name, channel, handle or number, how they were added, whether the platform verified them, when they were added and last wrote, their permission on each messaging channel, whether their automations are paused, their tags, and a column for each custom field. It never holds a message body, and an Instagram or Facebook id shows only its last four characters. That shape is typical. If you were expecting a searchable archive of past DMs, no mainstream tool exports one, and a ManyChat migration will not produce one either. What you are moving is relationship metadata: who these people are, what they asked for, and which tags describe them. It moves as a spreadsheet, but for anyone who has not messaged the new account yet, imported tags sit on an Unverified record, separate from the contact their first DM creates, so plan to merge them before relying on them in messages.

A clean way to switch DM automation tools

The decision to switch DM automation tools is usually made on price or reliability, then delayed for months by a fear of losing something. The honest list of what you can lose is short: your flows, which you rebuild in an afternoon, and any conversation window that happens to be open on the day you cut over, which closes on its own anyway. Everything that represents real accumulated value, your contacts, your tags, your fields and your consent records, moves as a spreadsheet. Export before you cancel, rebuild your best three automations first, overlap on separate posts for a week, then disconnect. If you are weighing the move on cost rather than features, compare your current bill against the conversation allowances on HyperDM's pricing page before you start the clerical work.

Frequently asked questions

No. Flow formats are proprietary to each builder and nobody publishes an importer for a competitor's export. Plan to rebuild by hand, and treat it as a chance to delete the automations you stopped using. Most accounts have three to eight live flows, so the rebuild is usually an afternoon rather than a project.
Not if you export before your billing lapses. Contacts, tags and custom fields move as a CSV. What does not move is permission to message anyone on Instagram: an imported username that has never messaged you is stored as an unverified record, and you can only message them once they write to you.
For a few days, yes, provided they are on different posts. Both can be connected to the same Instagram account, but Meta allows only one private reply per comment, so two tools aimed at the same post will collide and one will fail. Split by post, compare delivery, then disconnect the loser.
Disconnecting the channel stops message flow but is not the same as deleting the account. Export first, disconnect second, cancel third. If you want your data removed from the old vendor, request deletion explicitly after you have the export file safely saved somewhere other than that vendor's platform.
Budget one working day for a creator account with a handful of flows, and three to five days for an agency account with client workspaces and sequences. The export and import take under an hour; rebuilding automations and the overlap period are what consume the rest of the time.
HyperDM

Run the automations. Add AI when you’re ready.

Comment-to-DM, keyword replies and follow gates — set them up, test them, then add optional AI answers from your real catalog. Free on one DM channel, 50 conversations a month, no card.