Skip to main content
Contributor I
May 14, 2024 8:34 AM UTC
Solved

Existing data in v1/v2 migration?

Hello,

We have a custom Klaviyo integration for our ecommerce infrastructure, which has been using the v1/v2 APIs for a couple of years.

I have fully understood and tested the differences between event structure in the v1/v2 APIs and the new APIs and how to migrate event generating code from the old format to the new format.

However, what I can’t quite establish is, what happens to all the existing events data (and profiles) - do we need to re-upload all historical data in the new format?

I.e. Are historical events already uploaded via v1/v2 100% compatible with equivalent events uploaded with the new APIs?

Are we required to delete all existing metrics and re-upload using the new APIs?

Thanks in advance!

Mat.

 

 

 

 

    This topic has been closed for replies.
    saulblumAnswer
    Klaviyo Employee
    May 14, 2024 2:33 PM UTC

    Correct, only the API call to create the events is different; any existing events will stay in the profiles, regardless of how they were created (old API, integration, CSV upload, etc.).

    4 replies

    Klaviyo Employee
    May 14, 2024 1:39 PM UTC

    Hi! Updating to the latest APIs won’t have any effect on existing profiles and events. In fact, the only way to remove an event from a profile is to delete the entire metric from the account.

    matcwhiteAuthor
    Contributor I
    May 14, 2024 2:31 PM UTC

    So we don’t need to remove and re-upload all our events in the new format?

    saulblumAnswer
    Klaviyo Employee
    May 14, 2024 2:33 PM UTC

    Correct, only the API call to create the events is different; any existing events will stay in the profiles, regardless of how they were created (old API, integration, CSV upload, etc.).

    matcwhiteAuthor
    Contributor I
    May 14, 2024 2:41 PM UTC

    Great, thanks!