Migration from Sendbot Classic to the new Sendbot is a copy-and-verification process, not an instant switch of live traffic. Your Classic workspace and existing conversations remain active while the copy is prepared. Automatic migration depends on availability and eligibility shown for your workspace.

​
How it works

  1. Sign in to Sendbot Classic as an administrator of the source workspace. Start the migration from Classic if the option is enabled for that workspace.
  2. Sign in to the new Sendbot Studio with the same login provider or a verified email that matches your Classic identity. Workspace ownership must be confirmed.
  3. Visit the migration page to accept or review the invitation and to see existing operations. If no transfer is listed, start it from the Classic workspace.
  4. Review the limitations, authorize copying, and select Migrate now only if available. If automatic migration is unavailable, no new copy has started.
  5. Follow the stages: compatibility checks, copying, and verification. Review warnings or pending actions before attempting any retry.
  6. Once the copy is verified, open the new workspace, review imported draft bots, reconnect integrations, test flows and publish only after validation.

​
What needs attention after copying?

The migration is designed to copy workspace structure, members, folders, bots and supported historical data, as confirmed by each operation. Scope varies with compatibility and the operation’s verified inventory.
  • Bots: imported as drafts, not automatically published.
  • Integrations and channels: credentials and live connections need reconnection or review.
  • Custom domains, URLs and live traffic: remain on Classic until separately switched.
  • Schedules and webhooks: require review before reactivation.
  • Members: may need to accept invitations using verified identities.
  • Subscriptions, plans, billing and credits: are not automatically transferred by the data copy. An additional CORE Base access process exists for eligible contracts after a verified copy; see below.
  • Old live chat sessions: are not resumed in the new Studio.

​
CORE Base access while retaining your Classic billing contract

The new Sendbot includes a separate entitlement process for CORE Base with 500 credits per month after a Classic workspace copy has completed and passed verification. CORE Base access requests are now enabled in production for eligible workspaces after a verified copy and Classic contract check. Copying a workspace does not automatically grant CORE Base; an administrator must request and explicitly authorize the entitlement. After a verified workspace copy, the administrator can check the Classic contract in Studio and explicitly consent to the new entitlement. This is separate from data-copy consent. Automated eligibility in this rollout is limited to supported Classic Starter contracts, verified billing evidence, ownership and an eligible destination workspace. Classic Core, custom, higher-tier and ambiguous contracts require individual review.
  • Once approved and applied, the new workspace receives CORE Base access and 500 monthly credits. This is not an up-front lifetime allocation.
  • The verified legacy price, currency, billing interval and paid-through date are retained. Charges remain on the original Classic contract: no second subscription is created or automatically repriced.
  • An annual Classic paid term remains annual for billing, but the 500-credit allowance is granted in monthly windows, not all at once.
  • Classic chat/session allowances, add-ons, existing sessions and live traffic continue in Classic; chat sessions are not converted into new wallet credits.
  • Other plans, multiple contracts and unverified billing conditions are never silently transferred.
CORE Base entitlement is separate from bot publication and traffic cutover. Check the availability and state displayed for your own migration; do not assume that the entitlement has been applied. Do not delete the Classic workspace or turn off active bots until the new bots have been tested and traffic has been deliberately switched.

​
Troubleshooting

There is no single guaranteed completion time. For account-specific issues, contact Sendbot support with the error and operation reference. Never share passwords, tokens or login codes.