Back to home

    Mapping Import

    Start with what you already have

    Most teams already maintain source‑to‑target mappings in spreadsheets. Magellan lets you import them directly — preserving your existing work while unlocking Semantic Match suggestions, lineage derivation, and the ULID‑keyed audit trail.

    Compare mapping-import steps

    Each step is a discrete pass with its own input artifact, its own role gate, and its own ledger entries. Predictive mapping enters only after validation and enrichment are complete — no Semantic Match Engine proposal reaches a Reviewer queue without a typed, validated mapping behind it, and a named SME signs every released decision.

    Import existing spreadsheets

    Input artifact

    .xlsx · .xls · .csv (column-mapping profile)

    Predictive mapping

    No

    Human-in-the-loop

    Contributor — resolve deferred rows

    Ledger entries

    SchemaIngestedMappingImportedMappingImportDeferredColumnProfileApplied
    Automatic MetaModel conversion

    Input artifact

    Imported rows + registered schema ULIDs

    Predictive mapping

    No

    Human-in-the-loop

    Contributor — resolve unmatched paths

    Ledger entries

    MetaModelProjectedTypeNarrowingDetectedMappingImportDeferred
    Validation & enrichment

    Input artifact

    Projected MetaModel mappings

    Predictive mapping

    Partial

    Human-in-the-loop

    Contributor — acknowledge warnings · Reviewer — clear errors

    Ledger entries

    ValidationRunCompletedEntityAnnotatedValidationFindingRaised
    Immediate predictive enhancement

    Input artifact

    Validated mappings + adjacent target attributes

    Predictive mapping

    Yes

    Human-in-the-loop

    Contributor — accept/reject proposals · Approver — release

    Ledger entries

    SemanticSuggestionReturnedSemanticSuggestionAcceptedLineageEdgeDerivedImpactAnalysisRun