Moving from Buildium to AppFolio

The short answer

Moving from Buildium to AppFolio is a trust-accounting cutover that happens to involve a data transfer, not the other way around. The risk isn't that a few tenant phone numbers fail to import. It's that owner operating balances, security-deposit liabilities and prepayments don't land cleanly in AppFolio's property-based ledgers and Adjusted Cash Balance logic. Get the opening balances and chart-of-accounts mapping wrong, and the bank can still reconcile perfectly while individual owner ledgers are already off.

This checklist covers the accounting work that has to be correct on day one, so owner distributions, management-fee sweeps and the monthly three-way stay compliant through the switch, not just after a cleanup project fixes what went wrong. It's part of our complete guide to property management accounting, and for how Buildium and AppFolio compare on bookkeeping generally, see our hub on bookkeeping that works with AppFolio, Buildium and Yardi.

Quick reference

Why the accounting side of this migration is its own category

Property managers hold other people's money, usually in one or more pooled trust accounts. At any point, the system of record has to be able to prove that the trust bank balance equals the sum of every owner and tenant liability, and that no owner is being paid, or having bills paid, from another owner's funds.

Buildium and AppFolio both support trust accounting, but the mechanics differ in ways that matter during a cutover. Buildium's reconciliation is closer to a traditional statement-to-register match. AppFolio calculates an Adjusted Cash Balance (ACB) upward from every property's ledger, and requires three numbers, the Statement Ending Balance, the Cleared Balance and the ACB, to match exactly before a reconciliation closes, a process AppFolio-focused bookkeeping specialists call the triple tie-out (APM Help). AppFolio also runs automated diagnostics that flag security-deposit mismatches and escrow cash mismatches before they compound, something Buildium's reconciliation tools don't replicate in the same automated form (APM Help). Every transaction in AppFolio also has to be tagged to a property; there's no way to post without one, which is the foundation its trust ledger structure depends on. None of that is optional during a migration: opening balances and chart-of-accounts mapping can't be treated as a simple "import the totals" exercise.

This is also a moment where the industry is actively tightening its own standard. NARPM launched a dedicated Trust Accounting Chart of Accounts Standard at its 2026 Broker/Owner Conference, developed with ProfitCoach and Crane, built as a software-agnostic framework with ready-made codes for specific platforms including Buildium (NARPM). That standard treats client funds as liabilities that must stay identifiable by owner and property throughout, which is exactly the distinction a sloppy migration collapses.

Pre-migration checklist: Buildium side

Do this work while Buildium is still the live system.

1. Freeze a clean cutoff date. The first day of a month or quarter is easiest. Record the exact bank statement ending balance and the corresponding Buildium book balance for every trust, escrow and operating account on that date.

2. Run and archive the critical reports. Buildium's dynamic reporting (Settings > Export Data, and the report screens themselves) supports Balance Sheet, Bank Transactions, Rental Owner Ending Balances, Rental Owner Statement and Trial Balance downloads as xls, csv or pdf. Pull all of these as of the cutoff, plus general ledger detail for the periods you intend to keep as reference and a list of undeposited funds and outstanding checks or ACH. Buildium doesn't offer a single clean export of full line-item financial history; plan on a report-based archive rather than one file.

3. Clear or document every exception. Negative property or owner balances, undeposited funds, unmatched receipts and stale outstanding checks have to be resolved, or explicitly carried forward as documented opening items. These are exactly the items that produce ACB and diagnostic failures after cutover if they're ignored.

4. Map the chart of accounts before anyone imports. Identify the Buildium accounts carrying compliance weight: operating trust cash, escrow or security-deposit cash if separate, security-deposit liability, prepayment or advance-rent liability, owner equity or reserve accounts, and management-fee income. Decide the corresponding AppFolio GL accounts, including whether operating and escrow cash share one bank account and one cash GL, share one bank with two cash GLs, or sit in two separate bank accounts. AppFolio's property-level tagging requirement means the mapping has to preserve traceability, not just totals.

5. Decide historical depth. Most firms bring active leases, current tenant and owner balances, and open payables or receivables. Full multi-year general-ledger history is rarely worth the import risk; keep Buildium in read-only mode as the archive for older detail instead.

Opening-balance and cutover checklist: AppFolio side

