User data migration
This reference article covers the considerations you’ll need to keep in mind when you’re migrating your user data to Braze.
Are you currently a non-native SMS client? If so, visit the non-native SMS documentation for your corresponding user data migration article.
Format user phone numbers to carrier standards
Phone carriers have a specific type of format they expect called E.164 which is the international telephone numbering plan that ensures that each device has a globally unique number. This is what allows phone calls and text messages to be correctly routed to individual phones in different countries. E.164 numbers are formatted as shown in the following image and can have a maximum of fifteen (15) digits. Learn more about user phone numbers.
Update historical information on users subscription states
If you have any historical information about your user’s subscription states for your various messaging channels, be sure to update this information in Braze.
Example migration steps
Before you begin composing SMS campaigns through Braze, you’ll need to update your user data to ensure that all of this works.
Here’s a quick summary of the user data you’ll need to update in Braze:
- Import users’ phone numbers in the correct format (E.164) formatting requires a plus
+
and a country code, e.g.,+12408884782
. For more information on how to import user phone numbers, refer to user phone numbers.- Use the users/track REST API endpoint to assign the
phone
value.
- Use the users/track REST API endpoint to assign the
- Assign your user’s SMS subscription state (e.g., subscribed or unsubscribed) if you have this information.
- Use the subscription/status/set REST API endpoint to set users as subscribed or unsubscribed from your SMS Subscription Group(s).
- Note that once the SMS Subscription Groups have been configured in your dashboard, you’ll be able to grab the necessary
subscription_group_id
which you’ll need for your API request.