Mapping audit

Mapping Audit records how each legacy field was matched to a suite field during migration, including unmatched or transformed values. It gives a transparent trail of the conversion logic so data lineage can be proven. Implementers and auditors use it to validate that imported balances and members carried over correctly.

Mapping audit
Mapping audit — live screen from the BridgeERP MFI Suite.

Workflow

  1. Open MFI > Configuration > Tools > Migration > Mapping Audit
  2. Filter by migration run to scope the entries
  3. Review how source fields mapped to suite fields
  4. Investigate unmatched or flagged transformations
  5. Confirm mappings before signing off a conversion

Fields reference

Every field on this screen, drawn from the live data model.

FieldTypeRequiredDescription
Run
run_id
Link → mfi.migration.runYesRun
Entity
entity
Choice: Member, Savings account, Savings transaction, Loan, Loan scheduleYesEntity
Source
source_id
TextYesSource
Destination
destination_id
NumberYesDestination
Note
note
TextNote

Notes & rules

  • Model mfi.migration.mapping -- field-mapping trail
  • Key fields: source field, target field, transform, run
  • Related: Runs, Source Formats
  • Used by implementers and auditors

Technical model: mfi.migration.mapping · Record: Migration mapping audit record

Was this page helpful?