AppFolio's onboarding team can help map the chart and load beginning balances, owners, residents and vendors. Treat their work as a draft your own accounting team validates, not a finished product.

1. Enter opening balances by property and owner, not as a single lump sum. Total cash being correct is necessary but not sufficient. Each owner's and property's share of trust cash, security deposits and prepayments has to be correct so AppFolio's property ledgers and ACB start clean.

2. Confirm security-deposit liabilities equal escrow cash. After load, run AppFolio's financial diagnostics and review the security deposit funds section for mismatches. Any gap here is a day-one problem, not something to clean up later.

3. Validate the three-way on the cutoff date. Bank statement ending balance has to equal AppFolio's cleared and book balance, which has to equal the sum of all client ledgers, owners plus security deposits plus prepayments. If those three numbers don't match to the penny, don't go live.

4. Run a parallel period. Keep both systems running for at least one full distribution cycle, often 30 to 60 days. Compare owner statements, distribution totals and the three-way reconciliation between the two before decommissioning Buildium.

5. Take extra care with mid-month cutovers. Transactions posted in Buildium after the starting numbers were already handed to AppFolio have to be re-entered or journaled deliberately. Duplicated or dropped entries are the most common failure mode on a mid-month move.

Worked example: opening balances that look fine until the first distribution

A 180-unit residential portfolio moves from Buildium to AppFolio on October 1. On September 30 the trust bank statement shows $412,800. Buildium's aggregate owner operating balances, plus security-deposit liability, plus prepayments, also total $412,800, so the three-way appears clean.

When the balances load into AppFolio, two mapping decisions get made for speed:

Both decisions get made for speed, and both pass the headline three-way check on cutover day, because the total cash position is unaffected either way.

On October 5 the team runs Pay Owners. AppFolio's Adjusted Cash Balance looks healthy in total. Distributions go out. Two weeks later the first owner calls: their statement shows a lower balance than expected, and a bill that was paid from another property's funds. The security-deposit liability no longer ties to the escrow cash account, because tenant-level detail was never established. The bank still reconciles. The trust accounting does not.

Correct treatment would have meant funding or transferring the three negative balances before cutover, loading security deposits at the tenant and property level so the liability equals the escrow cash, and confirming each owner's ledger against the exact portion of the $412,800 that actually belongs to them. That's the domain-specific failure mode this migration has to prevent.

Questions to ask AppFolio, and your own team, before you sign off

How Numetix works with a Buildium-to-AppFolio migration

We treat the migration as a controlled accounting cutover, not a software project. AI handles transaction matching and categorization; a CPA-overseen finance team maps the chart, validates opening balances by property and owner, clears exceptions before go-live, and runs the first several three-way reconciliations and owner-distribution cycles so the books stay clean while the team learns AppFolio's ACB and diagnostic workflow.

A practical first step: send us your most recent Buildium Balance Sheet, owner and trust balance reports, and a current bank statement for the trust and escrow accounts. We'll show you the exact opening-balance entries and the gaps that would otherwise show up after cutover. Book 30 minutes with our team. More on how Numetix serves property management companies.

Frequently asked questions

Can AppFolio import everything automatically from Buildium? No. AppFolio's onboarding supports mapping and loading key records and beginning balances, but full historical general-ledger detail rarely imports line by line. Plan on a clean cutoff plus a Buildium archive.

What's the single biggest accounting risk in this migration? Loading cash as a portfolio total instead of correctly allocating owner operating balances, security-deposit liabilities and prepayments by property. That produces an immediate three-way or diagnostic failure and can cause distributions that draw on the wrong owner's funds.

Do we need a separate escrow bank account in AppFolio? It depends on state rules and your current practice. AppFolio supports separate Operating Cash and Escrow Cash GL accounts if you run them separately; the configuration has to match your real bank accounts and the liability accounts tracking security deposits.

How long should we run both systems in parallel? At least one full owner-distribution and three-way reconciliation cycle. Many firms keep the parallel period to 30 to 60 days.

What proves the cutover was clean? The bank statement ending balance, AppFolio's cleared and book balance, the sum of all client ledgers, a check that security-deposit liability matches escrow cash, and a sample of owner statements compared to the prior Buildium statements.

Who should sign off on the opening balances? Someone who understands trust accounting and will own the monthly three-way after go-live, not only the operations or onboarding lead.