Kinnetly
A personal CRM export should let you take more than a list of names and email addresses. The useful part is the context around each relationship: notes, introductions, tags, reminders and the history that explains why a person matters.
That context took time to build. You should be able to back it up, restore it and leave with a usable copy if the product no longer suits you.
Portability is a trust test
Moving into a personal CRM asks for a quiet commitment. You add the people you know, tidy their details and record things that would otherwise live in your head. After a few months, the system may hold years of relationship history.
A polished import makes that commitment easy to start. A clean export tells you the commitment remains yours to end.
The OECD describes data portability as a way to give people more control over their data and reduce the cost of switching services. Its report on data portability looks at the wider effect on user choice and competition.
For relationship data, the principle is personal. You may be changing tools, closing an old account or keeping an independent backup. In each case, you need your information in a form you can keep and use.
A contact list is only the outer layer
A basic CSV export can preserve familiar fields such as name, company, email address and phone number. That is useful, especially when you want to open the file in a spreadsheet or import contacts somewhere else.
But a personal CRM usually holds more than address-book data. A proper export should account for the information that gives a relationship meaning:
- notes you have written about the person
- where you met and who introduced you
- tags and group membership
- contact and follow-up history
- reminders or useful dates
- links between people, companies and events
If an export leaves those parts behind, you still have your contacts. You have lost much of the reason you used a personal CRM in the first place.
Before committing to a tool, look for plain answers to three questions. What can I export? Which file formats will I receive? Can I restore the full system, including its relationships?
CSV and JSON do different jobs
There is no single perfect export format. The right one depends on what you need to do next.
CSV is easy to inspect. You can open it in a spreadsheet, check the rows and move standard contact fields between many products. vCard serves a similar purpose for address books and contact apps.
A whole relationship map is more complicated. One person can be linked to a company, an event and the friend who introduced you. Notes, tags and reminders may also have their own structure. Flattening all of that into rows can strip away the connections.
That is where a structured format such as JSON helps. It can preserve different record types and the links between them. You may not want to read the file over coffee, but it is better suited to restoring a connected system.
The strongest setup gives you both: common formats for moving contact details, plus a structured backup for rebuilding the full account.
A backup has to survive the restore
Downloading a file can feel like the job is done. It is not much comfort if the file is incomplete, outdated or impossible to restore.
A recent ACM study of mobile device backups found that backups do not always protect people as well as expected. Among the problems the researchers examined were backups that were missing, stale or difficult to use when they were needed.
You do not need an elaborate disaster-recovery plan for a personal CRM. A small routine is enough:
- Export after a major import or clean-up.
- Keep a dated copy somewhere separate from the service.
- Check that the file opens and contains the records you expect.
- Test the restore process before you depend on it.
- Repeat the export on a schedule that matches how often your network changes.
The restore test matters. It turns a reassuring download button into evidence that you can recover the system.
Check the exit before you move in
Most people review features before choosing software. Export and account closure often get left until later, when switching has already become inconvenient.
Spend five minutes on the exit path first. Look for documentation on exports and backups. Check whether the product offers a machine-readable copy, not only a PDF or screen print. Find out whether deleting the account is separate from downloading its data.
Then consider what would be missing if you left tomorrow. If the answer includes introductions, relationship history or notes you cannot recreate, portability deserves the same attention as search and reminders.
This does not mean you should expect to leave every tool. It means staying should remain a choice.
What Kinnetly lets you take with you
Kinnetly is a private, single-user relationship map. It supports CSV and vCard export for portable contact data, along with a JSON backup and restore for the whole network.
That distinction matters because Kinnetly stores connected information. People can be linked to companies, groups and events. You can record introductions, notes, tags and follow-up reminders. The JSON backup is designed to preserve that wider structure so it can be restored, while CSV and vCard give you common formats for contact data.
Kinnetly also supports CSV and vCard imports, so bringing existing contacts in does not require starting from scratch. Duplicate detection and merge tools help when records overlap after an import.
You should not have to trust a relationship tool because leaving feels too costly. You should trust it because it treats your data as yours.