Changing who manages an HOA — self-managed to professional, or one management company to another — is usually a manual, records-losing scramble. LotWize's Community Transfer feature turns it into a governed, board-approved, automatically-billed workflow.
Every HOA changes hands eventually. A self-managed board burns out and hires a property management company. A community fires an underperforming PMC and hires a better one. A property management company sells a portfolio, or a board simply outgrows the volunteer model. Whatever the trigger, the transition itself is rarely as clean as the decision that caused it.
Most of the time, a management transfer happens over email and spreadsheets: someone exports a member roster, someone else forwards a folder of PDFs, a check gets cut to close out the old vendor relationship, and three weeks later the new manager is still discovering delinquent accounts nobody flagged during handoff. There is no formal record of who approved the switch, no enforced governance step, and no system tracking what should happen to billing on either side of the transition.
LotWize's Community Transfer workflow exists because this handoff is a governance event, not just a data migration. It replaces the manual scramble with a structured process: a board vote, a receiving management company's formal acceptance, and an automated backend reconciliation that keeps both sides' books straight — without anyone having to remember to do it manually.
A management transition is really three separate problems happening at once, and most software (and most manual processes) only solves one of them.
The governance problem. Deciding to switch management is a board decision, not a unilateral one. In most communities, changing who manages the association's money, contracts, and legal compliance should require the same kind of collective sign-off as approving a special assessment. Email threads and verbal agreement at a board meeting are not documentation — if a homeowner later challenges the transition, there is nothing to point to.
The acceptance problem. A transfer is not final just because a board decided to leave. The receiving party — a property management company, or another PMC's portfolio — has to actually agree to take the community on. Without a formal acceptance step, associations can end up in limbo: the old manager considers the relationship over, the new one hasn't confirmed anything in writing, and nobody is clearly responsible for the association during the gap.
The billing problem. This is the part almost every manual transition gets wrong. A PMC's per-unit billing is calculated across its entire portfolio. When a community joins or leaves, someone has to remember to recalculate both the gaining portfolio's invoice and the losing portfolio's invoice. In practice, this recalculation frequently gets missed for a billing cycle or two — either the new PMC undercharges because the community wasn't added to the count, or the old PMC keeps billing for units it no longer manages.
LotWize's Community Transfer feature is built into the board settings area (for the community initiating a switch) and the PMC portfolio dashboard (for the management company receiving it). The workflow has three stages, and each one is enforced by the system rather than left to trust.
A board member or the community's super admin starts the transfer by naming the destination — either by entering a specific PMC portfolio ID, or by finding one through LotWize's Marketplace, where self-managed boards can browse property management companies already using the platform. Filing the request doesn't complete the transfer. It opens a vote.
The system counts the community's current board members and calculates how many approvals are required for a simple majority — if there are five board members, three approvals move the transfer forward. Each board member who approves is recorded individually, with a timestamp, building an auditable log of who signed off and when. Nobody can approve twice, and the transfer sits in a visible "Pending Board Approval" state — showing the running approval count — until the majority is reached.
This matters most in the situation self-managed boards worry about: a board president or a single officer unilaterally deciding to switch management without the rest of the board's knowledge. The workflow makes that structurally impossible. The transfer simply cannot advance past this stage without documented majority consent.
Once the board clears its vote, the transfer status moves to "Pending PMC Acceptance." At this point the destination management company sees the incoming request on its own transfers dashboard — the requesting community's name, who on the board initiated it, how the board voted, and when. Critically, only a portfolio owner or admin at the receiving company can accept it; a lower-level staff account can't quietly onboard a new client without the right authority signing off internally.
This stage prevents the other common failure mode: a board assumes a new manager has taken over, while the intended management company never formally agreed to anything. Nothing is final until someone with the authority to accept new business at the receiving company explicitly does so.
This is where the workflow earns its keep. The moment the receiving company accepts, three things happen automatically, in the same operation:
If anything in that sequence fails partway — a database write error, a network hiccup — the workflow doesn't leave the community in a broken half-transferred state. It automatically reverts the community's management record back to what it was before, so the transfer either completes cleanly or doesn't happen at all. There's no scenario where a community ends up orphaned mid-transition with neither the old nor new manager clearly on record.
None of this is complicated project management. It's the unglamorous mechanics of a handoff that boards and PMCs otherwise reconstruct by hand every single time — usually while also dealing with the emotional and political weight of "we're firing our management company" or "the board just doesn't want to do this anymore." Removing the manual coordination doesn't just save time; it removes the specific failure points where transitions actually go wrong: unrecorded consent, unclear acceptance, and forgotten billing adjustments.
It also cuts both directions. A community moving from self-managed to professionally managed gets a documented, board-approved paper trail proving the decision was made properly — useful if a homeowner later asks "who approved this?" A property management company gains a portfolio without a manual onboarding scramble on the billing side, and loses one (if a client leaves) without having to remember to stop invoicing for it. And because the same workflow handles PMC-to-PMC transfers, not just self-managed-to-PMC, it works for the situation where a portfolio company changes hands or a community fires one manager to hire another — arguably the highest-friction version of this transition, since two professional operators both have existing systems that need to reconcile.
A management transition is a governance event, not just a data export — it needs a real approval trail, not an email thread.
LotWize requires a documented board majority vote before any transfer can proceed, with each approval timestamped individually.
The receiving management company must formally accept the transfer — only a portfolio owner or admin can do it — so no community ends up "transferred" without the new manager's actual consent.
Acceptance automatically opens a 90-day transition window and resyncs per-unit billing for both the gaining and losing portfolios — no manual invoice adjustment required.
The workflow supports self-managed-to-PMC transfers and PMC-to-PMC transfers alike, and rolls back cleanly if any step fails, so a community is never left in limbo between two managers.
A board member or the association's admin initiates a transfer request naming the new management company. The board then votes — a simple majority of current board members must approve — before the request moves to the receiving management company for formal acceptance. Only once the destination company accepts does the transfer take effect, at which point billing and management records update automatically.
No. LotWize's transfer workflow requires documented approval from a majority of the community's board members before a transfer can advance past its initial "Pending Board Approval" stage. Each board member's approval is timestamped individually, creating an auditable record that the decision was collective rather than unilateral.
When the receiving management company accepts a transfer, LotWize automatically recalculates per-unit billing for both portfolios in the same operation — the gaining portfolio's total updates to include the new community, and the losing portfolio's total (if applicable) updates to remove it. Neither side has to manually notify billing or track the change on a separate spreadsheet.
Yes. As soon as a transfer is accepted, a 90-day transition window opens automatically. This gives both the outgoing and incoming management sides — or the board and the newly hired PMC, in a self-managed-to-professional switch — a defined runway to finish reconciling vendor contracts, records, and final invoices without an informal, untracked deadline.
Yes. The same workflow handles PMC-to-PMC transfers, not just self-managed-to-PMC transitions. This covers cases where a portfolio changes ownership or a community terminates one management company to hire another — the workflow still requires the community's board to approve the move and the new management company to formally accept it.
Considering a management change — in either direction? Start a free LotWize trial to see the Community Transfer workflow alongside board voting, vendor management, and billing tools built for the switch. For the bigger-picture decision behind the switch, read our guides on self-managed HOA vs. management company costs and switching HOA software to LotWize.
LotWize handles violations, resident questions, dues reminders, and meeting packets automatically — so your board gets its time back.
More guides for HOA boards
Property management companies acquiring a competitor's HOA portfolio usually get a CSV manifest, a data room, and two weeks. AI due diligence reads that data the way an analyst would — scoring financial health, maintenance backlog, document quality, and compliance risk before the deal closes.
One property manager has 12 communities and a clean inbox. Another has 9 and is buried in escalations. Portfolio owners rarely see the gap until someone quits. LotWize's staff workload dashboard scores every property manager's caseload and lets owners rebalance it in a few clicks.
Angry communities rarely call before the annual meeting. AI sentiment tracking reads portal messages, appeals, and maintenance requests to surface a rolling mood score per community — so property managers catch trouble before it becomes a board recall.
