Move a retention platform one journey at a time. Inventory the customer events, consent records, exclusions, templates and reports each journey depends on. Test the destination with sample contacts before switching live campaign traffic, keep one sending owner per audience, and agree who can pause or roll back each launch.

Last reviewed: September 30, 2026.

For Indian marketing teams with 10K+ contacts, replacing a tool is only part of the job. A renewal reminder can look correct in preview and still reach a customer who already renewed. This checklist focuses on the records, tests and owners that prevent that mistake.

1. Decide what must move

Start with the journeys you actually run, not every feature in the old account. Record each trigger, audience, message, goal, business owner and technical dependency. Include quiet service reminders as well as visible marketing campaigns.

• Keep: journeys with a clear purpose and reliable source data.
• Repair: useful journeys with duplicate sends, weak exclusions or missing events.
• Retire: unused workflows, obsolete offers and messages without a responsible owner.

For category selection, use customer retention automation platforms. For channel roles, use Email + WhatsApp automation. Email can explain a renewal; WhatsApp can provide a timely prompt when the customer is eligible. Neither channel needs to fire just because the other did.

2. Map identity and events

For each active trigger, record the source system, customer identifier, timestamp, required fields and acceptable delay. Agree how phone numbers and email addresses join to the same person. Keep a source-to-destination field map so an import does not silently change the meaning of a value.

Test a new event, a late event, a repeated event and an event with a missing identifier. Decide whether to reject, retry or investigate each case. Prioritize the events your first journey needs; importing every historical event is not a substitute for a working trigger.

3. Preserve consent and exclusions

Keep email subscription status separate from WhatsApp permission. Export the source, date, scope and withdrawal state of each permission where available. Preserve unsubscribe, bounce and complaint exclusions separately from temporary holds such as an unresolved support case.

Do not mark an imported number as opted in merely because it exists in a CRM. Review Meta opt-in guidance and your applicable legal requirements. Use the WhatsApp opt-in management guide to organize the operating checks.

Run negative tests before launch: an opted-out contact stays excluded, a renewed customer leaves the reminder audience, and an unresolved permission record is held for review. Confirm how a new opt-out reaches both systems during the transition.

4. Confirm account and message portability

Treat the WhatsApp number, business account access, contacts, conversation history, templates and automations as separate workstreams. Ask both providers which items transfer, which need rebuilding, who initiates the change and what service interruption is possible. Obtain a sample export before agreeing a cutover.

Review the WhatsApp Business Platform documentation and message template guidelines for the current account and template requirements. Do not assume a template accepted in the old setup is ready in the new one.

For email, assign ownership of sender-domain verification, authentication records, unsubscribe handling and bounce processing. Test delivery with a limited audience. Infrastructure or partner status alone does not guarantee inbox placement.

5. Rebuild and test one journey

Choose a workflow whose entry and exit conditions you can observe. A renewal reminder is suitable only if renewal events arrive reliably. Build the destination workflow, inspect a sample audience and explain differences from the old count before sending.

• Trigger: the intended event enters the right customer once.
• Eligibility: permission, exclusions and recent activity are checked before each send.
• Exit: a purchase, renewal or opt-out stops the appropriate follow-up.
• Handoff: replies and support exceptions reach a named person.
• Failure: missing events, rejected messages and connector errors become visible.

Keep shadow validation separate from live sending. Compare audience selection without letting both platforms message the same people. If a controlled live test is necessary, use explicitly separated audiences and document which system owns each group.

6. Preserve reporting, then cut over

Save the old reporting baseline before retiring the account. Record campaign identifiers, attribution windows, time zones and definitions of sends, clicks and conversions. Use consistent UTM parameters and a migration annotation in analytics. The campaign tracking software guide covers the reporting operating model.

Name a launch approver and a monitoring owner. Record when sending ownership changes, how the old workflow is paused and where failures are reviewed. Set rollback conditions before launch, such as missing critical events or an unexplained audience mismatch. These are team-defined acceptance criteria, not universal numeric thresholds.

A rollback needs more than an old login. Preserve the data required to resume safely, reconcile messages already sent and prevent duplicate follow-ups. After the agreed monitoring window, remove obsolete access and retire the old journey only when its owner signs off.

Choose the platform for the operating job

CampaignHQ is a Meta Tech Partner offering customer retention automation for email and WhatsApp, built on AWS. Its product overview describes shared customer profiles, segments, event-triggered workflows and campaign reporting. Demonstrate your actual consent, suppression and connector requirements before committing; a product description does not prove that every legacy workflow transfers natively.

Compare MoEngage alternative evaluation, Interakt alternatives, WATI alternatives and AiSensy alternatives when they match your starting platform. Keep this checklist as the migration acceptance record, rather than choosing a tool from a feature count.

If WATI is on your shortlist, use the WATI plans, add-ons and message-usage guide to check the recurring commitment separately from the migration work. Confirm the users, automation allowance and integrations your first journey needs before choosing a plan.

Moving from Amazon Pinpoint?

Match the replacement to the workload before applying the journey checklist. Use the Pinpoint end-of-support guide to identify the retirement scope, compare Pinpoint replacements by workload, and use the Pinpoint-to-SES migration guide for email export and cutover checks. An email delivery service does not by itself replace campaign and journey operations.

Frequently asked questions

Who should approve the migration?

Name one business approver for audience and message purpose, and one technical owner for events and integration recovery. Document who can pause sending outside normal working hours.

Should we move email or WhatsApp first?

Move by journey. A workflow may use one or both channels, but its entry, eligibility and exit rules need to work together before it goes live.

Can conversation history move with a contact CSV?

Do not assume so. Ask for separate export and import specifications for contacts, messages and attachments, and test retrieval in the destination.

What if consent records are incomplete?

Quarantine uncertain records from the affected promotional journey. Have the responsible team review evidence and the lawful contact path rather than recreating permission from an old send list.

When can we close the old account?

After journey owners accept the new workflows, required records are retained, reporting is reconciled and rollback dependencies are retired. Check contractual retention and export deadlines before cancellation.

Further reading: WhatsApp Business Platform docs, Meta WhatsApp opt-in guidance, Meta template guidelines. For a general definition, see customer retention and the customer retention overview.

Written by CampaignHQ Team