Migration reconciliation compares the source system, transformation output, and destination system at an agreed cutoff. Its purpose is not to prove that the importer ran without an error message. It proves that material records arrived completely, retained their meaning, and can support the same operational balances and decisions after cutover.
Start with control totals and record counts by property: occupied units, active leases, deposit liabilities, open tenant balances, transaction sums, open work orders, vendor bills, and document counts. Then sample individual histories, especially difficult ones such as partial payments, reversed ACH entries, credits, lease changes, split deposits, and work orders with attachments. A matching portfolio total can still conceal a payment moved to the wrong tenant.
Imagine the source reports $18,450 of tenant receivables and the destination reports the same total. Row-level comparison reveals that a $600 credit was omitted from one tenant while a second tenant’s balance was understated by $600. Control totals pass, but ledger integrity fails. Reconciliation requires both aggregate agreement and record-level exception review.
Do not resolve differences with an unexplained opening-balance plug. Classify each exception as mapping, cutoff, duplication, missing source, unsupported destination field, or accepted transformation. Assign an owner, correction, evidence, and retest result. Keep the source export immutable, retain transformation versions, and obtain a provider receipt for each import attempt so the final cutover can be reproduced.
Three levels of proof
A migration is ready only when structural, financial, and operational checks agree.
•
Structural — expected records, relationships, documents, and stable IDs exist.
•
Financial — ledger, deposit, cash, receivable, and payable control totals reconcile.
•
Operational — active leases, payment settings, open work, notices, and owners remain actionable.
Scenario: equal totals, crossed tenants
Two $1,200 payments are swapped between units. The portfolio cash and receivable totals remain unchanged, so only a tenant-level join and sample statement reveal the error. Aggregate-only reconciliation would certify a migration that could send incorrect balances to both households.
Cutover decision
Proceed when every material exception is corrected, explicitly accepted with impact documented, or routed to a controlled post-cutover queue. Keep a rollback point until the destination produces the expected ledgers, documents, and workflows.
Related tools & guides
Editorial ownership
Written and maintained by the Aptoria editorial team
Repository and source review completed July 28, 2026. Aptoria reviews scope, source fit, examples, limitations, links, and publication gates. This record does not claim attorney, CPA, lender, appraiser, or other independent professional sign-off.
Primary and authoritative sources
Related terms
AI & autonomy
Data portability
The practical ability to export property data in documented, usable forms and move it to another system without losing meaning or evidence.
Accounting & tax
Tenant ledger integrity
The condition in which every tenant charge, payment, credit, return, and running balance is complete, traceable, and arithmetically consistent.
AI & autonomy
Property management system of record
The designated property-management source whose current records are authoritative for each defined class of operational data.
AI & autonomy
Provider receipt
A durable record from an external service showing what request it accepted, rejected, or completed under a provider-assigned identifier.
From definition to done
Aptoria runs the routine work behind these terms — rent, books, and screening — inside limits you set. Free for your first unit.
Start free