DocumentationCX Enterprise Coworker

Migrate Adobe Analytics projects to Customer Journey Analytics with Coworker

Last update: October 28, 2026

CREATED FOR:

  • Intermediate
  • Admin

Use Adobe CX Enterprise Coworker to migrate Adobe Analytics projects and their associated components to Customer Journey Analytics within a single conversation.

Coworker validates that the dimensions and metrics in your project are mapped to your Customer Journey Analytics data view, helps you map any that aren’t, then re-creates the project in Customer Journey Analytics.

AVAILABILITY
The functionality described in this article is in the Limited Testing phase of release and might not be available yet in your environment. This note will be removed when the functionality is generally available.
IMPORTANT
Before you migrate any projects, read Prepare to migrate components and projects from Adobe Analytics to Customer Journey Analytics in the Adobe Analytics documentation. It explains how to prepare for a migration, what’s included, which elements cause errors, and how mappings affect your entire organization. This information applies to migrations in Coworker.

Differences from migrating in the Adobe Analytics user interface

Migrating projects with Coworker differs from migrating them in the Adobe Analytics user interface in the following ways:

Coworker
Adobe Analytics user interface
Who can migrate projects
Adobe Analytics administrators, and users with the Component Migration permission
Adobe Analytics administrators only
Project owner
The user who is performing the migration
The user that you specify in the Project owner field
Mapping dimensions and metrics
Coworker validates the project and lists how each dimension and metric is mapped. For any that can’t be automatically mapped, Coworker suggests a dimension or metric in your data view and updates the mapping.
In the Map schema section, you select each dimension or metric with a Not mapped status and manually map it.
How you migrate
Describe what you want in a prompt. Coworker does the work, asking a few questions along the way. For example, Coworker can create a project with the components you name, then migrate it. See Start from specific components.
Create a project in Analysis Workspace, add the components that you want to migrate, and save the project. Then, in Component migration, select the project, specify a project owner, map the schema for each report suite, and select Migrate.

Prerequisites

To migrate projects with Coworker, you need:

  • Access to the Adobe Analytics MCP. The component migration tools are enabled automatically for customers who have Adobe Analytics MCP access. To confirm that aa-mcp is connected, see Get started analyzing data with Coworker Chat.

  • Adobe Analytics administrator rights, or the Component Migration permission in the Admin Console. You don’t need to be an administrator.

  • The prerequisites for component migration in the Adobe Analytics documentation.

  • A project that uses base report suites. Virtual report suites can’t be migrated.

Review report suite mappings before you migrate

Consider reviewing how a report suite’s dimensions and metrics are mapped before your first migration from that report suite. Mappings apply to every project that your organization migrates, so settling them first helps later projects pass validation. For guidance on choosing mappings, see Decide as an organization how you will map components in the Adobe Analytics documentation.

To review mappings, select Review mappings only on the Scope tab, or ask Coworker directly:

Prompts

  • “Show me how the dimensions and metrics in my report suite are mapped to my data view”
  • “Which dimensions and metrics in my report suite aren’t mapped to my data view?”

You can also ask Coworker to update mappings.

If you skip this review, Coworker still checks the mappings for each project that you migrate.

Start a migration

Coworker always migrates a project and its associated components. To migrate specific components, ask Coworker to add them to a new project, then migrate that project.

Components that already exist in Customer Journey Analytics aren’t re-created, so you can use both methods. For example, migrate your most important projects first, then migrate any remaining components. Choose where to start based on what you want in Customer Journey Analytics:

  • Migrate a project when you want to keep the project’s panels and visualizations in Customer Journey Analytics. See Start from a project.
  • Migrate specific components when you want components such as segments, calculated metrics, or date ranges in Customer Journey Analytics, but don’t need any of the projects that use them. For example, you might plan to build new projects in Customer Journey Analytics that include them. See Start from specific components.

Start from a project

