Migrating vendors

Eventvisor can help you safely migrate from one third-party analytics vendor to another incrementally.

Challenges#

Organizations often invest heavily into a chosen third-party analytics service, and it is not uncommon to see them stuck with it for years.

Either because of requirements or growing costs, management may decide to switch to a different vendor or roll out their own custom internal solution.

But when third-party SDKs are deeply integrated into your applications, it is not that easy to migrate to a different vendor. The difficulty grows even more when the application is complex and has a lot of events, and you want to migrate gradually.

This is where Eventvisor can help ease the burden of migrating to a different vendor incrementally.

Eventvisor destinations#

When using Eventvisor, we can define these destinations in a central place.

For example, we may already have the existing vendor as existingVendor destination:

description: Existing vendor
tags:
  - web
# ...

And we can introduce a new destination called newVendor that we wish to migrate to:

description: New vendor
tags:
  - web
# ...

Migration by filtering#

You can start by filtering out the events from existing vendor, and filtering in the events to the new vendor.

Filtering out#

# ...
conditions:
  - source: eventName
    operator: notIn
    value:
      - pageView
      - buttonClick

Filtering in#

# ...
conditions:
  - source: eventName
    operator: in
    value:
      - pageView
      - buttonClick

Learn more in destinations page how conditions work.

Migration by sampling#

Alternatively, sampling can be used to gradually migrate ingesting the tracked events to the new vendor.

Sampling first half#

# ...
sample:
  by: attributes.userId
  range: [0, 50] # first 50% of users

Sampling second half#

# ...
sample:
  by: attributes.userId
  range: [50, 100] # last 50% of users

Learn more in sampling page.

Choosing a migration strategy#

It is completely normal if you wish the tracked events to end up in both vendors at the same time for a while until you gain more confidence in the new vendor.

Above examples show how you can choose to migrate gradually without overlapping the tracked events in both vendors. Ultimately, you are in control to choose the strategy that works best for you.

Clean up#

Once your migration is complete, you are free to either archive or delete the existingVendor destination.

This will impact applications tracking events with Eventvisor SDKs immediately. And the application developers can take their time to remove any vendor specific modules they might be using.