Migrating Your WhatsApp List to a New Tool Without Losing Consent

Switching campaign tools is where lists get hurt - not in the move itself, but in what gets left behind. Contacts arrive; consent records stay in the old tool. The suppression list does not travel. A week later, people who asked to stop are hearing from you again, and the blocks land on your number.

This guide is the migration that loses nothing: the three datasets that must move, a five-step sequence, and the re-permission path for lists whose records are already broken.

What a migration actually moves

Three datasets, and only the first is obvious:

1. The contacts - numbers, names, and any columns your new tool can use as variables.
2. The consent records - per contact: source, timestamp, and the wording they agreed to. This is what makes the list an asset; the consent guide defines the four facts.
3. The suppression list - everyone who opted out or was removed. These must land in the new tool’s do-not-contact list before the first send, or your first campaign re-contacts people who explicitly left.

The third one is the migration’s most common casualty, and its absence is the fastest way to turn a tool switch into a deliverability crisis.

Step 1: export everything, including the boring parts

From the old tool, export in this order:

1. Contacts with every column - not just name and phone. Source, timestamp, tags, segments.
2. The suppression / opt-out list, however the tool names it.
3. Delivery history for the recent period, if exportable - useful for comparing the new tool’s numbers against a known baseline.
4. Your message templates and campaigns, for reference; they re-type rather than import, which is fine.

If the old tool cannot export your own data freely, that is a finding about the tool, not a reason to stay - and it is exactly the question the buyer’s checklist puts first for the next vendor.

Step 2: clean and map before you import

The import is only as good as the file. Before importing into Automate:

• Normalize the phone column to digits with country codes - the parser strips spaces, dashes and leading plus signs, and repairs Excel’s scientific-notation mangling, but the country code has to be there.
• Keep the consent columns - they import as ordinary columns and stay with the contact, so the records survive inside the new tool.
• Split segments into separate files if you plan to run them as separate audience lists - one import per list keeps the structure you already built.
• Dedupe expectations: numbers already queued or sending are skipped as duplicates; numbers previously sent or failed are not - re-sending to a past audience is legitimate.

Step 3: bring the suppression list

Before any campaign, import the old tool’s suppression list into the new one’s do-not-contact list. On Automate, the suppression list is checked before every send on every connection, entries can also be added manually, and anything queued for a suppressed number is cancelled on the spot. The point of doing this first is simple: the safest moment to restore a do-not-contact guarantee is before a single message exists to violate it.

Step 4: re-link your numbers

Numbers join the new tool by QR scan - WhatsApp on the phone, Linked devices, Link a device, exactly like linking WhatsApp Web. Two facts make this step calm rather than scary:

• The number does not change. Contacts keep seeing the same sender; nothing about your presence resets.
• Warm-up does not necessarily restart. The ramp keys off when the connection was created, and established numbers can have warm-up disabled per connection - the warm-up guide covers which numbers qualify.

Send a test message to your own phone as the final check: template rendering, spintax, attachment, and the number’s health in one step.

Step 5: the parallel run

Do not cancel the old subscription yet. Run one full campaign cycle with both accounts active:

1. Send the first campaign on the new tool to a mid-warmth segment.
2. Compare its health report against the old tool’s baseline - delivery, read rates, failure breakdown.
3. Confirm opt-out handling end to end on the new tool: one test reply, one suppression, one verified exclusion.
4. Check that every segment and list actually moved - the forgotten segment is always the one nobody emailed in months.

Then cancel the old account, and the migration is finished rather than assumed.

When consent records are missing

Plenty of lists arrive at a migration with no usable records - bought once upon a time in a looser era, or exported from a tool that never tracked sources. Importing them on hope converts an old problem into a new one with your name on it.

The fix is a re-permission campaign, and it is honest work:

1. Import the questionable contacts into their own list, clearly named.
2. Send one message: plain, short, and genuinely optional - “Reply YES if you’d like to keep hearing from us on WhatsApp; otherwise we won’t message you again.”
3. Import only the yeses into the main list. The rest are done - not retargeted, not “given one more chance”.

The list shrinks, sometimes painfully. It also becomes defensible for the first time - the proving-of-consent that laws like the GDPR and India’s DPDP Act make the sender’s job - and the engagement metrics that follow - the reads and replies that drive everything in the deliverability pillar

• are why a smaller clean list beats a larger haunted one on every number that matters.

Timing the switch around your calendar

Two timing rules save headaches. First, migrate between campaigns, never mid-queue: finishing a campaign on the old tool and starting the next one on the new tool keeps every message’s outcome attributable to one system. Second, give the switch a quiet week rather than the festive ramp-up - the first send on new infrastructure should not be your highest stakes send of the year. Sync the switch with a natural gap in the calendar, send one moderate campaign to prove the pipe, then resume the normal rhythm with confidence. That is the whole migration: three datasets, five steps, and one honest cut where the records run out.