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 nine years of data extensions, AMPscript, triggered sends and a Send Log that somebody once promised would always be there.
Now there is Marketing Cloud Next, and the orgs have to move. That move starts the same way every time: somebody opens the Marketing Cloud UI and starts counting. How many templates. How many automations. Which of the data extensions are still referenced by anything. Which of the triggered sends point at something that was deleted in 2019 and has been silently failing over ever since.
We built re:target because the first weeks of any Marketing Cloud Next migration go into manual inventory work that a tool should be doing, and because nobody enjoys explaining to a client that the Send Log they have depended on for nine years is not coming with them.
It is a measurement instrument, not a migration engine. It reads, it counts, it tells you what will not move and roughly what the move will cost in developer days. What you do with that is a decision, and decisions are not something we are trying to automate.