re:target
Simulated run

See a simulated assessment run.

A scripted run against our sample business unit, ending on the report a real scan produces. Modeled on a Marketing Cloud development business unit, with made-up identifiers and volumes scaled to a small-to-medium production business unit.

Inventorying the sample org…

  1. 1Business unit connectedworking…
  2. 2Folder tree walked
  3. 3Emails, templates & blocks
  4. 4Data extensions
  5. 5Journeys
  6. 6Automations & activities
  7. 7Usage & references resolved
  8. 8Rating migration complexity
  9. 9Report ready

What it connected to

Read permissions requested
Email · Documents and Images · Saved Content · Automations · Journeys · Data Extensions. Nothing with write, send or subscriber access.

Made-up values, shown read-only. In a real assessment these come from a read-only installed package in Marketing Cloud.

Migration complexityMedium

Simulated run · sample orgMID 5432112345

Readiness report — Parent BU, sample org

Medium, because only 711 of 3,413 items are used by anything running. 5 of 7 categories are high complexity, but most of what is in them can stay behind, so most of the work is deciding what not to bring. Nothing blocks the move, and 4 things need a decision before you can scope it.

Run it on my own business unit See pricing

Items inventoried3,4137 categories, 394 folders
Changed in last 90 days46314% of inventory
Live roots4617 of 72 journeys and 29 of 118 automations — what the graph walks from
Orphaned items1,90056%Not referenced or used by anything running, untouched in 90 days

Inventory

All 7 categories · 3,413 items
CategoryItemsChanged 90dLiveIdleWrite-onlyUnverifiedOrphanedComplexity
Emails1,48621216441000912Medium
Templates & content blocks34231589200192High
Data extensions6121482361182118219High
Journeys7291700055High
Automations118232900089High
Automation activities38934111000278High
Folders39469614300155Low
Automation activities by type · 389 activities in 118 automations
ActivityItemsLiveOrphanedComplexity
SQL query21461153High
Import file461432Medium
File transfer381226Medium
Send email33726Low
Data extract27819High
Script19613High
Filter1239Medium

Dependencies

A reference is not the same as use. Every object below is classified by whether it is used by a live root — a running journey, an active automation schedule, a triggered send that has fired recently — not by how many things point at it.

Live711

Used by a running journey, automation or triggered send. These are the items the move is about.

Write-only21

Something is still writing here and nothing reads it — usually a broken integration, or a manual export nobody switched off.

Idle763

Referenced, but only by things that are themselves stopped. Follow the reference up before deciding.

Orphaned1,900

Nothing running references or uses it, and nothing has touched it in 90 days, so it is probably not needed. Leaving it behind is the cheapest win in the migration.

Unverified18

Referenced from AMPscript we could not resolve statically. Marked unverified rather than orphaned, because guessing here is how a tool talks somebody into deleting something load-bearing.

Orphaned items by category · 1,900 of 3,413 items, 56% of the business unit
CategoryOrphanedOf category
Emails91261%
Automation activities27871%
Data extensions21936%
Templates & content blocks19256%
Folders15539%
Automations8975%
Journeys5576%
What this run could and could not see

Edges resolved: journey entry sources and activities, automation activities, query targets and sources, email → template, email → content block, triggered send → data extension, folder parentage.

Not resolved: References constructed inside AMPscript or SSJS at send time. We could not resolve the LookupRows calls in 9 emails statically. The 18 data extensions they may touch are marked unverified rather than orphaned.

We publish this because the failure mode that matters is calling something orphaned when the reference keeping it in use was one we could not see. 18 named unverified objects is a better result than 1,900 confident ones.

Decisions

  1. 337 of 612 data extensions are not used by anything running

    Needs a decision

    Rebuilding all 612 on the target side is the expensive default. 219 are orphaned and can stay behind. The other 118 are referenced only by journeys and automations that have stopped, so somebody has to decide which are seasonal and which are abandoned before the scope is fixed. 21 more are still being written to with nothing reading them; find what writes to them before deciding.

  2. 6 of 17 active journeys use a Salesforce Data entry source

    Needs a decision

    Entry sources are modeled differently in Marketing Cloud Next, which builds on Data 360 rather than a direct Salesforce object subscription. These 6 need designing against the target model, not lifting across. The other 11 move with review.

  3. 61 SQL queries in 29 live automations need re-expressing, not moving

    Needs a decision

    Marketing Cloud Next has no Automation Studio. Each running automation is rebuilt as a scheduled Flow, Data 360 transforms and segment schedules, and each of its queries is re-expressed as a transform or as segment criteria rather than copied. The other 153 queries sit in automations nothing runs and can stay behind. The 6 live script activities need someone to decide what replaces them, because server-side JavaScript has nothing to run in.

  4. 284 of 342 templates and content blocks have no live email using them

    Needs a decision

    Content Builder's template model differs on the target side, so each one carried across is rework. 58 are actually in use. Carrying those and archiving the rest is substantially cheaper than porting all 342 — but it is a decision someone has to own.

This is our sample. Run it on yours.

A real scan produces the same kind of report for your own business unit. Read-only, nothing to install in your org, and free to start.

Start free Talk to us