Switching from AppFolio is a data project before it is a software decision. What decides the outcome happens before you sign anything: a complete export, a parallel run measured in closes, and written go live criteria. URBI onboards buildings through that exact sequence, and this is the plan.
Why do property managers start planning an exit?
Most exits start with a workflow that will not bend, not a feature that is missing. AppFolio is a capable platform and its own reviewers say so. A Resident Manager writing on G2 in April 2026 credits it with pulling leasing, accounting, maintenance, and communication into one place, then adds that reporting and certain workflows "can feel a bit limited when it comes to customization". Four triggers recur in public reviews, each worth reproducing on your own account before you treat it as a verdict.
- Accounting architecture. An Accounting Manager writing on G2 in April 2026 wrote that "integration with other systems like QuickBooks Online is limited", while praising the same platform for centralizing accounting and reporting in one place.
- Support access. Reviewers on Capterra and Trustpilot through 2026 describe long waits to reach a person after the sale, while still calling the underlying technology good.
- Payment and cancellation friction. Trustpilot reviewers in 2026 describe errors on some payment methods and friction when winding down.
- Portfolio fit. AppFolio requires a minimum of fifty units, which puts single building associations outside its target market.
For a scope by scope look at the alternative, see the URBI and AppFolio comparison.
What should you extract before you give notice?
Extract everything you would need to run the portfolio for a year if the platform vanished tomorrow. Ask in writing, with a date, while you are still a customer in good standing, and store it outside both platforms in a document structure that survives staff turnover.
| What to pull | Format to request | Why it matters later |
|---|---|---|
| Full general ledger and chart of accounts, every year | CSV, one row per journal line, with account, fund, property, date | Your audit defense and your opening balances |
| Trial balance and bank reconciliation, each month end | PDF and CSV | The frozen record you reconcile against |
| Owner and resident ledgers, open receivables, unapplied credits | CSV per ledger, plus an aging CSV with due date and bucket | Day one calls, and aging buckets rarely survive an import |
| Vendor master, tax status, year to date payment totals | CSV | You file 1099s from this, not a partial year |
| Leases, signed documents, certificates of insurance | PDF files plus a manifest CSV mapping each file to a unit or expiry date | A document dump with no manifest is unusable |
| Charge schedules, late fee rules, approval chains | CSV where possible, screenshots where not | Configuration, not data, so it rarely exports |
| Open and recent work orders, with attachments | CSV plus a separate file export | Photo attachments are the most common silent loss |
| Resident contacts with consent and preferences | CSV | You cannot lawfully re email people who opted out |
What actually breaks in a property management data export?
Four things break in almost every migration, and all four are predictable.
- Balances that do not tie. Sub ledgers export cleanly, then the general ledger tie out fails because held deposits, prepaid rent, and accruals land in different accounts in the new chart. Import one opening balance journal entry per property, not years of history, and map trust accounting first, since held funds need their own accounts on both sides.
- Attachments. Work order photos, scanned invoices, and signed leases often export as links back into the old system rather than as files. Open one before trusting the batch.
- Configuration and reports. Late fee rules, approval limits, charge schedules, and permission roles are settings, and nobody exports settings. Custom reports do not migrate at all, so every saved report is a rebuild.
- History. Closed work orders, old announcements, and archived messages usually stay behind, so decide in advance what lives in a read only archive.
How long should the parallel run last?
Run both systems in parallel for two full month end closes, not two calendar months. The unit of truth in property accounting is a close, not a date. Cut over mid period and you own half a month in each ledger with no clean tie out for either.
The first close proves the import landed. The second proves the process runs: charges generate, late fees apply, payouts send, statements produce, and the bank reconciles. Our modern month end close walkthrough shows what good looks like.
- Cut over on the first day of a fiscal period. A fiscal year boundary gives the cleanest audit story; a quarter boundary is the usual compromise.
- Agree the read only retention window in writing before notice goes out, and hold it a year past cut over or longer where your state requires it.
Timelines slip when nobody on the vendor side is named and dated. A Manager reviewing Yardi Breeze on Capterra in February 2026 reported that "After 5 months of no go live, the set up was cancelled". Different product, same lesson: put a named implementation lead and dated milestones in the contract before you sign.
What are your go live criteria?
Go live criteria are a short written list of tests that must all pass before cut over, agreed at the start so nobody renegotiates under pressure.
- Trial balance matches the old system's final trial balance to the cent, per property.
- Cash per bank account matches the bank statement, not just the old system.
- Every resident and owner ledger balance matches, and the exception list is empty rather than explained away.
- Total aged receivables and every aging bucket match.
- One charge run produces correct charges for a sample of every unit type.
- One test payment settles end to end, from resident payment through bank deposit to ledger line.
- Every board packet and owner statement report is rebuilt and approved by its signer.
- Residents on one pilot floor have logged in, paid, and filed a maintenance request from their phones.
Who owns which piece of the migration?
Name one person as project owner, because the common failure is that everyone owns the migration and nobody does. Assign the rest by name too.
- Project owner: the dated plan, the vendor relationship, the go or no go call.
- Controller or head of accounting: chart of accounts mapping, opening balances, the trial balance tie out.
- Property manager: unit and lease data, charge schedules, the work order backlog.
- Front desk or concierge lead: visitor, package, and amenity setup, plus desk scripts.
- Board treasurer or owner representative: the report list and board packet contents.
- Vendor implementation lead, named in the contract: import runs, configuration, training, dates.
What do the first 30, 60, and 90 days require?
The first month is extraction, the second is the first parallel close, the third is the second close and cut over.
- Days 1 to 30, extract and map. Pull every export above, screenshot every settings page, and freeze optional configuration changes. Map the old chart of accounts to the new one line by line, with the controller signing each line.
- Days 31 to 60, first parallel close. Import opening balances and open items, then run the month in both systems. Explain every difference in writing, because one you cannot explain is a defect, not rounding. Rebuild your ten most used reports and train staff while the old system still carries the work.
- Days 61 to 90, second close and cut over. Run the second close in both, test payments end to end, and work the go live checklist item by item. Send residents a pre launch letter a week before their credentials arrive, so the first email from the new system is expected. Cut over on day one of a fiscal period and move the old system to read only that day.
- Running several buildings? Stage them. Migrate one end to end, then apply what you learned across the rest of the portfolio.
Where does URBI fit, and what does it not do yet?
URBI onboards buildings by bulk CSV import of units and residents, and that is the honest description of it. There is no live two way sync with an incumbent property management system, so your old platform stays the system of record until cut over. That is what the parallel run is for.
- Onboarding. Units and residents load by CSV, and residents get token based invites with one time password verification and consent capture. Staff and board credentials are provisioned immediately, and concierge training happens before launch day.
- Accounting. URBI Accounting is In Beta. It runs double entry books, a chart of accounts seeded by property type, fund tagging across operating, trust rent, trust deposit, and reserve, and a two way QuickBooks Online sync with URBI as the system of record. If QuickBooks is the problem you are solving, ask to see that sync on a demo.
- AI, stated plainly. HERO is the manager facing AI. It reasons over bank lines that rules and matching did not catch and proposes adjusting entries at close, and a person accepts or changes each one. Arthur is the resident and tenant facing AI on phone, SMS, email, and in app chat.
- Exit terms. URBI is month to month with no service agreement, so the cancellation friction you may be leaving is not recreated on the way in. For the wider picture, see URBI for residential buildings.
Frequently asked questions
How long does switching from AppFolio actually take?
Plan ninety days from the day extraction starts to the day the old system goes read only. That covers a month of extraction and mapping plus two full month end closes run in parallel. Clean data and few custom reports sometimes finish in sixty. Heavy configuration or a thin accounting team means four months and a fiscal year boundary.
Can I switch mid fiscal year without breaking my books?
Yes, if you cut over on the first day of a period and import one opening balance journal entry per property rather than years of history. Mid period cut overs break books because half the month sits in each ledger. Tell your auditor first, and keep the old system's final trial balance as the bridging document.
What happens to my historical data after I leave?
Assume you keep only what you exported while still a paying customer. Negotiate a read only retention window in writing before any termination notice goes out, and store the general ledger, statements, leases, and documents in your own cloud storage. Verify every export opens and reconciles before the account closes, because a file you cannot open is not a record.
Switching from AppFolio is survivable when it is run as a data project, with named owners, two parallel closes, and go live criteria written before anyone feels rushed. To see what URBI's CSV import handles and what it does not, email hello@myurbi.co.
