User Data Migration

Let’s run through all the considerations you’ll need to keep in mind when you’re migrating your user data to Braze.

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 which 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 below and can have a maximum of fifteen (15) digits. e164

Adding Aliases to the User Profiles

Aliases are neccessary in order to be able to capture any Custom Events or custom keyword responses. You will want to set the “alias label” to “phone” and the “alias name” to the user’s phone number.

Update Historical Information on Users Subscription States

If you have any historical information about your user’s subscription states for your various messaging channels, please 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:

  1. Import users’ phone numbers in the correct format (E.164) (this requires a ‘+’ and a country code, e.g. +12408884782) For more information on users phone numbers, check out our documentation.
    • Use the users/track REST API endpoint to assign the phone value.

  2. Add a user alias to identified user profiles with a user’s phone number. The required format for this is alias_label: ‘phone’ and alias_name: ‘+12408884782’
    • Use the users/alias/new REST API endpoint to assign an alias to existing user profiles .
    • There are also SDK methods for Aliasing Users iOS / Android / Web.

  3. Assign your user’s SMS subscription state (e.g. subscribed or unsubscribed) if you already 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.
New Stuff!