Step 1 of 6 — Digital Presence
Executive Overview
Answer at a business level — no technical knowledge required. Your answers generate a complexity score and migration estimates.
6
steps
~5
minutes
zero
tech knowledge needed
Number of Digital Properties
How many websites or apps does your company run?
Count every customer-facing digital property — websites, mobile apps, regional sites, and portals. A rough count is fine.
1 — just our main website
A single web presence, no mobile apps
2–3 properties
Main site plus one or two others (e.g., a mobile app, microsite, or regional site)
4–6 properties
Multiple web and/or mobile surfaces — likely includes both iOS and Android apps
7 or more properties
Large portfolio — multiple brands, regional sites, or an extensive app ecosystem
Single-Page Application (SPA)
Do any of your sites update content dynamically without reloading the page?
If clicking around your site feels like using an app rather than a traditional website — where content changes without a full page refresh — answer yes. Think Netflix-style browsing.
No — traditional websites only
Yes — at least one property works this way
Not sure
Step 2 of 6 — Data Complexity
Analytics Setup
These questions gauge how deeply Adobe Analytics is wired into your business. The more customized the setup, the more careful the migration needs to be.
Analytics Setup Complexity
How would you describe your Adobe Analytics setup?
Basic — mostly out-of-the-box
Standard page views, basic click tracking, not much custom configuration
Moderate — we've done meaningful customization
Custom events, some e-commerce tracking, analytics team has built beyond the defaults
Advanced — heavily customized
Dozens of custom variables, complex business logic baked in, product-level tracking
I don't know — our analytics team manages this
We'll treat this as potentially advanced for estimation purposes
E-Commerce Tracking Depth
Do you sell products online and track revenue, cart abandonment, or individual product performance?
No — we don't track e-commerce
Yes — basic order and revenue tracking
Yes — detailed product-level analytics (SKU, category, merchandising)
Individual product attributes and category performance tracked per item
Report Suites
How many separate Adobe Analytics report suites does your organization maintain?
A report suite is a separate "bucket" of analytics data. Many companies have one per brand, region, or major product line.
1–2 report suites
3–5 report suites
6 or more report suites
Not sure
Step 3 of 6 — Integrations
Integrations & Dependencies
Analytics rarely lives in isolation. Other tools depend on it, and those dependencies must be carefully managed during migration.
Other Adobe Tools in Use
Which other Adobe tools does your company use? (Select all that apply)
Adobe Target
Personalization and A/B testing
Adobe Audience Manager
Audience segmentation and data management
Adobe Real-Time CDP
Real-time customer data platform
Adobe Campaign / Journey Optimizer
Email, SMS, or cross-channel campaign orchestration
None of the above / not sure
BI Tool Dependency
Does your team use BI tools (like Tableau, Power BI, or Looker) that pull data from Adobe Analytics?
No — we analyze data directly in Adobe Analytics
Yes — we have BI dashboards fed by Adobe Analytics data
Not sure
Downstream Data Pipelines
Does Adobe Analytics feed any automated data pipelines — for example, a data warehouse, data lake, or machine learning systems?
No — Analytics is self-contained
Yes — we have downstream data pipelines that depend on Analytics exports
Not sure
Step 4 of 6 — Reporting
Reporting Footprint
Reports and dashboards in Adobe Analytics don't migrate automatically — they must be rebuilt. The more you have, the more work is involved.
Active Report Volume
Roughly how many active Analytics reports or dashboards does your team rely on regularly?
Fewer than 10
A small set of essential reports the team checks regularly
10–25 reports
A moderate library across a few teams
26–50 reports
Substantial reporting infrastructure across multiple teams or business units
More than 50 reports
Enterprise-scale reporting with many stakeholders
Mission-Critical Reports
Are there specific reports that would cause a significant business problem if unavailable for even a few days?
No — we could manage a short disruption
Yes — we have 1–3 mission-critical reports
e.g., executive dashboard, weekly performance summary
Yes — many reports are business-critical
Finance, product, and marketing all depend on Analytics for decisions
Scheduled Report Deliveries
Do any scheduled Analytics reports go directly to executives or external stakeholders?
No scheduled deliveries
A few (fewer than 10)
Many (10 or more)
Step 5 of 6 — Team & Readiness
Team & Readiness
The biggest schedule risk in any migration isn't technical — it's whether internal teams have time to do their part.
Internal Development Team
Does your company have internal web developers who own your website code?
Some technical website changes must be made by your own engineers — they cannot be delegated to an implementation partner.
Yes — we have an in-house development team
We use an agency or outsourced development team
This adds coordination overhead and can extend timelines
Our development resources are very limited or tied up in other projects
Analytics Team
Does your company have a dedicated analytics team that manages Adobe Analytics day-to-day?
Yes — we have dedicated analytics staff
Analytics is managed by a small team wearing multiple hats
No dedicated analytics team — managed ad hoc
AEP Licensing Status
Has your company purchased (or begun purchasing) Adobe Experience Platform (AEP) licensing?
Customer Journey Analytics requires Adobe Experience Platform. Without it, migration cannot proceed past planning. This is the single most common project blocker.
Yes — AEP is already licensed and active
In progress — procurement is underway
Not yet — we haven't started licensing discussions
Step 6 of 6 — Timeline & Urgency
Timeline & Business Drivers
Understanding business drivers helps frame the right approach and flag anything that could affect the target timeline.
Migration Driver
What is driving your interest in migrating to CJA?
Adobe contract renewal is coming up
We need to make a licensing decision soon
Adobe has communicated that AA will be sunset or deprioritized
We want the cross-channel and identity capabilities CJA offers
Executive directive — we've been told to modernize our data stack
Target Completion Timeline
When would you ideally like to be fully operating on CJA — old system decommissioned?
Within 6 months
Aggressive — feasible only for lower-complexity implementations with available resources
6–12 months
Reasonable target for most implementations
12–18 months
Comfortable timeline for complex or enterprise implementations
No firm deadline
Prior Migration Experience
Has your organization run a major analytics platform migration before?
Yes — we've done this before and have a playbook
Somewhat — we've done tech migrations, not specifically analytics
No — this would be our first major analytics migration
Notes Optional
Additional context, pain points, or known complexity drivers: