CJA data view missing during Adobe Analytics component migration

A team migrating Adobe Analytics reports to Customer Journey Analytics finds that a data view it used days earlier no longer appears in the component migration selector. That is the symptom reported in Experience League. The missing option blocks the project mapping, but the question does not establish whether the view was deleted, access changed, or the migration interface is stale.

Establish which object disappeared

Have a CJA administrator locate the data view by its exact name and connection, and record its identifier, sandbox, organization, and current status. Check whether a second administrator sees it in the migration picker. Separate “the data view exists in CJA” from “this migration operator can select it.” The distinction prevents a team from creating a duplicate view or remapping a report suite merely to get past a selector.

Check migration and viewing rights together

Adobe’s component migration guide says the dialog maps dimensions and metrics to a selected CJA data view. Its access-control guidance describes product-profile access to individual data views, including the auto-include setting. Compare the operator’s and intended project owner’s profiles; a successful migration is of little use if the eventual owner cannot open its components. Capture permissions before changing them so access can be restored deliberately.

Reproduce one project before a bulk move

Use a small, noncritical project and the same report suite, owner, and data-view selection. Record the dropdown result and timestamp, then retry after confirmed permission changes or with an authorized admin. If the view exists and the access path is valid yet the picker still omits it, provide Adobe Support the organization, data-view ID, affected user, and reproduction. Do not silently substitute a similarly named view: differing data-view settings can change the numbers a migrated report shows.

Adovo’s view

A migration is a transfer of meaning, not a sequence of successful clicks. When the target view disappears, stop and identify the exact data object and who can use it. A report that opens against the wrong view is a more dangerous outcome than a migration that pauses visibly.