Short answer: migration sign-off should prove that approved source records were mapped, loaded, counted, reconciled, sampled, and tested in the destination; that balances and critical workflows remain correct; that exceptions have owners; and that cutover, rollback, communication, and post-launch checks are ready. A successful import message is not evidence that the portfolio migrated correctly.
GAO describes leading migration practices that include data cleaning and validation, cutover planning, go-or-no-go decisions, reconciliation, and performance measures. Current AppFolio and Buildium guidance also emphasizes clean source data, defined cutoffs, role-based training, and controlled transition periods. This independent checklist is educational guidance, not an accounting opinion, security certification, legal instruction, vendor warranty, or guarantee against disruption.
Freeze a defined source snapshot
Record the source systems, extraction time, portfolio scope, entities, files, filters, time zone, and hash or other integrity evidence. Define which system remains authoritative for each workflow during the transition. Uncontrolled edits after extraction make later count and balance differences difficult to explain.
Approve the mapping before the final load
Map property, unit, owner, resident, lease, vendor, account, transaction, work order, document, note, identifier, date, status, and custom fields. Record transformations, defaults, exclusions, and destination constraints. Use the data quality scorecard to distinguish source defects from migration defects.
Reconcile counts and control totals
Compare source and destination counts by entity and property. Reconcile opening balances, receivables, payables, deposits, owner funds, bank totals, recurring charges, credits, and unresolved items through qualified financial review. Preserve the exact query, report, cutoff, result, difference, explanation, and approver.
Test relationships and documents
Confirm that leases connect to the correct units and residents, properties to owners and accounts, work orders to properties and vendors, and documents to the intended records. Test file readability, names, dates, versions, permissions, and representative historical retrieval.
Download the migration sign-off
Download the editable data migration validation and cutover sign-off (CSV). It covers scope, source evidence, mapping, counts, balances, relationships, documents, permissions, workflows, integrations, exceptions, rollback, approval, and hypercare.
Validate permissions after data arrives
Test what each staff, owner, resident, vendor, and service role can see and change. Include denied tests and cross-property isolation. Migrated data can expose information even when the application feature itself works. Connect the tests to the permissions matrix.
Run day-one workflows end to end
Test rent and charge creation, payment posting, owner reporting, maintenance intake, vendor dispatch, resident messages, lease dates, documents, exports, and audit events. Use realistic pilot properties and preserve outputs. A screen loading correctly does not prove the accounting or downstream record is correct.
Reconcile integrations and scheduled work
Verify identity, payments, banking, email, messaging, screening, calendars, storage, access, and reporting flows. Confirm identifiers, direction, schedule, retries, duplicate handling, and control totals. Use the integration reconciliation playbook for delayed or conflicting records.
Set go-or-no-go and rollback authority
Define blocking conditions, accepted residual exceptions, decision authority, latest safe rollback point, restoration source, communication owner, and business-continuity path. The decision should reference current evidence rather than project pressure or a target date alone.
Close only after post-cutover reconciliation
Monitor balances, failed jobs, duplicate records, portal access, support volume, late integrations, report differences, and workflow outcomes through a defined period. Record each exception and final result. Use the release-readiness checklist to preserve the deployed change and closure decision.
Frequently asked questions
Should the old system be turned off immediately?
Not automatically. Define contractual access, security, retention, read-only use, cutover authority, and the period needed for reconciliation. Avoid uncontrolled dual entry.
Who signs off a property-management migration?
Assign one accountable migration owner, with qualified approval for financials, security, data, operations, and executive risk according to consequence.