Moving to Marketing Cloud Next is not a lift-and-shift.
re:target reads your Marketing Cloud Engagement business unit and shows what is in it, what is still used, and what has to be decided before anything moves. Starting costs nothing: no card, and no commitment to buy. And the move is yours: run it with your own team or partner, or bring ours in.
re:target assess · one business unit · three scans · no card
Migration complexity:Medium
- Items inventoried
- 3,413
- Orphaned
- 1,900 · 56%
- Active journeys
- 17 of 72
From a legacy business unit to a decision you can defend.
How complex the move is
Low, medium or high — for the business unit and for each category, with the reason stated beside it.
The business unit as it really is
Assets, folders, data extensions and journeys, connected by their dependencies.
What can stay behind
We walk outward from running journeys and automations. In our sample org, 56% of the business unit is orphaned.
What needs redesign
The things that do not map cleanly to Data 360, Flow and Marketing Cloud Next, with the decision stated plainly.
Assess for free. Plan per business unit. Transform with us.
re:target assess
FreeOne business unit and three scans. See what is in it, what is still used, and how complex the move is, then walk through the result with us.
re:target plan
Per business unitThe ordered migration plan with effort estimates and every item's dependency tree. Mark each item move, rebuild or leave behind, track it as it moves, and export the lot for your own tooling or AI.
re:target transform
Per use caseA scoped engagement: our team moves what can be moved, with re:target automating what it can, rebuilds the rest, and leaves you with a roadmap and a business unit running on Marketing Cloud Next.
Private hosting on dedicated infrastructure is a paid engagement on any of the three.Pricing and questions
Move it, rebuild it, or leave it behind.
Marketing Cloud Engagement and Marketing Cloud Next are different technologies, with different data and orchestration models. Some capabilities can coexist for a while; some assets should be rebuilt; some should never move. re:target gives each one a defensible disposition instead of pretending every object has a one-to-one destination — and with re:target plan you mark each item, add your notes, and track the move until it is done.
For the team making the decision, and the partner delivering it.
Replace assumptions with a migration baseline.
Give marketing, architecture and procurement the same view of the business unit before budgets and waves are fixed.
- Reduce scope before you pay to rebuild it
- Separate coexistence candidates from migration work
- Carry evidence into architecture and partner conversations
Streamline discovery with a white-label report.
re:target does the inventory, so your team spends its expertise where it matters: target design, sequencing and delivery. If you want more hands on a move, ours can help.
- A white-label report with your logo and colors, ready for the client
- Your experts on the decisions, not on the assessment
- The same discovery on every client, whoever runs it
You are granting API access to a production marketing org. We treat that seriously.
Every permission we request is read, and the connect page lists all six before you create the package. Hosting is in the US, or in the EU on request at no extra cost. If your org cannot send metadata through shared infrastructure at all, private hosting runs re:target on a dedicated instance, on any offer.
- Never written
- 0 write permissions
- Data retention
- Until you delete it
- Subscriber data
- Never read
- Hosting
- US, or EU on request
Years of ExactTarget and Marketing Cloud Engagement work leave behind more than assets. They leave assumptions, stopped journeys, hidden dependencies and integrations nobody wants to touch. re:target turns that history into evidence, so the next architecture starts with facts.