The continuity guarantee

It's yours.
Take it anytime.

Every record your community creates here belongs to your community — exportable in one click, in a format you can actually use, without asking us and without paying to leave.

Read the whole thing

71Record types exported

1Click to take it

7 daysTo download an archive

$0Cost to leave

01Why this page exists

Your Data Is Someone Else's Switching Cost

Ask any board that has tried to change management companies. The minutes are in someone's inbox. The ledger comes back as a PDF. The violation history is "in the system," and the system belongs to the company you're trying to leave. Nobody refuses — the answer is always a quote, a timeline, and a conversation about renewing.

That isn't a support problem. It's the business model: when the manager is the customer, the community's records are the collateral. We sell to the association instead, so the incentive runs the other way — and the only way to prove it is to publish the list rather than the slogan.

Charge you to export your own data
Send the ledger as a PDF and call it a migration
Require your manager's sign-off to release the records
Make you open a ticket and wait on us
Hold an archive over an unpaid invoice
Treat your history as the reason you can't leave

Lock-in only ever protects a bad manager.

02What you get

One Button. One Zip. Everything.

Settings → Your data → Request export. No support ticket, no approval from us, no fee, and no window in which it's unavailable — including while you're in a dispute with your manager, or with us. A large community's archive is built in the background, so you can close the tab.

your-community-export.zip
├── README.txt          plain English, for whoever opens this a year from now
├── manifest.json       what's inside, and what was withheld — with reasons
├── data/               71 files, one per record type, complete rows
├── csv/                members.csv, units.csv, requests.csv, ledger.csv
└── files/              every document and photo you've uploaded (optional)

JSON, not a PDF

Complete rows for all 71 record types — the same structure the software runs on, so another system can actually read it.

Spreadsheets for people

4 CSVs — members, units, requests and a running financial ledger — for the board members who are going to open Excel, not a code editor.

Every document and photo

Optional, because a community's storage can run to hundreds of gigabytes. Checked, and the archive carries the files themselves — not links back to us.

A manifest that admits things

Row counts, the fields blanked for a handover, and every record type deliberately left out with the reason it isn't yours. Machine-readable, so the next system can verify it.

03Two versions

Your Copy, and the One You Hand Over

"Export" means two different things depending on who's asking. Your own archive is everything. The version you hand an incoming management company on day one is the full operational record without the board's private deliberation — because a board's internal discussion isn't part of the community's record, and shouldn't arrive with the new manager's welcome packet.

Everything

record types, verbatim — including your channels, comments, moderation history and every AI action ever taken on your behalf. For your own archive.

Shareable

record types — members, units, finances, delinquency, requests, documents and governance. Safe to hand to a successor on day one.

What the shareable version leaves behind

Channels
Channel membership
Channel messages
Channel mentions
Channel moderation log
Comments
Reactions
Comment reports
Portal activity
Email delivery tracking
Discounts applied
AI credit wallet
AI credit ledger
AI conversations
AI messages
AI action queue
AI context snapshots
AI document index
AI ledger index
AI notice history
Board Room briefings
Board Room sessions
Board Room minutes
Community ledger — in part

Community ledger: Owner-visible entries only. Board-tier entries — personnel, and anything naming one household's standing — stay in the community's own full export.

Per-owner delinquency stays in both versions. Balances, payment status and payment history travel with the handover on purpose. A successor manager who can't see who is behind cannot do the job — an export without it would be a courtesy, not a transition.

04Where the line is

What a Manager Takes, and What Stays

A manager's operating knowledge is theirs. A community's record of itself is the community's. That line is drawn in the schema rather than in a contract clause — which is why we can show you exactly what sits on the other side of it, and why each of these is excluded.

Your management company's

Their billing account and their staff roster belong to the agency and travel with them. Everything they did inside your community — vendors, requests, communications, decisions — stays with you.

Agency billing account
Agency staff roster

The platform's

Catalogs and marketing content that are identical for every customer, plus the bookkeeping of the export mechanism itself. There is nothing of yours in them, and every archive already carries its own manifest.

Pricing catalog
Discount catalog
Marketing page content
Signup waitlist
Export job history

Nobody's to move

Push notification tokens are live credentials tied to one browser on one device. They are useless anywhere else and unsafe to copy, so they are never exported — to you or to anyone.

Device push tokens

05If you leave

Cancelling Ends the Subscription, Not the Ownership

Your records aren't deleted

Cancelling stops the billing. It doesn't touch a single row of your community's history.

Export keeps working for at least 12 months

You don't need an active subscription to take your own data out. The button is still there, and it still runs.

No hostage-taking, ever

A dispute, an unpaid invoice or a renewal conversation is never a reason we sit on your minutes. We'll ask you for the money like anyone else.

Deleting it for good is your call

Permanent deletion happens on request from an admin, confirmed in writing, because it can't be undone. Never on our schedule.

06Not yet

What We Don't Promise Yet

A guarantee is only worth reading if it also says where it stops. Everything above is live today. These are not:

The guided management transition is Phase 4

Today, replacing a management company means an admin promotes a board member, revokes the outgoing manager's access, and takes a shareable export by hand. The wizard that does it as one reviewed operation — with a grace period instead of an instant cut-off, and a permanent audit entry — isn't built yet.

The 12-month window is a commitment, not a countdown

Nothing in the code deletes a cancelled community's records at 12 months or at any other time. In practice you have more than we promise. We would rather promise the smaller number and keep it.

Agency-owned assets aren't a separate scope yet

Templates and playbooks a manager builds inside your community currently come with your export. Until that layer ships, the line above is drawn at the billing account.

It's a snapshot, not a live feed

There's no API or scheduled push to another system. If your community needs one, ask — that's a feature request, not a policy problem.

Ask us the hard question

"What happens to our records if we fire you?" is the question every board should open with, and the one most vendors answer with a brochure. Ours is on this page. Tell us about your community and we'll show you the export running against real data.

A real export of a real community, on a call, start to finish
The full written policy, before you sign anything
An honest answer about what isn't built yet

Fire us and keep everything.

It's a strange thing to advertise. It's also the only version of this promise that means anything — and the reason a good management company has nothing to lose by offering it.

See the platform For property managers

hoaconnect.info · Built in Miami Beach

It's yours.Take it anytime.