Skip to content

Migrate from Lose It, Cronometer, Waistline

Three community trackers, three different export shapes, one import flow inside NutriTrace. All of them land in the same tables via Settings → Import & Export → Import from another app, with a preview step and per-date conflict policy before anything writes.

For MyFitnessPal specifically, see Migrate from MyFitnessPal; it has enough quirks to earn its own page.

Preview and conflict policy (all three sources)

Every commit goes through POST /api/nutrition-import/preview first (server/routes/nutrition-import.js). The preview returns:

  • Every food and diary row that would be inserted.
  • Per-date grouping so you can see what lands where.
  • Dupe detection against your existing catalog by name and brand.
  • Parse warnings for rows that skipped or transformed.

Only after you confirm does the commit endpoint (POST /api/nutrition-import/commit) actually write. The per-date conflict policy applies at commit time:

  • Skip: leave any date that already has diary data untouched.
  • Merge: add imported rows alongside anything already there.
  • Overwrite: replace whatever is on that date with the imported rows.

The UI groups dates so you can, for example, skip everything before 2024 and overwrite everything after.

Lose It

Lose It (CSV, subscription required to export)

Lose It gates its data export behind Lose It Premium. If you have a paid subscription:

Export from Lose It

  1. Log in to loseit.com on desktop.
  2. Account → Data → Export.
  3. Pick a date range and download the CSV. The export contains foods, exercises, and body measurements as separate CSV files inside a zip.

Lose It's mobile app does not surface the export; use the web app.

Import into NutriTrace

  1. Open Settings → Import & Export → Import from another app.
  2. Pick Lose It (CSV) from the source picker.
  3. Upload the foods CSV first (this brings across your custom Lose It foods into your Local catalog).
  4. Upload the diary CSV. Preview shows the days and rows it would insert.
  5. Pick a conflict policy per date range and Commit.

What survives

  • Foods: name, brand, per-serving macros, serving size, category (mapped to your NutriTrace categories where possible).
  • Diary rows: per-food entries with quantity, unit, meal slot. Lose It's meal slots (Breakfast / Lunch / Dinner / Snacks) map directly to the NutriTrace defaults; if you have renamed your slots, the importer surfaces a slot mapping step.
  • Body measurements: weight, waist, and any custom fields land under Diary → Body Stats on the appropriate dates. Backdated entries are accepted.

What doesn't

  • Recipes: Lose It's recipe export is opaque JSON that lists ingredients as free text without linked food IDs. Re-create high-value recipes manually in NutriTrace's Recipe editor.
  • Photos: no image export from Lose It.

Cronometer

Cronometer (CSV, free)

Cronometer exports for free. No subscription needed.

Export from Cronometer

  1. Log in to cronometer.com on desktop.
  2. Settings → Account → Data → Export Data.
  3. Pick a date range. Cronometer produces one CSV per data type (Servings, Biometrics, Notes, Exercises).
  4. Download.

The mobile app also has an export under Settings → Data, but the desktop export is more thorough.

Import into NutriTrace

  1. Settings → Import & Export → Import from another app.
  2. Pick Cronometer (CSV).
  3. Upload the Servings CSV (the per-food diary rows). Preview, pick a conflict policy, Commit.
  4. Repeat with the Biometrics CSV for weight and body measurements.
  5. Optionally, the Exercises CSV for manual workouts (these land in the activity_log table).

What survives

  • Per-food diary rows with quantity and unit. Cronometer's food catalog is largely USDA-derived; the importer matches against USDA first, then OFF, then your Local foods.
  • Biometrics: weight, body fat, custom fields (any of Cronometer's biometric categories map to Body Stats).
  • Notes: per-day notes land on the day's diary.notes field.
  • Exercises: name, kcal, duration land in activity_log with source='manual_form'.

What doesn't

  • Recipes: Cronometer exports recipes as flat serving lines rather than structured ingredients. Re-create the important ones in NutriTrace's Recipe editor.
  • Custom foods: partial. The Servings export flattens to per-day rows; custom-food metadata (barcode, category, notes) is not fully preserved. Bulk-import your custom foods separately via Settings → Import & Export → Bulk Import if you need them intact.

Waistline

Waistline (JSON, free, open-source)

Waistline is the open-source Android nutrition tracker NutriTrace grew out of (the storage prefix wl_u<id>_<key> is a Waistline holdover, per ARCHITECTURE.md:193). Waistline exports a full JSON backup with foods, meals, recipes, and diary rows all included. This is the highest-fidelity import path of the three on this page.

Export from Waistline

  1. Open Waistline on Android.
  2. Settings → Backup and Restore → Export.
  3. Save the resulting JSON file (typically waistline_backup.json).

Transfer the file to whatever device you are running NutriTrace's browser or Android app from.

Import into NutriTrace

Two entry points, depending on which NutriTrace surface you are on:

  • Web / desktop: Settings → Backup and Restore → Restore Waistline backup. Upload the JSON, preview, commit.
  • Android: same path. On Android in local-only mode, the import runs entirely on-device against the SQLite mirror.

What survives

  • Foods: name, brand, barcode, per-serving and per-100g macros, categories. Photos are not carried over (Waistline stores them separately).
  • Meals: preserved as saved Meals.
  • Recipes: preserved as Recipes with ingredient linkage intact where the source ingredient food is in the export.
  • Diary rows: full per-food rows with quantity, unit, meal slot.
  • Body stats: weight and any custom Waistline fields.

What doesn't

  • Wellness data: Waistline doesn't track it.
  • Water containers: Waistline's water tracking is coarser; NutriTrace's container library will need setting up under Settings → Water.