Garage Export Format

Quiver can export your entire garage — bikes, components, rides, service history, component assignments, and attachments — to a single JSON file. You own your data and can take it with you at any time.

To export: open Settings → Export garage. To import on another device or after reinstalling: open Settings → Import garage.

Photos and documents are embedded as base64-encoded data so the file is fully self-contained — no sidecar folders needed.

{
  "format": "quiver-garage",
  "version": 4,
  "exported_at": "2026-05-06T14:30:00.000Z",
  "bikes": [ ... ],
  "rides": [ ... ],
  "setups": [ ... ],
  "componentAssignments": [ ... ],
  "entityAttachments": [ ... ],
  "serviceLogTasks": [ ... ]
}

{
  "id": "stu901",
  "bike_id": "abc123",
  "name": "Race",
  "is_default": 0,
  "display_order": 1,
  "created_at": "2026-05-01T10:00:00.000Z",
  "modified_at": "2026-05-01T10:00:00.000Z"
}

A named configuration for a bike. Each bike has at least one setup (the Default, with is_default: 1). Components are linked to setups via ComponentAssignment.setup_id.

{
  "id": "abc123",
  "name": "Sunday Tarmac",
  "brand": "Specialized",
  "model": "Tarmac SL7",
  "year": 2023,
  "type": "road",
  "catalog_id": 42,
  "frame_material": "carbon",
  "color": "Gloss Tarmac Black",
  "size": "56",
  "purchased_at": "2023-04-01",
  "starting_km": 0,
  "archived": false,
  "active_setup_id": "stu901",
  "image_data": "<base64>",
  "image_mime": "image/jpeg",
  "created_at": "2023-04-01T10:00:00.000Z",
  "modified_at": "2026-05-01T08:22:10.000Z",
  "components": [ ... ]
}

{
  "id": "def456",
  "type_id": "chain",
  "brand": "Shimano",
  "model": "CN-LG500",
  "notes": null,
  "state": "active",
  "installed_at": "2025-01-15",
  "installed_at_km": 12500,
  "interval_km": 3000,
  "design_life_km_override": null,
  "wears_indoors_override": null,
  "service_tools_override": null,
  "service_tasks_override": null,
  "replaced_at": null,
  "replaced_at_km": null,
  "photo_data": null,
  "photo_mime": null,
  "created_at": "2025-01-15T09:00:00.000Z",
  "modified_at": "2025-01-15T09:00:00.000Z",
  "service_log": [ ... ]
}

{
  "id": "ghi789",
  "date": "2025-03-20",
  "km_at_service": 15200,
  "action": "service",
  "action_kind": "chain_hotwax",
  "recurrence_km": 500,
  "notes": "Waxed in Molten Speed Wax",
  "created_at": "2025-03-20T18:00:00.000Z",
  "modified_at": "2025-03-20T18:00:00.000Z"
}

{
  "id": "tsk012",
  "service_log_id": "ghi789",
  "task_id": "chain-degrease",
  "task_title": "Degrease the chain",
  "ordering": 1,
  "checked": 1,
  "note": "needed two passes — chain was filthy",
  "modified_at": "2025-03-20T18:00:00.000Z"
}

One row per checklist task on a service log entry created via the "Service this" flow. Snapshots the task title at the time of service so historical replay still shows what the user actually saw, even if a dictionary task title is later edited.

{
  "id": "jkl012",
  "bike_id": "abc123",
  "date": "2026-04-28",
  "distance_km": 87.4,
  "duration_min": 195,
  "notes": null,
  "setup_id": "stu901",
  "is_indoor": 0,
  "source": "strava",
  "external_id": "12345678901",
  "created_at": "2026-04-28T14:00:00.000Z",
  "modified_at": "2026-04-28T14:00:00.000Z"
}

{
  "id": "mno345",
  "component_id": "def456",
  "bike_id": "abc123",
  "distance_at_assign": 12500,
  "distance_at_unassign": 15200,
  "assigned_at": "2025-01-15",
  "unassigned_at": "2025-06-01",
  "setup_id": "stu901",
  "created_at": "2025-01-15T09:00:00.000Z",
  "modified_at": "2025-06-01T12:00:00.000Z"
}

One row per stint on a bike. A component that has been on two bikes will have two assignment rows. An open assignment (currently installed) has unassigned_at: null and distance_at_unassign: null. With multiple setups, a component can have one open assignment per setup simultaneously.

{
  "id": "pqr678",
  "entity_type": "bike",
  "entity_id": "abc123",
  "mime_type": "image/jpeg",
  "file_base64": "<base64>",
  "created_at": "2026-01-10T08:00:00.000Z",
  "modified_at": "2026-01-10T08:00:00.000Z"
}

A photo or document attached to a bike or component — for example, a purchase receipt or warranty card. The file content is base64-encoded inline; there is no file_path field (paths are device-specific and meaningless across devices).

Importing offers two modes:

• Merge — upserts records. Existing records with the same id are updated; records not present in the file are left untouched. Safe for syncing between devices without losing new data added on the destination.
• Replace all — wipes local data first, then inserts everything from the file. Use when restoring from a backup.

After a successful import, Quiver pushes the imported records to iCloud so they appear on all your devices automatically.