The Migration page lets the platform owner bring accounts, plans, and data over from a supported source platform — currently BotSailor — into this platform. It covers both the admin-side bulk migration setup and the per-user self-service import that regular users can run once it’s enabled.
Save BotSailor migration credentials for the platform: API token, WhatsApp whitelabel domain, a display name for the source, and a WABA (WhatsApp Business Account) system user access token
Allow or disallow individual users from running their own one-time account migration from their own Settings page
Choose the migration scope: migrate all BotSailor users, or only users on specific BotSailor package(s)
Map each BotSailor package to a local plan, with a billing cycle (monthly, quarterly, or annual)
Map each BotSailor addon to a local addon plan (optional — unmapped addons are skipped)
Choose what gets imported during sync: labels, custom fields, contacts (user accounts, plan assignment, WhatsApp channel details, and a random reset-required password are always included)
Run the bulk sync and watch live progress, including per-user status and any errors
Cancel a sync while it’s running
Run a separate Sync Expiry job that refreshes subscription expiry dates from BotSailor for admin users whose subscription has expired (or for all users)
Open Migration from the Platform sidebar and stay on the BotSailor tab (currently the only migration source).
In the Migration Credentials card, enter the BotSailor API token, the WhatsApp whitelabel domain, a display name for this source, and the WABA access token, then click Save. Credentials must be saved before you can validate and continue.
Optionally check Do you allow user to migrate? so individual users can run their own one-time migration later from the /migration page in their own workspace.
In the Start Migration card, choose the scope: Migrate all users or Migrate users by plan. If migrating by plan, select one or more BotSailor packages once they load.
Click Validate & Continue. This validates the API token and loads BotSailor’s packages, user count, and addon count.
On the Map Packages to Plans step, choose a local plan and billing cycle for every BotSailor package shown, then click Continue.
On the Map Addon Packages step, optionally map BotSailor addons to local addon plans and a billing cycle. Unmapped addons are skipped during sync. Click Continue.
On the Sync step, choose what to import (Labels, Custom Fields, Contacts), review the package mapping summary, and click Start Sync.
Watch the progress bar and succeeded/failed counts while the sync runs. Click Cancel Sync if you need to stop it early.
Once complete, click Start New Migration to run another batch, or scroll down to Sync Expiry to refresh expiry dates for already-migrated admin users — choose Expired users only or All users, then click Sync Expiry.
