SFMC Migration Discovery Pass
Run discovery in a sequence that captures inventory first, dependencies second and business importance third.
Evidence tier describes my hands-on relationship with the content. Official sources describe platform contracts/documentation. Production observations should not automatically be treated as official limits.
A migration-ready inventory that separates what exists, what depends on what and what actually matters.
Use a stable object inventory/export.
Keep client metadata private.
Agree on the migration scope and cutover boundary.
Inventory before redesign
Capture the actual environment before proposing a cleaner future state.
Normalize metadata
Transform inconsistent exports into stable records while retaining raw payloads for traceability.
Map execution dependencies
Connect automations, queries, targets, sends, Journey entry sources and CloudPages.
Classify business relevance
Automation can inventory objects; people still decide what is business-critical.
Validate migration objects with a checklist
Turn inventory findings into repeatable migration validation.
Turn the Recipe into checkable work.
Progress, notes and history stay in this browser.