Salesforce bought ExactTarget in 2013 and spent the following decade renaming it. Email Studio, Marketing Cloud, Marketing Cloud Engagement — the label on the tin changed several times while the thing inside it accumulated years of data extensions, AMPscript, triggered sends and journeys.
Now there is Marketing Cloud Next, and we know what moving to it is not. It is not a lift-and-shift: Engagement and Next are different technologies, built on different data and orchestration models. Teams have to decide what moves, what is rebuilt, and what continues to run in Engagement for a while. That decision still starts with an awkward question: what is actually in the business unit, and which parts are still doing useful work?
We built re:target because inventory and dependency work is too important to be improvised in a spreadsheet, and because a migration scope should distinguish live architecture from the debris a long-lived platform naturally accumulates.
It reads, counts, traces and classifies, and it never writes to Engagement. What you do with the evidence is a decision, and decisions are not something we pretend to automate.