Checklist · CRM Account Operations
CRM Export Reconciliation Before a Migration
Compare exported and imported records by identifiers, relationships and financial totals, with a worked example showing why matching counts can mislead.
Published Updated
Published by FxTrusts, a supplier of brokerage and prop firm technology. Prepared with AI-assisted research and drafting; reviewed against the cited public sources. Examples are illustrative. Product links describe our services.
Quick answer
A migration reconciliation compares source and destination records at a defined cutoff using identifiers, relationships, counts and relevant financial totals. Matching row counts or total balances alone is insufficient. The export must preserve meaning, ownership and the ability to trace exceptions back to original records.
Establish the snapshot and scope
State which clients, wallets, trading accounts, documents and historical events are included, along with the extraction time and allowed changes during the process. A moving source can make comparisons inconsistent. Database isolation can support a coherent local snapshot, but linked external systems may need separate cutoffs and reconciliation. Record exclusions and any data intentionally transformed instead of reporting an apparently complete migration that omits them.
Match keys and relationships before totals
Check unique identifiers, missing and unexpected records, parent-child links, currencies and environment scope. A duplicated record can compensate numerically for a missing one and leave the row count unchanged. Similarly, balances can sum correctly while being attached to the wrong clients. Preserve a mapping from source IDs to destination IDs and validate ownership independently of display names or email addresses.
Reconcile financial meaning and precision
Compare amounts in their own currencies and account models before conversion or aggregation. Simulated balances, credits and real wallet funds should not be collapsed into one total. Check decimal precision, sign conventions, dates and timezones, and document any normalization. A checksum can help detect file changes, but it does not prove that a transformation preserved business meaning. Use targeted record-level comparisons and explain every material exception.
Close exceptions through an approved sign-off
Classify mismatches by cause, impact, owner and resolution. Re-run the affected checks after a correction and retain both attempts. Protect exports with least-privilege access and an approved retention policy because they can contain sensitive records. Do not start a migration cutover solely because a spreadsheet total matches. The broader migration guide owns sequencing and rollback; this worksheet supplies the evidence that the transferred records are internally consistent.
Equal counts and totals with the wrong account
In this synthetic dataset, the source contains A=10, B=20, C=30 and D=0 units. The destination contains A=10, B=20, C=30 and E=0. Both have four rows and total 60, but D is missing and E is unexpected. A count-and-total check passes incorrectly; an identifier-set comparison finds the issue before account ownership or future events are mapped to the wrong record.
| Check | Source | Destination | Result |
|---|---|---|---|
| Row count | 4 | 4 | Matches |
| Amount total | 60 | 60 | Matches |
| Identifier set | A, B, C, D | A, B, C, E | Mismatch |
| Required resolution | Preserve D mapping | Investigate E creation | Do not sign off yet |
Implementation checklist
- Define extraction scope, cutoff and treatment of concurrent changes.
- Compare IDs, ownership and relationships before relying on totals.
- Reconcile currency, precision, signs and account models explicitly.
- Track exceptions, retests and authorized sign-off with protected exports.
Sources
These documents support the reference. Check the original publication for current requirements and the limits of its scope.
- PostgreSQL transaction isolationwww.postgresql.org
- OWASP authorization guidancecheatsheetseries.owasp.org
- OWASP logging guidancecheatsheetseries.owasp.org
Continue with the broader guides
Connect this reference to platform selection and the wider operating workflow.