What is regional migration?

Sendbird currently provides global instance coverage in 7 different regions (Tokyo, Seoul, Singapore, Frankfurt, Oregon, West Virginia, Canada) where it will serve as a database for our customers.

For customers with high traffic (100,000 MAU and above), we recommend choosing the region closest to your end-users.

Regional migration happens when our customers decide to move their region to a different region that is the closest. See the guide below on setting up and migrating the instance from one region to another.

Before we begin, let’s go over the terminology that will be used in the guide.

  1. Source instance: Original region instance(i.e. Free tier - Tokyo) that the customer wants to migrate from.
  2. Target instance: New region instance that the customer wants to migrate to.

Set up before migration:

  1. Create a new app with a target region (Dashboard >Create app).
  2. Turn on the data export API on the source instance.
  3. Turn on the migration API on the target instance.

=> Contact our Sendbird support team(with Target Application ID)


Now that everything is set up, you can begin the actual migration process.

You need to create users and channels (open/group) for a new application and then migrate all the messages to the target channel on the new application from the existing channel in the old application.

  1. If you have the data export functionality, please download all the messages within the desired time range.(link). The maximum time range is 7 days per request.

(Dashboard >Chat > Data Exports) If not, you should list all the messages via Platform API(link) and store them on your end.

  1. Register the users on your current chat solution to your Sendbird application based on your exported data. You can migrate the users into the Sendbird system using the create a user API.

  2. Create either an open or a group channel to migrate the messages on your chat solution based on your exported data. The Sendbird system doesn’t automatically create a channel for your migration.

  3. The maximum number of migrated messages per call is 100. Make sure to abide by the 5 requests per second rate limit to avoid failure during your migration(link).