SFMC Migration Discovery
Minimum discovery path before moving an active SFMC business unit.
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.
Inventory objects
Data Extensions/fields/folders, automations, SQL, imports/exports, CloudPages, Content Builder, journeys and messaging assets.
Capture relationships
Map send/test relationships, automation steps, source/target DEs, external files/APIs and business rules.
Classify criticality
Separate active production paths from historical, orphaned, duplicated and unknown assets.
Identify identity model
Document SubscriberKey/contact-key rules, opt-in, suppression, publication lists and cross-brand overlap.
Map external dependencies
SFTP, APIs, CRM/connector, domains, sender authentication, IPs, packages and credentials.
Validate with humans
Automated inventory handles the heavy lift; domain owners confirm real business importance and undocumented exceptions.
Define migration waves
Group dependencies together and specify pre/post validation for each wave.
Build evidence
Keep exportable inventory, decisions, risks and validation results as migration artifacts.