Before you commit to a personal CRM, try leaving it

The export button is easy to find. You click it, receive a CSV and move on. Months later, when you actually want to switch tools, you discover that the file contains the names but not the part you valued: the notes, the dates, or the conversation behind an introduction.

Test that before your collection becomes important.

This is an exit test you can perform with a few invented records. It does not require cancelling a subscription or moving your real history. Its purpose is to distinguish an available export from an export that serves your particular use.

Decide what must survive

An address book and a relationship history do not have the same minimum useful export. A phone number may be sufficient to contact somebody. It will not explain why you met or what you agreed to send.

Create a sample with the fields that matter to you. Here is the eight-field test record used in this article; the person and details are fictional.

These are test requirements, not a claim that every CRM offers every field. Cross out what you do not need. Add a field that would make your own exit impossible without it.

Distinguish the export types

Apple Contacts provides a useful concrete distinction. Selected records can leave as vCards, while a Contacts Archive is a different backup format. Notes and photos have vCard export settings. Apple also warns that exporting via Numbers includes information excluded by certain vCard or private-card sharing settings. So changing formats can change what you disclose. [1]

That is why the first test should use invented, non-sensitive records. “I just wanted a spreadsheet” is not a good moment to discover that a private note came along.

A product-specific archive may be appropriate for restoration in that product. A broadly readable file may be better for inspection elsewhere. A source link may be readable but useless after an account closes. Record which job each export actually performs.

Do not upload a real address book to an unknown online converter simply to check a format. Use a trusted local reader or your organization’s approved tools.

Some missing fields are documented limits

Mesh’s June 2026 export documentation says it provides CSV output, while some licensed information is excluded. It also restricts a Teams workspace export to an authorized primary account holder or administrator. Those are distinct questions: what data can leave and who may request it. [2]

Dex’s guide points to settings for exports of contacts, notes and network updates. That identifies an available route; it does not establish that another product can recreate every relationship between those records. [3]

These observations are not a head-to-head migration test. We did not export a real customer account, compare complete schemas or verify round-trip fidelity. They explain what to check before interpreting an export claim.

Open the file before importing it

Inspect the smallest unit that matters. Are there separate rows for notes? Are dates clear? Did line breaks survive? Did two email addresses become one unreadable cell? Can you tell the difference between a name and an organization?

Then follow one complete relationship through the file. Find Sofia’s record, the workshop note and the outstanding reading list. If they are separate files, determine which stable identifier connects them. Matching only on a display name is fragile when two people have the same name.

A simple result sheet can use present, readable, connected, missing. Those labels answer different questions. A note can be present but disconnected from its person. A link can be readable but lead to a document you will no longer be permitted to open.

The downloadable exit-test worksheet includes the eight fields, the result labels and a blank record. It contains no vendor data or actual contact information.

Test the return trip in an empty destination

When an approved destination supports the format, import only the sample into a separate empty test area. Check it as a user, not only as a row count. Can you find the person and interpret the note without remembering what the original screen looked like?

Do not test by merging into your primary contact book. That turns an evaluation into a cleanup problem. Do not delete the original records until your intended backup or migration has been validated independently.

If the destination cannot represent a field, choose deliberately: retain a separate readable archive, map the field elsewhere, or accept the loss because it is unimportant. A silent loss is the problem; a documented tradeoff can be reasonable.

Choose around the context you use

Kluro’s value proposition centers on finding relationship context and returning to the underlying conversation. That makes source references and dated context particularly worth evaluating when choosing any tool in this category. The personal CRM overview explains that use case.

Use the eight-field sample to evaluate each candidate’s actual export controls. The comparison is useful when you can recover the context you rely on in an approved place and an intelligible form.

Keep the sample and your result sheet. When the product or your needs change, you can repeat the same check instead of starting from an export button and a guess.