The buyer decision
Judge vendor export fit by record scope and attachment behavior, excluding migration engineering and cost or lock-in economics.
Criteria & methodologyA product offering CSV export has established only part of the buyer’s portability requirement. Rows may omit relationships, comments or attached files needed to interpret the record outside the application.
Specify the export outcome before evaluating vendors. This guide concerns product fit, not building a migration pipeline or calculating replacement costs.
Define the record that must leave the product
| Requirement | Evidence to request |
|---|---|
| Relevant entities | Which record types are included? |
| Stable identity | Can exported records be distinguished? |
| Relationships | How are references to other records represented? |
| Attachments | Files, links or another delivery mechanism? |
| Date and status context | Can a later reader interpret the values? |
Do not assume every item is required. The buyer should identify what matters for its intended downstream use.
A documented attachment distinction
Airtable documents attachment fields, explaining that CSV exports represent attachments as URLs rather than the files themselves.
Its attachment URL behavior guide recommends downloading files from exported links before those links expire. That is a concrete reason to distinguish a list of attachment links from a self-contained file export.
This example does not establish the full export scope of every Airtable configuration or imply that every product behaves the same way. Ask for current documentation covering the actual records and offered edition.
Evaluate the package a reader receives
Use harmless sample records with an attachment and a relationship to another record. Generate the proposed export and ask a person unfamiliar with the application to identify the record and retrieve the supporting file.
Inspect what is absent and what still depends on access to the original product. If files are represented by temporary links, record the required handling and whether that satisfies the buyer’s intended use.
A supplier saying that all data is exportable should be supported by the relevant scope, format and practical artifact. The publication has not run this evaluation.
Choose with export limits visible
A simple row export may be sufficient for a narrow reporting need. A buyer needing complete attachments and relationship context should require a stronger demonstrated package.
Do not infer legal retention sufficiency, security effectiveness or migration success from an export button. Those are separate judgments.
Browse the Buying Evidence hub and demo evidence scorecard for recording the requirement and evidence.