How to migrate from Wati to Waxiomatic in an afternoon

Switching BSPs feels scary. Your contact list, your custom attributes, your template approvals, your team's muscle memory — all of it lives on the current platform. The honest truth: most migrations are simpler than the dread suggests, and Waxiomatic ships an importer that does the heavy lifting. Here's the playbook we use with pilot customers, refined over a handful of real moves.

Step 1: Stay on Wati for now. Don't disconnect your WABA from Wati while you evaluate. WhatsApp lets a WABA be controlled by exactly one BSP at a time, so the actual switch is a one-time event you'll do at the end. Until then, Wati keeps sending and receiving as usual.

Step 2: Export your Wati contacts. In Wati, go to Contacts → Export. You'll get a CSV with columns like Phone, Name, Email, Tags, plus any custom parameters you've defined. Save this file.

Step 3: Sign up for Waxiomatic's Free Forever tier. No credit card. Go to waxiomatic.com/signup, create an account, finish Embedded Signup against a *test* phone number you control (an SMS-receiving SIM you have lying around works) — this is just to validate the platform. Your production WABA stays untouched on Wati.

Step 4: Run the migration importer. Visit /dashboard/contacts/migrate, pick the Wati tab, and drop your CSV. The importer maps Wati's column names onto our schema, dedupes within the batch and against any contacts already in your Waxiomatic org, preserves tags + custom attributes as Waxiomatic contact attributes, and writes an immutable consent audit row for every imported contact with source: migration_import so DPDP / GDPR reviewers can trace the provenance back to Wati. The dry-run preview tells you how many rows will be created vs. updated before you commit. For our 12,000-contact pilot, the import took ~90 seconds end-to-end.

Step 5: Re-create your templates. Browse our Notification Library (a growing catalog of pre-built templates organized by industry × language) and clone the ones that match. For custom templates, the AI Spam-Check will catch the most common Meta rejection reasons before you submit. Approved templates from Wati don't transfer — Meta scopes template approvals to a BSP — but the Notification Library tends to be a cleaner starting point than dragging old templates over.

Step 6: Move your WABA. This is the irreversible step. When you're ready to switch, you'll go through Meta Business Manager and complete Embedded Signup against Waxiomatic using your production phone number. Wati's tenancy on that number ends, Waxiomatic's begins. We recommend doing this during your lowest-traffic hour so the transition is invisible to your customers.

A few things to watch for. Wati's "broadcasts" become Waxiomatic's broadcasts (same shape, same template-based flow). Wati's "bot replies" map to Waxiomatic flows — you'll need to recreate any complex logic in our visual flow builder, but for keyword → reply trees the migration is mechanical. Tags carry over directly. Conversation history does not carry over — Meta keeps message history with each BSP separately and we can't export it across the boundary.

We've done this migration for D2C apparel brands, fintech companies, healthcare clinics, and three real-estate developers. None of them have regretted the switch, but the smoothest moves are the ones where you sit on the Free Forever tier for a week first to validate the UX before flipping the switch.

If you want a hand, reply to the welcome email after you sign up and we'll do the import + WABA transition on a 30-minute Zoom — at no charge, for any team migrating from Wati, AiSensy, Interakt, or Gallabox.