Enterprise platforms accumulate years of undocumented logic. Approval thresholds, vendor deduplication rules, exception handlers, automations that stopped running — all of it lives in the transaction history, not the configuration. Canaan ingests the full history and runs pattern analysis to reconstruct what the system actually does. Not what it was configured to do. What it does.

A complete inventory of the rules, exceptions, and dependencies governing the source system. It is the translation layer between what the source system holds and what the destination system expects. Every item documented. Every ambiguity surfaced — not resolved. The map does not decide. It shows. Nothing moves without a corresponding entry on the map.

Decision-making belongs to the business. Which vendor record is canonical when duplicates exist. Whether a deprecated workflow has a destination equivalent. Whether an entity appearing in hundreds of transactions should migrate, be cleaned, or be retired. Canaan surfaces each as a discrete question with full context. Migration proceeds when each is resolved.

Structure before transactions. Transactions in chronological order. Edge cases in the order their dependencies allow. Destination systems validate records against their context — so every record's context exists before the record itself moves. Dependency order eliminates validation failures by design, not by exception handling.

A populated destination system. A complete log of every record that migrated, its source, and the decision governing how it was handled. Documentation of the source system's logic — typically produced for the first time during the engagement. Every record traceable to its origin. Every rule written down for the people who inherit the new system.