To migrate a project and its associated components:

  1. Sign in to Coworker.

  2. Select New chat.

  3. In the text field, prompt Coworker to migrate your project. For example:

    Prompt

    I want to migrate components from Adobe Analytics to Customer Journey Analytics.

    Coworker describes what it can migrate and starts a questionnaire.

  4. On the Scope tab, select one of the following options, then select Next:

    table 0-row-2 1-row-2 2-row-2 3-row-2
    Option Description
    A specific AA project Migrate a project that you name. Follow the remaining steps in this section.
    Review mappings only Check how a report suite’s metrics and dimensions map to a data view, without migrating anything. See Review report suite mappings before you migrate.
    Plan a full upgrade Get an end-to-end plan for moving from Adobe Analytics to Customer Journey Analytics. See Plan your implementation with Coworker.

  5. (Optional) Answer the questions on the Source & target tab, then select Next.

  6. On the Review tab, confirm your answers, then select Submit.

    Coworker checks which Adobe Analytics companies you have access to and how many base report suites each one has, then starts a second questionnaire.

  7. Answer the following questions, selecting Next after each one:

    table 0-row-3 1-row-3 2-row-3 3-row-3
    Tab Question Additional context
    Project What is the name of the AA project you want to migrate? A partial name is fine.
    Report suite Which report suite does the project use? Select a report suite from the list, or type the name of another one.
    Data view Which CJA data view should it migrate to? (Optional) Type the name of a data view, or leave it blank and Coworker suggests matching data views.

  8. On the Review tab, confirm your answers, then select Submit.

    To skip the questionnaire at any step, select Skip questionnaire and describe what you want in the chat instead.

  9. Continue with Review the validation results and mappings.

Start from specific components

To migrate specific components:

  1. Ask Coworker to create a project with those components and then migrate it. For example:

    Prompt

    I want to migrate all of my Analytics segments with “Spring sale” in the name to CJA. Create a new Workspace project with all of these segments added, then migrate that project to CJA.

    Coworker creates the project in Adobe Analytics.

  2. Continue with the following section, Review the validation results and mappings.

Review the validation results and mappings

Coworker validates the project against the data view you selected, then reports whether the project can be migrated. The results list each dimension and metric in the project and the Customer Journey Analytics dimension or metric that it’s mapped to. For example:

  • Metric: Occurrences becomes Events
  • Dimension: Hour stays Hour

For the components and project elements that are migrated, see Understand what is included in a migration in the Adobe Analytics documentation.

If validation doesn’t pass:

  • Dimensions or metrics that can’t be automatically mapped: Coworker suggests a dimension or metric in your data view to map each one to, updates the mapping, then validates the project again. You can also tell Coworker which dimension or metric to map it to, for example, “Map Page Views to web.webPageDetails.pageViews.value.”

  • Unsupported elements: Remove any unsupported elements from the project in Adobe Analytics. For example, make sure every panel uses a base report suite rather than a virtual report suite. Then ask Coworker to check the project again. For the list of unsupported elements, see Understand unsupported elements that cause errors in the Adobe Analytics documentation.

To check mappings for a whole report suite before you migrate, see Review report suite mappings before you migrate.

Migrate the project

  1. When validation passes, Coworker asks whether to create the Customer Journey Analytics version of your project on the data view you selected. Select Yes, migrate, then select Submit.

    To stop without migrating, select No, stop here.

    Coworker re-creates the project in Customer Journey Analytics, with you as the project owner. Your original Adobe Analytics project doesn’t change.

  2. Continue with the following section, Check the migration status.

Check the migration status

Migrations run in the background, so the new project might not be ready right away.

  1. Prompt Coworker to check the status of the migration:

    Prompt

    Check status

    Coworker reports one of the following statuses:

    table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2
    Status What it means
    Queued The migration is waiting to start.
    Started The migration is in progress.
    Completed The migration finished. Coworker provides a summary of what was migrated, including the project name and data view.
    Failed The migration failed. You can retry the migration. See Retry a failed migration in the Adobe Analytics documentation.

  2. When the migration is complete, open the new project from your project list in Customer Journey Analytics Workspace.

  3. (Optional) Transfer ownership of the project to any user in Customer Journey Analytics. For more information, see Transfer assets.

After a migration completes, Coworker can suggest another project to migrate next.

Tips for better results

Next steps

recommendation-more-help
coworker-help