Migrate to PesoLend without freezing collections
A staged path to move open loans, staff habits, and reporting from spreadsheets or legacy tools into a cleaner operating core.
Migration principles
Collections cannot stop while IT experiments. Good migrations protect cash posting continuity, freeze scope early, and compare old versus new balances before cutover. PesoLend recommends parallel runs and branch-by-branch expansion when networks are large.
Read features so stakeholders know what is in MVP, and security so access is redesigned rather than copied blindly.
What to migrate first
- Borrower identities and contact details.
- Open loan balances, products, and schedules.
- Officer and branch assignments.
- Historical repayments needed for disputes (as practical).
Recommended stages
1) Discover and clean
Inventory products, exception policies, and spreadsheet versions. Deduplicate borrowers. Decide which balances are authoritative.
2) Configure and pilot
Set roles, products, and one pilot branch. Train posting until cashiers and collectors trust the screens.
3) Parallel run
Operate old and new paths together for a defined window. Compare dues, collections, and outstanding totals daily.
4) Cut over
Freeze writes on the old tool for the pilot scope. Keep a rollback note for emergencies. Expand to the next branch only after reconciliation is clean.
5) Optimize
Add reminders and integrations after posting quality is proven — see integrations and API.
People and change risks
The hardest part is habit. Collectors may keep side notebooks. Managers may keep private trackers. Address that in training using the {a(‘/glossary/’,’glossary’)} and {a(‘/guides/’,’guides’)}.
- Name a business owner for migration, not only an IT owner.
- Measure posting accuracy and due-list adoption, not vanity login counts.
- Celebrate the first clean week of matching cash and system totals.
Multi-site operators should sequence with multi-branch patterns. Field teams should align routes via field collections.
Data cleaning playbook
Deduplicate borrowers by name plus unique ID where available. Normalize phone numbers. Flag loans with impossible schedules. Decide treatment for fully paid accounts you still want historically visible.
Assign a data owner who can make judgment calls daily during the pilot. Without that owner, migrations stall in chat threads.
Cutover day habits
- Freeze old writes for the pilot scope at a known time.
- Post a short war-room checklist.
- Compare outstanding totals before opening the branch.
- Keep a rollback contact list printed, not only digital.
Related: security, integrations and API, guides, pricing, contact, login.
When to pause expansion
If posting lag grows, if cash mismatches persist, or if staff reopen side notebooks, pause new branches. Fix habits before you multiply them. That discipline is how networks scale cleanly with multi-branch patterns.
Communication plan during cutover
Tell staff what changes on cutover morning, what stays the same for borrowers, and where to escalate. Tell borrowers only what they need — usually nothing if payment channels are unchanged. Over-communicating system internals creates anxiety without improving posting.
Keep a visible issues log for the first two weeks. Close issues with owners and dates. Celebrate the first clean reconciliation publicly inside the company.
- Pilot branch announces go-live date early.
- HQ monitors exception volume daily.
- Training refresh scheduled for week two.
Continue: features, why PesoLend, customers, FAQ.
Legacy spreadsheet triage
Label each workbook as authoritative, reference-only, or discard. Most organizations keep too many reference files that still get edited.
Archive discard files read-only. Move authoritative balances into the migration set with operations and finance sign-off.
- Workbook inventory complete.
- Authoritative sources signed off.
- Parallel run differences explained daily.