Clean the core before the migration.
Classify custom code, interfaces, and data debt before selecting what moves, retires, or shifts to an extension layer.
Operating pattern
A migration can carry forward custom code, interfaces, and data conditions whose current purpose is unclear. Moving every object preserves that ambiguity in the target environment.
The cleanup decision needs evidence about usage, dependencies, business purpose, and the target platform’s standard capabilities.
Capability pattern
Inventory the relevant objects and dependencies, then classify each item: retain in the core, rebuild as an extension, replace with standard capability, retire, or hold temporarily with an explicit reason.
Keep the classification and its evidence visible so migration and process teams work from the same decisions.
What the pattern enables
The pattern connects data and workflows. Data conditions are examined alongside the processes that created them, while migration scope is tied to documented business purpose rather than object count alone.