Adobe Analytics to Customer Journey Analytics Migration: A Complete Guide

As customer journeys span web, mobile, in-store, and call center touchpoints, organizations need analytics that can connect these interactions into a coherent view. Adobe Analytics was built around a different measurement model centered on report suites and session-based data. Customer Journey Analytics (CJA) rebuilds this foundation by using Adobe Experience Platform to bring data from multiple channels into a connected view of the customer journey. 

For organizations already invested in Adobe marketing analytics, moving from Adobe Analytics to Customer Journey Analytics is fundamentally an architectural shift. Without careful planning, that shift can introduce significant operational risk.

Why Should Organizations Migrate to Customer Journey Analytics?

Adobe Analytics uses a fixed report suite schema that is defined when data is collected. Each eVar, prop, and event has a set role and limit. Combining data across report suites or channels can often require workarounds. These constraints become harder to manage as businesses expand their digital footprint and need a broader view of customer behavior.

Customer Journey Analytics, built on Adobe Experience Platform, supports unlimited dimensions and metrics. It can connect web, mobile, call center, and offline data using person-based identity stitching, instead of relying on session or cookie identifiers. This makes cross-channel attribution possible in ways Adobe Analytics was never designed to support.

Adobe describes CJA as a platform for understanding customer behavior “across every touchpoint.” The capability matters for teams that have outgrown report-suite limitations and need to connect online behavior with offline outcomes.

Adobe Analytics vs. Customer Journey Analytics

The two platforms share Adobe’s analytics heritage, but they are built on different foundations. The comparison below focuses on the criteria that shape a migration decision.

Neither platform is universally superior. Adobe Analytics remains a capable choice for a defined, single-channel measurement model, while Customer Journey Analytics fits organizations whose channels and identity complexity have outgrown the limitations of a single-channel structure. 

What to Assess Before Migrating from Adobe Analytics to Customer Journey Analytics 

Before any organization begins moving data or projects to Customer Journey Analytics, a structured readiness assessment matters more than starting quickly. A rushed start tends to surface problems midway through the project, when those problems are harder to fix.

Audit the Current Adobe Analytics Implementation

Start with an inventory of existing report suites, projects, segments, and calculated metrics. Adobe Analytics administrators have access to a component migration tool that lists what exists and flags elements unsupported in CJA, such as certain visualizations and panels. Removing or reworking these before migration prevents failed transfers later.

Adobe also provides Analytics Inventory to summarize projects, components, report suites, and users across the environment. Use both tools together to scope the migration accurately. Analytics Inventory shows the overall migration effort, while the Component Migration Tool identifies what needs to be reworked or replaced.

Check Your Data Collection Method

How data reaches Adobe matters as much as what data is collected. Organizations already running Adobe Tags and the Experience Platform Web SDK have a more direct path into Customer Journey Analytics. 

Those still on the older AppMeasurement library face more preparation, since the Web SDK (Software Development Kit) introduces new concepts such as XDM schemas, identities, and datasets that AppMeasurement does not support natively.

Define an Identity Strategy

Customer Journey Analytics connects data across channels through person-based identity stitching rather than session or cookie IDs.

Before migration, teams should identify the available customer identifiers across each data source and confirm whether those datasets share a common person ID or require identity stitching.

Evaluate Historical Data Needs

Decide how much historical Adobe Analytics data needs to be carried forward, and treat it as a licensing decision rather than a preference. The Analytics source connector ingests history into Adobe Experience Platform through the Analytics source connector, which backfills up to 13 months by default. Going further back requires the Extended Data Capacity add-on, and CJA data entitlement is itself limited to timestamps under 13 months unless additional capacity is licensed.

This has a direct consequence for reporting continuity: organizations that rely on multi-year year-over-year comparisons need either to license extended capacity or to plan on running Adobe Analytics in parallel as the historical system of record. Establish which of the two applies before implementation begins.

Assess Adobe Experience Platform Readiness

Since CJA runs on Adobe Experience Platform, readiness includes having schemas, datasets, connections, and data views planned out. This is where many customer journey analytics platform rollouts either gain momentum or stall, depending on how clearly the underlying data architecture has been mapped in advance.

One key constraint affects this architecture. A CJA connection can only combine datasets within the same Experience Platform sandbox. Data cannot be joined across sandboxes. Define your sandbox strategy early to ensure the required datasets can work together within CJA.

Adobe Analytics to CJA Migration Journey

A migration to Customer Journey Analytics moves through distinct phases, each with a different objective. Understanding this sequence helps set realistic timelines and avoids the common mistake of treating migration as a single technical task.

Discovery and Assessment

This phase confirms whether CJA is the right fit and establishes a clear picture of the current environment. It draws on the readiness assessment covered earlier, converting findings from the audit, data collection review, and identity mapping into a documented baseline for the project.

Solution Design

