Adobe Experience Cloud
AJO onboarding can convert assets, but migration still needs acceptance tests
Evaluate AJO guided onboarding with a representative migration slice and explicit review gates.
November 10, 2026
A platform switch often stalls between an attractive demo and a defensible migration estimate. Adobe's AJO onboarding announcement describes template conversion, content-block detection and journey previews. It also says onboarding is in Limited Availability and that later capabilities are directional.
Test a slice that contains the hard parts
Select one live journey with conditions, consent rules, reusable content, language variants and a measurable outcome. Include the data structures and channel configuration it depends on. Ask Adobe which source systems and conversion paths are available in your tenant; the announcement names Eloqua and Salesforce Marketing Cloud API connections plus file and screenshot upload.
Compare the original journey with the converted canvas step by step. Check entry logic, wait behavior, suppression, personalization tokens, fragments and fallback content. A template that looks right in preview can still target the wrong profile attribute.
Put human approval at the handoff
Assign an owner for source inventory, data mapping, content, compliance and production release. Record conversion exceptions and decide whether each asset should move, be redesigned or be retired. Adobe's journey guidance recommends planning, validation, monitoring and optimization as separate stages; an import does not complete those stages.
Estimate effort from the tested slice and exception rate, not from a vendor automation percentage. Rehearse rollback and compare actual outcomes after cutover.
Adovo’s view
Migration speed matters only when meaning survives. The valuable unit is a customer decision, not an imported template. Let automation remove mechanical work, then spend human attention on logic, consent and proof that the journey still serves its purpose.
