Move your HOA to hoa.to.
We’ll do the migration.
The biggest reason boards stay on software they've outgrown is fear of switching. So we make it a non-event: your data comes over intact, and we reconcile the numbers to the penny before you go live.
How it works
- 1Send us an exportA CSV/roster export from your current system (or a spreadsheet): units, owners, balances.
- 2We import & mapWe load units, owners, opening balances and documents, and map your chart of accounts.
- 3We reconcileTotals are matched to the penny against your prior system, so nothing is lost.
- 4You go liveInvite residents, turn on payments, and start collecting, usually within days.
What comes over
How your data maps
Most systems export the same handful of tables under different names. This is how each one lands in hoa.to and what we check on the way in.
| From your export | Becomes in hoa.to | What we check |
|---|---|---|
| Unit or lot list, addresses, unit factors or square footage | Units, with the allocation basis used for dues | Unit count matches; allocation factors sum correctly |
| Owner roster, co-owners, tenants, mailing addresses, emails | Owners and residents linked to units, portal invitations | Every unit has a current owner; prior owners kept for history |
| Balances and AR aging as of the cutover date | Opening balances per unit | Total receivable equals the old system to the penny |
| Assessment schedule, late fee and interest policy | Recurring charges and collection rules | Next billing run reproduces the old amounts |
| Chart of accounts, bank and reserve balances | General ledger with operating and reserve funds | Fund balances tie to the last bank reconciliation |
| Governing documents, minutes, policies, insurance | Document library with owner visibility set per file | Public vs owner-only vs board-only visibility reviewed |
| Vendors, open violations, ARC decisions (where exportable) | Vendor list, violation and ARC records with dates | Open items carry their notice dates so cure periods are not reset |
Choosing the cutover date
The safest cutover is the day after a billing run and before the next payment due date. Balances are at their simplest, no assessment is issued twice, and owners see one clean statement from the new system. A fiscal year-end is tidy for the accountant but is also the treasurer's busiest month, so many boards choose a quiet mid-year month and let the year-end close happen in hoa.to with the prior months imported as history. Whatever date you choose, freeze changes in the old system from that day and keep it read-only.
Pre-migration checklist
Vendor-neutral. It applies whether you are leaving a platform or a spreadsheet.
- Export a full data dump from your current system, units, owners, balances, and transaction history, before you cancel anything.
- Confirm how far back your dues and payment history exports; many boards want at least two to three years for audits and owner disputes.
- Get a complete owner and resident directory, including archived or inactive owners and prior owners of record.
- Check what's required to reconnect (or replace) your bank and payment processor, new account and routing setup can take longer than the software migration itself.
- Migrate governing documents, meeting minutes, and any signed forms or e-signatures, not just financial records.
- Review your state or provincial notice-period requirements before announcing a new system to owners; switching software doesn't reset those timelines.
- Reconcile opening balances between the old and new system to the penny before go-live, and keep read-only access to the old system through a transition period.
- Time the cutover around your billing cycle so dues aren't invoiced twice, or missed, during the switch.
What can go wrong, and how we avoid it
- • Balances that do not tie. Usually a payment posted in the old system after the export. We re-pull the balance file on the cutover date and reconcile again.
- • Owners invited before the data is right. We keep the portal invitation step until after reconciliation is signed off by the board.
- • Autopay gaps. Bank and card autopay do not transfer between processors. Owners re-enrol in the new portal; we tell them once, with a deadline before the next due date.
- • Reset cure periods. Open violations are imported with their original notice dates so the statutory clock is unchanged.
- • Lost history. Documents, minutes and prior-owner records are imported, not just the current roster.
Frequently asked questions
How long does a migration usually take?
It depends on the size of your community and how clean your current export is, but most self-managed associations are live within days of sending a complete export, not weeks.
What if our current system won't export everything?
We import what's exportable, most systems support at least units, owners and balances, and work with you on anything that has to be entered manually, like older violation history some platforms don't let you export.
Do we lose access to our old system during the switch?
No. You can keep read-only access to your prior system through the transition, which is good practice for any migration regardless of which platform you're leaving.
Who reconciles the opening balances?
We match the imported balances against your prior system's records line by line before you go live, so the totals tie out to the penny before residents see anything.
Can we import ourselves?
Yes. The setup area accepts spreadsheet uploads for units and owners, and you can go at your own pace. Most boards send us the export instead and review the result.
Do statutory notice periods change when we switch?
No. Meeting notices, records deadlines and cure periods run on the statute and your governing documents, not on your software. Time the announcement of the new portal separately from any legally required notice.
Ready to switch?
Get started for free and import at your own pace, or email us your export and we'll handle the migration for you.