With the current state understood, the team defines the target state. This includes designing the Experience Data Model schemas, planning datasets and connections, and deciding how existing report suites and channels will map into Customer Journey Analytics data views. Governance decisions, such as who administers connections and data views, are also settled here.

Historical data scope belongs here too. Because backfill depth is contractual, it needs to be agreed with Adobe during design rather than discovered during implementation.

Implementation

This is where the designed solution gets built. Schemas, datasets, and identities are configured in Adobe Experience Platform first, creating the foundation for data to flow in through the Web SDK or the Analytics Source Connector. Connections and data views are then set up in Customer Journey Analytics. 

Expect to rebuild components rather than migrate them directly. Adobe’s documentation states that Adobe Analytics segments and calculated metrics are not compatible with CJA: the component migration tool re-creates segments against whichever dimensions and metrics you have mapped, and existing calculated metrics are not ported at all. Analysis Workspace projects also need to be rebuilt to work with CJA’s data structure and visualization options. Scope this as design work, not a data transfer.

Validation

Before anyone relies on the new environment, reporting needs to be checked against the old one. This means comparing key metrics between Adobe Analytics and Customer Journey Analytics, confirming that identity stitching is working as intended, and resolving any discrepancies before stakeholders start making decisions from the new data.

Three differences account for most of what looks like a discrepancy, and knowing them in advance shortens this phase considerably. Core terminology is remapped: so Visitors become People, Visits become Sessions, and Hits become Events. Event de-duplication works differently in CJA, which can move conversion counts unless deduplication IDs are configured in the data view. And attribution now lives in the data view, configured per component, rather than being fixed at collection. Reconcile these deliberately before treating a variance as an error.

Go-live and Adoption

The final phase shifts reporting and decision-making fully to Customer Journey Analytics. This includes training teams on the new interface, retiring redundant Adobe Analytics workflows, and monitoring the environment closely in the weeks after cutover, since real usage often surfaces edge cases that testing does not.

When approached as a sequence rather than a single event, migration becomes a manageable project rather than a disruptive one.

Common Migration Challenges (and How to Avoid Them)

Even a well-planned migration runs into friction. Knowing where it typically surfaces makes it easier to manage. 

Legacy Data Models Do Not Map Cleanly

Report suites built around eVars and props don’t always have a direct equivalent in the Experience Data Model.

Avoid it: Map dimensions and metrics early using Adobe’s component migration tools, and treat unmapped components as design decisions.

Identity Stitching Is Assumed, Not Verified

Teams often assume person-based identity resolution will work out of the box across web, mobile, and offline sources.

Avoid it: Confirm shared identifiers exist across data sources before migration, and test stitching logic against real data before go-live.

Historical Data Decisions Are Made Too Late

Deciding how much history to carry forward after implementation has already started disrupts timelines and reporting continuity.

Avoid it: Finalize historical data scope during solution design and confirm early whether the default 13-month backfill covers the reporting your stakeholders actually depend on.

AppMeasurement Dependencies Slow Things Down

Organizations still on AppMeasurement often underestimate the work needed to adopt the Web SDK.

Avoid it: Assess the current data collection method early, since this determines the realistic implementation timeline.

Validation Gets Rushed

Skipping thorough metric comparisons between Adobe Analytics and Customer Journey Analytics leads to discrepancies that surface after teams have already switched over.

Avoid it: Build in a dedicated validation phase, and don’t shift full reporting reliance to Customer Journey Analytics until key numbers reconcile.

Target and A4T Reporting Have No Direct Equivalent

Teams running Adobe Target expect their existing experimentation reporting to move across. The A4T panel is not supported in Customer Journey Analytics, and A4T data brought in through the Analytics source connector cannot be analyzed in the CJA experimentation panel.

Avoid it: Inventory Target-based reporting during discovery, and plan to send experiment and variant data into Experience Platform directly so the CJA experimentation panel can use it.

Persistence and Attribution Behave Differently

Because CJA calculates persistence and attribution at report time rather than at collection, variables with long or unlimited expiration windows do not reproduce their Adobe Analytics behavior. Data view persistence is capped at 90 days.

Avoid it: Review eVar expiration settings against that cap during solution design, and configure attribution model and lookback window per component in the data view rather than assuming defaults will match.

Governance Ownership Is Unclear

Without a defined owner for schemas, connections, and data views, Customer Journey Analytics environments drift out of alignment over time.

Avoid it: Assign clear governance roles for the Adobe Experience Platform environment before go-live. 

Conclusion

Moving from Adobe Analytics to Customer Journey Analytics means adopting an analytics foundation built around real customer behavior. CJA connects data across channels, devices, and touchpoints that may not fit within a single report suite.

Organizations that treat migration as a data architecture investment tend to get more value from CJA. The goal is  a stronger analytics foundation.

That said, migration isn’t the right decision for everyone at this stage. Some organizations still have room to grow within Adobe Analytics,  while others are already hitting the limits this blog post has described.