AppMeasurement to Web SDK to CJA: the migration guide for data engineering teams
Moving off AppMeasurement and onto Customer Journey Analytics is not one migration. It is three, and they can be run independently:
- Collection. AppMeasurement to Web SDK. Changes how data leaves the browser. Does not require an XDM schema.
- Platform. Adobe Analytics to Customer Journey Analytics. Requires a schema, a dataset, a connection and datastream mapping.
- Reporting. Report suites to data views, and the components inside them. This is where most of the risk sits, and it is the step teams under-budget.
Teams that treat these as one project stall on the schema. Teams that sequence them ship collection first, keep reporting stable, and move platform and reporting when the data is proven.
The single most consequential design decision is this: do not rebuild eVar1 and prop1 in your schema. Adobe's own guidance is to capture durable facts in the schema and apply attribution and persistence at the data view level. A schema that mirrors your old variable map inherits every workaround you have accumulated since Omniture, permanently, because schemas are effectively immutable while data views are not.
The three migrations, and why conflating them stalls projects
The reason so many CJA migrations sit half-finished for quarters is that the team scoped one project with one cutover date, and the schema became the critical path for everything, including work that never needed a schema.
| Migration | What changes | Schema required | Can run alone |
|---|---|---|---|
| AppMeasurement to Web SDK | Library, payload shape, method calls | No | Yes |
| Adobe Analytics to CJA | Storage, identity, reporting engine | Yes | Yes, but needs Web SDK or a data connector first |
| Report suites to data views | Component definitions, attribution, persistence | No | Only after CJA exists |
Sequence them. Prove each one before starting the next.