Bulk imports and data migration

Moving members, loans and savings from spreadsheets or an old system — and importing daily bulk transactions.

Zung imports data from spreadsheets so you can migrate from another system and post large batches of transactions.

Import	Where	Typical use
Members (clients)	Members → Import	Migration; onboarding a new group or employer
Loans	Loans›Import loan	Migrating the active portfolio
Savings accounts	Savings›Import savings	Migrating accounts and opening balances
Loan repayments	Loans›Bulk repayments → import	Payroll check-off, M-Pesa statements
Savings deposits	Savings›Bulk deposits → import	Payroll check-off

How to import

Download the template from the import screen — always use the current template, not an old copy.
Fill one row per record. Keep the column headings exactly as they are.
Use the IDs Zung expects for products, branches, officers and payment types (shown on their list screens).
Upload. Zung validates every row and tells you which rows failed and why.
Fix the failed rows and upload them again.

Imports only accept products, members and officers from your own institution — a row pointing at another institution’s record is refused.
Blank lock-in or opening-balance cells in a savings import fall back to the product’s values.
The member import accepts the template format offered on its page.

Freeze transactions in the old system at a cut-off date.
Import members, then savings with opening balances, then active loans with their outstanding balances.
Post opening balances for the general ledger.
Reconcile: number of members, total savings, portfolio outstanding and PAR must match the old system’s reports at the cut-off.
Only then start posting new transactions in Zung.

Important

Run the full migration in a test institution first. A failed migration in production is very hard to unwind.