What is re:target
A migration readiness analyzer for Marketing Cloud Engagement. It reads a business unit and shows what the move to Marketing Cloud Next involves, before the project is scoped.
Marketing Cloud Engagement and Marketing Cloud Next are built on different data models, so a business unit cannot be copied across as it is. Before a migration can be priced or scheduled, someone has to establish what the business unit contains, what is still in use, and what has to be redesigned. re:target does that work from the metadata, and turns it into a report you can scope against.
How it works
- Connect a business unit through an installed package with read permissions only.
- Scan. re:target inventories emails, templates, content blocks, data extensions, journeys, automations and folders, then builds a dependency graph from everything that is running.
- Read the report. Each category is rated for migration complexity, with the reason stated, and the open decisions are listed.
What the report shows
| Figure | What it shows |
|---|---|
| Items inventoried | Every metadata item in the business unit, across its categories and folders. |
| Changed in last 90 days | Items created or modified recently, and their share of the inventory. |
| Live roots | Running journeys and active automations — where the dependency graph starts. |
| Orphaned items | Items nothing running references or uses, untouched for 90 days. Usually safe to leave behind. |
Below the summary, three sections carry the detail: Inventory (counts and complexity per category), Dependencies (what is live, idle, write-only or orphaned, and which references could not be resolved) and Decisions (what must be settled before the migration can be scoped).
| Category | Items | Changed 90d | Live | Idle | Write-only | Unverified | Orphaned | Complexity |
|---|---|---|---|---|---|---|---|---|
| Emails | 1,486 | 212 | 164 | 410 | 0 | 0 | 912 | Medium |
| Templates & content blocks | 342 | 31 | 58 | 92 | 0 | 0 | 192 | High |
| Data extensions | 612 | 148 | 236 | 118 | 21 | 18 | 219 | High |
| Journeys | 72 | 9 | 17 | 0 | 0 | 0 | 55 | High |
| Automations | 118 | 23 | 29 | 0 | 0 | 0 | 89 | High |
| Automation activities | 389 | 34 | 111 | 0 | 0 | 0 | 278 | High |
| Folders | 394 | 6 | 96 | 143 | 0 | 0 | 155 | Low |
| Activity | Items | Live | Orphaned | Complexity |
|---|---|---|---|---|
| SQL query | 214 | 61 | 153 | High |
| Import file | 46 | 14 | 32 | Medium |
| File transfer | 38 | 12 | 26 | Medium |
| Send email | 33 | 7 | 26 | Low |
| Data extract | 27 | 8 | 19 | High |
| Script | 19 | 6 | 13 | High |
| Filter | 12 | 3 | 9 | Medium |
Migration complexity
Complexity measures how much judgment a category needs, not how long it will take.
| Rating | What it indicates |
|---|---|
| Low | The structure recreates cleanly on the target side. |
| Medium | Nothing blocks the move. The cost is mainly volume and review. |
| High | The model differs on the target side, so items have to be redesigned rather than lifted across. |
Scope
- re:target assesses. Running a report changes nothing in your account.
- It reads schemas, definitions and counts — never subscriber data or data extension rows.
- Where you want the move handled, re:target transform is scoped per use case: our team moves what can be moved, with re:target automating what it can, and rebuilds the rest.
Who it is for
- Customer teams — marketing, architecture and procurement get the same view of the business unit before budgets and migration waves are fixed.
- Salesforce partners — re:target does the inventory and produces a white-label report for the client, so your team spends its time on target design, sequencing and delivery.How partners use it.