The short answer
Reconcile a PMS migration by freezing or logging activity at one cutoff, preserving the source export, mapping fields, comparing source closing totals with target opening totals, tying cash to external evidence, and testing high-risk records. Record every difference, correction, owner, and retest. A successful import message is not proof of a successful migration.
Practical next step:
Put this workflow into practiceA software migration can be technically complete and operationally wrong. Rows arrive, totals look close, and the team starts using the new system—then an old concession reappears as rent, a deposit loses its tenant allocation, or a post-cutoff payment exists in only one place. Reconciliation is the control that separates “data moved” from “the new system can safely become authoritative.” Current PMS routes normalize supported exports into content-bound review staging with recorded hashes and review evidence. Approval does not create or change live portfolio records; a separately implemented, authorized, reconciled cutover is still required. OFX and QuickBooks Web Connect (.qbo) files can be parsed locally for format, date, amount, duplicate-ID, and unsafe-markup review. That preflight does not import, post, match, retain, or establish a QuickBooks Online API connection.
Guide evidence map
Preview the answer, sections, action steps, and questions this guide actually contains. This map describes the page's structure; it is not a rating or completion measure.
Direct answer (1)
Guide sections (6)
Action steps (4)
Common questions (4)
Direct answer
1
Reconcile a PMS migration by freezing or logging activity at one cutoff, preserving the source export, mapping fields, comparing source closing totals with target opening totals, tying cash to external evidence, and testing high-risk records. Record every difference, correction, owner, and retest. A successful import message is not proof of a successful migration.
Section connection graph
Choose a section to follow it to a key takeaway already on this page. The pairing uses repeated terms in this guide's own copy; if no terms repeat, it follows the guide's reading order.
1. Define the controlled position before exporting anything
2. Map meaning, not just column names
3. Use a three-way bridge for cash and deposit obligations
4. Sample records by consequence, not convenience
5. Turn differences into an exception log
6. Release, rollback, and stabilize deliberately
Guide section
Define the controlled position before exporting anything
Connected takeaway
Matching row counts do not prove matching obligations, balances, or chronology.
The animated line only confirms the current selection; it does not indicate priority, progress, or a score.
Decision reading path
Start with the action you are making, then read the section that uses the closest wording. When there is no wording match, this follows the guide's written order.
1. Freeze and preserve
2. Map and dry-run
3. Reconcile and retest
4. Release and stabilize
Step 1 of 4 → section 1 of 6
Your action
Freeze and preserve
Name the scope and cutoff, control new activity, and retain the untouched source export.
Read next
Section 1: Define the controlled position before exporting anything
Connection basis: shared wording — freeze, preserve, name, activity.
The line shows where the linked section appears in this guide. It is not a priority, completion, or confidence score.
Implementation readiness gates
The migration release gates
Pass each gate with retained evidence. A record-count match is useful, but money, active obligations, and source custody remain hard release conditions.
1. Scope and cutoff
2. Lease and resident position
3. Cash and liability bridge
4. History and custody
Scope and cutoff
Evidence
Property list, entity list, migration scope, source timezone, and cutoff timestamp
Pass condition
Every included record and every post-cutoff transaction has one named destination.
Failure signal
Teams export at different times or continue posting without a controlled delta log.
Reversible rollout sequence
1
Dry-run the full export and import using the same scope and field map planned for production.
2
Reconcile in a read-only target, correct the mapping or source record, then rerun instead of hiding defects with plugs.
3
Approve the cutover only when critical gates pass and the rollback trigger remains usable.
4
Run a controlled stabilization close and archive the signed evidence packet.
These are evidence gates, not percentages. A failed gate pauses or narrows the rollout instead of averaging into a misleading readiness score.
Define the controlled position before exporting anything
Write one migration sentence that a reviewer could test: “Move the active operating records for these legal entities and properties through 11:59 p.m. Eastern on July 31, including the listed history and attachments.” Name what is excluded, how post-cutoff activity will be handled, and which system is authoritative during the freeze, delta, and stabilization windows.
Build a record inventory before a field map. Count properties, units, active and future leases, open balances, refundable deposits, vendors, recurring charges, open work orders, documents, and event history. Counts are not reconciliation, but they expose missing categories and make it harder to discover after cancellation that a legacy export omitted attachments or inactive records.
Use legal entity and bank-account boundaries—not one portfolio-wide total that lets errors offset.
Preserve the unmodified source export with a timestamp and checksum or other integrity record.
Name the archive owner and prove a second person can retrieve it.
Map meaning, not just column names
A source “balance” field can mean current amount due, all-time net charges, or a display figure after credits. A target field with the same label may calculate something else. For every high-risk field, record the source definition, target definition, transformation, null behavior, accepted values, effective-date rule, and reconciliation control.
Treat identifiers separately from labels. Tenant names, unit labels, and vendor names can repeat or change; stable source IDs and a crosswalk make corrections traceable. Keep old IDs in a migration reference field or retained crosswalk so a later dispute can connect the new record to its origin without guessing.
Test zero, negative, blank, future-dated, inactive, amended, and duplicate records.
Separate contract rent, market rent, effective rent, charges, collections, and outstanding balances.
Define whether attachments, notes, approvals, and audit events are records, files, or both.
Use a three-way bridge for cash and deposit obligations
Compare the old system’s controlled closing balance with the new system’s opening balance for the same scope and time. Then connect the result to independent evidence—usually a reconciled bank statement plus documented outstanding items. Two systems can agree with each other and still be wrong, so the external leg matters.
Refundable deposits need both a control total and tenant-level detail. In a five-unit example, the source and bank may both support $6,840 while the target shows $6,740. The missing $100 could be unapplied cash, a deposit allocation, or a mapping defect. Record the exact tenant or transaction, cause, correction, and retest; do not post a portfolio-level $100 adjustment that makes the total look clean while leaving the resident record wrong.
Sample records by consequence, not convenience
Random samples help find ordinary defects, but a small landlord can often inspect every active lease and every open balance. Add risk-based samples: recently renewed leases, mid-month changes, concessions, partial payments, returned payments, roommates, transfers, deposit changes, open notices, recurring vendor bills, and records with attachments.
Test the target as a workflow, not only a database. Generate a tenant ledger, rent roll, owner statement, deposit report, payment batch, renewal list, open-work-order list, and export. A value can exist in a table yet be absent from the report or workflow the landlord will actually use.
Turn differences into an exception log
Each exception should name the source record and value, target record and value, effect, suspected cause, correction owner, correction method, retest evidence, and disposition. Grouping everything under “migration cleanup” destroys accountability and makes the same transformation bug look like dozens of unrelated manual errors.
Correct the earliest reliable layer. If the field map is wrong, fix the map and rerun. If the source record is wrong, document and approve the source correction before re-exporting. Use a target-side adjustment only when it represents a legitimate opening entry with durable supporting evidence—not as a way to force a control total.
Release, rollback, and stabilize deliberately
Define a rollback trigger before production: for example, an unexplained cash difference, missing active lease, inaccessible deposit detail, or failed payment-provider connection. Rollback may mean extending the legacy read-only window and pausing new activity rather than trying to reverse every imported row.
After launch, perform a stabilization close using the first real payment, invoice, owner transaction, work order, and reporting cycle. Compare opening-to-closing movement in both operational and accounting records. Sign and retain the source export, target reports, bank evidence, exception log, approvals, and archive instructions as a single migration release packet.
Action plan
Stage 1 of 4
Freeze and preserve
Name the scope and cutoff, control new activity, and retain the untouched source export.
Select a stage to trace the exact handoff. The rail marks the selected position in this guide's own workflow; it is not a completion score.
1
Freeze and preserve
Name the scope and cutoff, control new activity, and retain the untouched source export.
2
Map and dry-run
Document field meanings and edge cases, then import into a read-only test target.
3
Reconcile and retest
Bridge totals to details and external evidence; fix causes and rerun failed controls.
4
Release and stabilize
Approve with a rollback path, then verify the first live operating cycle.
Key takeaways
Matching row counts do not prove matching obligations, balances, or chronology.
Use one cutoff, entity-level totals, tenant-level detail, and an independent cash leg.
Fix mapping defects at the source of the error instead of hiding them with opening-balance plugs.
Keep the legacy export and signed release evidence retrievable after go-live.
Frequently asked
What is PMS migration reconciliation?
It is the evidence-based comparison of the source system’s controlled closing records with the target system’s opening records and external support. It covers totals, record detail, documents, history, exceptions, and the first live operating cycle.
Which records should block a property-management software cutover?
This framework treats missing or unexplained active leases, occupancy, tenant balances, deposit liabilities, cash, or critical source custody as cutover blockers. A portfolio can add stricter gates based on its contracts, accounting, jurisdiction, and risk.
Should I keep access to the old PMS after migration?
Keep a controlled legacy archive or read-only access until documents, history, reports, and identifiers have been exported and retrieval-tested under the applicable retention policy. Do not assume a basic CSV contains the complete operating record.
Is a migration test environment enough?
No. A dry run is essential, but the release also needs a controlled production cutoff, external balance evidence, exception ownership, rollback conditions, and a stabilization review after real activity begins.
Keep reading
All reviewed guidesGetting started
How to switch property management software without losing data
AI & autonomy
Property-management system of record: decide which data wins
Getting started
Property management field mapping before a migration or integration
Getting started
Out-of-state landlord operating guide: local coverage without losing control
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
Let the agent help with the routine.
Aptoria helps coordinate supported routine work from this guide inside configured limits. Free for your first unit.