Runs — BridgeERP Docs

Runs lists each data-migration execution that imported records from a legacy core-banking or spreadsheet source, with counts, status and errors. It lets implementers track onboarding progress and re-run or fix failed batches. It is central to a clean, verifiable conversion when an institution adopts the suite.

Workflow

Open MFI > Configuration > Tools > Migration > Runs
Click New to start a migration run and pick the source
Upload or point to the source data file
Execute and monitor the import counts and errors
Review the Mapping Audit and fix any rejected rows

Fields reference

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

Field	Type	Required	Description
Default branch `branch_id`	Link → mfi.branch	Yes	Records without an explicit branch in the source will be assigned to this branch.
Website Messages `website_message_ids`	List	—	Website communication history
Dry Run `dry_run`	Yes/No	—	If True, the Commit button only stages and validates — no live writes.
Pull via REST API `api_mode`	Yes/No	—	When true, the operator fills credentials below; the Pull-from-API action populates the file attachments.
API base URL `api_base_url`	Text	—	e.g. https://acme.sandbox.mambu.com/api
Name `name`	Text	Yes	Name
Source Format `source_format_id`	Link → mfi.migration.source.format	Yes	Source Format
Has Message `has_message`	Yes/No	—	Has Message
Ratings `rating_ids`	List	—	Ratings
State `state`	Choice: Draft, Files staged, Validating, Ready to commit, Committed, Rolled back, Failed	—	State
Members CSV/XLSX `file_members_id`	Link → ir.attachment	—	Members CSV/XLSX
Savings accounts `file_savings_acc_id`	Link → ir.attachment	—	Savings accounts
Savings transactions `file_savings_txn_id`	Link → ir.attachment	—	Savings transactions
Loans `file_loans_id`	Link → ir.attachment	—	Loans
Loan schedules `file_loan_schedules_id`	Link → ir.attachment	—	Loan schedules
Rows Members `rows_members`	Number	—	Rows Members
Rows Savings Acc `rows_savings_acc`	Number	—	Rows Savings Acc
Rows Savings Txn `rows_savings_txn`	Number	—	Rows Savings Txn
Rows Loans `rows_loans`	Number	—	Rows Loans
Rows Loan Schedules `rows_loan_schedules`	Number	—	Rows Loan Schedules
Validation Report Json `validation_report_json`	Long text	—	Validation Report Json
Validation Report Html `validation_report_html`	Rich text	—	Validation Report Html
Is Valid `is_valid`	Yes/No	—	Is Valid
Commit Log `commit_log`	Long text	—	Commit Log
API username / consumer key `api_username`	Text	—	API username / consumer key
API password / consumer secret `api_password`	Text	—	API password / consumer secret
Tenant code (Musoni) `api_tenant`	Text	—	Tenant code (Musoni)
Api Page Size `api_page_size`	Number	—	Api Page Size
Mapping Count `mapping_count`	Number	—	Mapping Count

Actions & buttons

Buttons available on this screen and what they do:

Stage files
Validate
Commit (dry-run)
Commit (LIVE)
Pull from API

Status lifecycle

Records on this screen move through these statuses:

Draft → Files staged → Validating → Ready to commit → Committed → Rolled back → Failed

Notes & rules

Model mfi.migration.run -- import executions
Key fields: source format, counts, status, errors
Related: Source Formats, Mapping Audit
Used by implementers and data migration teams

Technical model: mfi.migration.run · Record: MFI Migration run