Rows without surprises.
Preserve identifiers, quoting, nulls, and field meaning when structured data becomes a spreadsheet export.
Journal collection
Data formats.
Keep the meaning intact at every handoff.
Focused reading from the Extraction Journal. Start with the guide that matches the next decision in your workflow.
3 COMPLETE ARTICLESJSON, CSV, and SQL-oriented exports solve different parts of the delivery problem. These articles explain how to choose a record shape, preserve identifiers, handle nulls, and test the receiving system. Start with JSON when the record contains relationships and nested fields. Read the CSV guide when a person or spreadsheet will consume a flat export, and the SQL guide when the source is a controlled database query. The format is not a quality guarantee: all three need a defined schema, a stable identity, and checks against the source. Review the transformation between formats as a separate stage so that convenient presentation choices do not silently change canonical data.
Structure is only the start.
Make absence, precision, relationships, evidence, and schema changes explicit in your JSON contract.
Query narrowly. Export clearly.
Design read-only datasets, stable continuation, snapshot semantics, and recovery at the database boundary.