Machine readability determines whether another service can import an export

What it is

A machine-readable export uses a reliably parseable format with documented field semantics and explicit types, allowing another service to process it without manual transcription. JSON, CSV, and XML are syntax containers only. Unstable identifiers, ambiguous time and units, or relationships flattened into display strings can still defeat migration. Portability also needs semantic interoperability: mapping fields to equivalent objects and relations.

Why it happens

Migration reconstructs structure, order, references, and context as well as values. Proprietary encodings, undocumented enumerations, missing time zones, and detached media metadata can parse while changing meaning. Without schema versioning, an importer breaks as exports evolve. Explicit schemas, stable keys, standard types, and compatibility rules reduce transformation uncertainty; an open file extension alone does not.

Studying it

An independent team can build an importer from public documentation and test fixtures spanning nulls, non-Latin text, time zones, attachments, relations, and large volume. Measures include parse failure, field loss, broken links, unit error, and manual repair time. Schema validation establishes syntax, not preservation of user meaning, so task-level comparison and sampled human reconciliation remain necessary.

Where it stops holding

Services do not always have isomorphic data models, and some semantic loss is unavoidable; retain source values and explanation rather than fabricating a mapping. Common standards may cover core objects while lagging domain-specific capabilities. A human-readable preview remains useful as a companion, not a substitute. Binary media can travel as multiple files organized by a manifest and stable relative references.

Applying it

• Use an open format with explicit encoding, type, and nesting rules, publishing a data dictionary, enumerations, units, time zones, and version policy.
• Preserve stable object identifiers and relations; associate media through a manifest, checksums, and relative paths rather than filenames alone.
• Provide schemas, examples, and validation while evolving versions without silently breaking older importers.
• Have an independent team implement import and round-trip testing, reconciling counts, relations, times, content, and media checksums; repair or explicitly report every loss.

Related

• Same group: O1.12.1 Portability lets users retrieve their data in a structured format · O1.12.3 Derived and inferred data are usually outside portability scope · O1.12.4 Export can become a bulk-exfiltration attack surface
• Adjacent: O2.04 Privacy dashboard · P3.05 Freedom to leave
• Search terms: machine-readable export · semantic interoperability · round-trip testing