Short answer: an AppFolio migration should begin with a complete record inventory and end only after accounting, resident, owner, maintenance, document, and permission workflows agree in the new system. Exporting names and balances is not enough. Preserve the source reports, attachments, audit context, and definitions that explain those values.
AppFolio markets guided onboarding and specialist data handling for teams moving into its platform. Moving away from any established property-management system deserves the same discipline. This guide is independent and is not affiliated with AppFolio. Available exports, retention requirements, contract terms, and assistance can vary, so confirm the current scope with AppFolio and qualified accounting or legal advisers before setting a cancellation date.
1. Define why the team is moving
Write down the workflows that must improve and the conditions that would make the migration a failure. Examples include faster maintenance assignment, simpler owner reporting, lower total cost, cleaner mixed-rental calendars, better field access, or more understandable permissions. This prevents the team from recreating the same process in a different interface.
2. Build a source-system inventory
Record every active module, integration, portal, report, custom field, recurring charge, bank connection, template, automation, and user role. For each item, identify its business owner, replacement destination, export method, retention requirement, and validation test.
- Properties, units, owners, residents, applicants, leases, and vendors.
- Charts of accounts, bank accounts, opening balances, deposits, payables, receivables, and owner distributions.
- Work orders, inspections, unit turns, photos, invoices, and unresolved approvals.
- Documents, communication history, templates, custom fields, permissions, and integration identifiers.
- Current and historical reports needed for tax, owner, audit, or dispute support.
3. Ask for the export scope in writing
Do not assume every visible screen has a matching bulk export. Ask what can be exported, in which formats, whether attachments are included, whether stable identifiers are preserved, how long access remains available after notice, and what assistance is offered. Test a sample export early. A CSV that looks complete may omit notes, relationships, files, or transaction detail required to explain a balance.
4. Create a mapping workbook
Map each source field to the destination field, transformation rule, default, and exception owner. Keep original IDs in a legacy-reference field when possible. Normalize addresses, phone numbers, dates, property and unit names, status values, and owner relationships without overwriting the untouched source export.
The broader property management software implementation checklist provides a 30-day framework for ownership, testing, training, cutover, and post-launch review.
5. Close and reconcile before cutover
Choose a financial cutoff date. Complete bank reconciliation through that date, document outstanding checks and deposits in transit, review tenant and owner balances, resolve duplicate vendors, and identify transactions that will remain open. Preserve a final trial balance and the reports used to support it.
For accounts that hold money on behalf of others, the three-way reconciliation checklist explains how adjusted bank cash, book cash, and supporting sub-ledgers should be compared. Local trust-account and record-retention rules still require professional review.
6. Pilot one representative slice
Use a property that includes an active lease, owner relationship, open work order, recent payment, expense, attached document, and upcoming renewal. Import it, then complete the work that happens on a normal day. A successful row count is not a successful migration if users cannot locate the lease, explain the balance, or close the repair.
7. Validate by control total and workflow
- Compare record counts by property, unit, owner, resident, lease, vendor, and document type.
- Compare cash, receivables, payables, deposits, owner balances, and income and expense totals as of the same cutoff.
- Open a sample of attachments and confirm they belong to the correct records.
- Verify user roles with least-privilege accounts, not only an administrator.
- Run rent, maintenance, owner reporting, move-in, move-out, and export workflows end to end.
8. Communicate portal and payment changes
Residents and owners need a clear timeline, verified destination, support route, and explanation of what changes. Avoid sending sensitive setup instructions through an unverified channel. Confirm payment processing, autopay behavior, outstanding balances, portal invitations, and document availability before declaring the switch complete.
9. Keep the old system read-only
Where the agreement permits, retain read-only access long enough to answer exceptions and complete required retention. Store final exports in controlled, backed-up storage with an inventory and checksum. Do not leave former staff accounts or unnecessary integrations active merely because the application remains available.
Frequently asked questions
How long does an AppFolio migration take?
There is no universal duration. Portfolio size, accounting cleanup, attachment volume, integrations, export availability, training, and the number of exceptions matter more than a vendor estimate. Plan around validated milestones rather than a date alone.
Should every historical transaction be imported?
Not automatically. Decide what the destination must calculate, what users need to search, and what can remain in an immutable archive. Preserve legally and operationally required records even when they are not loaded into the new application.
When should the AppFolio account be canceled?
Only after exports are complete, destination workflows pass, financial totals reconcile, portal and payment transitions are confirmed, retention needs are satisfied, and the contractual notice period is understood.
Bottom line
A controlled AppFolio migration protects meaning, not just rows. The destination should be able to explain who a record belongs to, how a balance was produced, what work remains open, and which evidence supports the next decision.