# Migration to JENTIS: A Short Guide

## Migrating to JENTIS: A Short Guide

Migrating your tracking setup to JENTIS is a strategic step toward a future-proof and privacy-compliant data infrastructure. This short guide gives you a quick overview of the essential steps to take, depending on your current setup.

### Recommended: Use the Native JENTIS Data Layer

The most robust and scalable integration path is to adopt the JENTIS Data Layer natively. This enables:

* Full support of JENTIS default tracking models
* Out-of-the-box tag templates, triggers, and variables
* Clean and consistent data models across tools

If you are building a new implementation or can influence the backend/frontend setup, **this is the way to go**.

**Learn more**: [set-up-jentis-data-layer](https://docs.jentis.com/data-capture/web-tracking-setup/set-up-jentis-data-layer "mention")

### Migration Option A: Bridge via Data Layer State

If your website already uses a structured `window.dataLayer` (e.g. GTM Enhanced Ecommerce), you can configure JENTIS to observe and react to specific events within it.

This involves:

* Creating a **JENTIS State** that listens for events (e.g. `gtm.init`)
* Mapping values from the dataLayer to **JENTIS Variables**
* Building **Triggers and Tags** based on these States and Variables

✅ Flexible but requires adjusting trigger states manually.

**Guides**: [enhanced-e-commerce-bridge-via-jentis-state](https://docs.jentis.com/data-capture/web-tracking-setup/set-up-gtm-data-layer/enhanced-e-commerce-bridge-via-jentis-state "mention")

***

### Migration Option B: Bridge via Code Snippet (Preferred for GTM Users)

When migrating from GTM Enhanced Ecommerce, JENTIS provides a code-based translation layer. This bridge reads `window.dataLayer` and converts the data into JENTIS format on the fly.

This method:

* Automatically listens for events and translates them
* Requires no manual trigger-state updates
* Supports Enhanced Ecommerce events out of the box

**Guide**:&#x20;

* [ga4-e-commerce-data-layer-bridge-ga4-to-jentis](https://docs.jentis.com/data-capture/web-tracking-setup/set-up-gtm-data-layer/ga4-e-commerce-data-layer-bridge-ga4-to-jentis "mention")
* [enhanced-e-commerce-data-layer-bridge-gtm-to-jentis](https://docs.jentis.com/data-capture/web-tracking-setup/set-up-gtm-data-layer/enhanced-e-commerce-data-layer-bridge-gtm-to-jentis "mention")

### Summary

| Migration Method        | Best For                                    | Effort | Recommendation  |
| ----------------------- | ------------------------------------------- | ------ | --------------- |
| JENTIS Data Layer       | New setups / full control                   | Medium | ⭐ Best Option   |
| Bridge via Code Snippet | Existing GTM Enhanced Ecommerce setup       | Low    | ✅ Preferred     |
| Bridge via State        | Custom GTM events with variable integration | Medium | Useful fallback |

Choose the migration method that best fits your technical constraints and long-term data governance goals.

Need help? Contact JENTIS support or your tracking implementation partner.
