PushOwl, as part of Brevo, provides a seamless migration experience from Klaviyo to Brevo.
Overview of Migration Services
PushOwl/Brevo makes it straightforward to transfer your profiles from Klaviyo to Brevo. Data migration includes automatic sync of your Klaviyo lists and segments into PushOwl & Brevo with all the customer profiles created in Brevo as contacts. The subscription status is maintained as per what we fetch from Shopify, however.
The PushOwl x Klaviyo integration allows you to sync customer data and automate personalized email/SMS marketing campaigns. Engage effectively with your customer base using Klaviyo's robust email and SMS marketing features directly integrated with your e-commerce operations.
Steps for Migrating Profiles
Follow these steps to ensure a smooth migration from Klaviyo to Brevo:
Synchronize Klaviyo with Shopify: Ensure that your Klaviyo account is synced with Shopify. This ensures that customer tags and subscription statuses are accurate and up-to-date.
Log in to PushOwl Dashboard- Access your PushOwl dashboard and log in with your credentials.
Navigate to Integration Settings In your PushOwl dashboard, click on Settings. Under Settings, select Integrations.
Activate Klaviyo Integration Find the "Klaviyo" tile in the integrations section. You will be prompted to enter an API token generated from the Klaviyo account.
Generate Klaviyo API Token: Steps to Create a New API Key in Klaviyo. Log in to your Klaviyo account. Go to Integrations → Developer → Manage API Keys. Click Create Private API Key and provide a meaningful name to easily identify its purpose.
Set the following required API permissions for smooth integration:
Read Profiles
Read Lists
Read Subscriptions
Read Segments
Read Accounts
Click Activate to finalize the API key setup.
Copy the generated API token and paste it into the PushOwl integration setup panel.
Important Considerations
Data Discrepancies
Please note that Klaviyo to Brevo syncs might show data discrepancies due to:
Invalid contacts (e.g., malformed emails, invalid SMS numbers).
Duplicate contacts
Default Field Mapping
The integration uses default mapping for syncing standard contact fields. Custom field mapping or advanced configurations are not supported directly in the UI.
Attribute Explanation:
Brevo Attribute Description
FIRSTNAME is Customer first name
LASTNAME is Customer last name
SMS Customer is phone number
CUSTOMER_ID is External customer ID
LOCALE is Customer locale
COUNTRY is Customer country
CITY is Customer city
ZIP is Customer zip code