If you left your platform tomorrow, what would actually leave with you?
Data ownership is not just a clause in the terms of service. It is whether you know exactly which records can leave, in what shape, and how you would check nothing important was lost.
Many brokerages have someone who runs the business out of the CRM in a way nobody else fully understands. Custom fields with meanings that live in one person's head, notes going back years, a pipeline structure that encodes how this market actually works. Ask what would happen if the platform changed or the relationship ended and the room tends to go quiet. The data may technically belong to the brokerage. Whether it would still be usable somewhere else is a different question.
Ownership is measured at the exit
Plenty of platforms say you own your data. The more useful question is what owning it means on the day you decide to go. A few questions separate real portability from a legal technicality:
- Which objects export, exactly—contacts, notes, tasks, appointments, deals, message history, files—and which do not?
- Is the export structured and documented, or a pile of files you would need to reassemble by hand?
- Can an ordinary admin run it, or does it require a support ticket?
- Are relationships preserved—which contact belonged to which agent, which people were on which deal?
- Are there commercial terms, fees, notice periods or retention rules that affect when and how you can export or delete?
Check the move, not just the file
An export is only as good as the migration it supports. Before relying on one, it is worth running the checks a careful operator would: compare record counts before and after, spot-check a handful of contacts with long histories, confirm that notes and dates came across intact, look for duplicates, and keep the old system available until the new one has been reviewed. Those checks apply in both directions—moving in and moving out.
Why lock-in hides in the details
Lock-in rarely announces itself. It tends to arrive as friction: exports that omit the context that made the records valuable, formats only a developer could love, histories that never leave the system. Each sounds minor. Together they can mean the switching cost is not the subscription you are leaving—it is years of operational memory held in a shape you did not choose.
A brokerage that cannot leave a platform cleanly does not fully own its operation. It rents it.
The standard we are setting for ourselves
Revybr includes imports and exports, and we are not going to promise that every record moves losslessly—no honest platform can. What we commit to is narrower and checkable: being clear about which objects can be imported and exported, what each contains, and what is not covered, so you can review it against your own data and run the checks above before planning a switch. A platform should earn your business continuously rather than hold it structurally. Portability also pairs with honesty about what software can promise, which we take up in why compliance support is not a compliance guarantee.