01 / The work
Review before committing the rows.
A migration can create lasting confusion if columns, amounts or people are matched incorrectly. SettleLift’s import prototype uses an explicit dry run, highlights errors and requires choices for duplicates instead of silently rewriting existing clients.
02 / The process
Make migration a reviewable process.
- Paste a CSV with the supported headers and inspect the parsed rows. Quoted names, row widths and currency values are checked.
- Resolve validation errors and unknown columns. Review in-file duplicates and possible existing-client matches explicitly.
- Commit the reviewed rows and inspect the resulting client/debt relationships. Keep the source file and migration evidence for a future audited import.
03 / Context & decisions
What stays connected
Review the source inventory, column mapping, duplicate choices and linked debts before records are committed. A production move needs file counts, reconciliation and a rollback plan. Historical payment evidence should retain its source.
Current scope & remaining work
04 / Product status
What you can explore today.
- Working preview
- CSV dry run, validation, duplicate choices and reviewed local commit.
- Prepared backend
- Tenant-aware relationships for imported records.
- Connection work remaining
- Audited bulk migration, file transfer, rollback and reconciliation tooling.
05 / Common question
Can I upload a full export from another CRM?
Not as a one-click migration today. Its exact schema and files must be mapped and reviewed before a production importer is enabled.