Your Yazio history
Bring the log, map the columns
Ask to import and an importer opens right in the chat: pick your export, map the columns, preview what will be added, then confirm. The file is read in your browser — the AI never sees the rows. In clients without in-chat panels, paste your export instead.
Your Yazio history can come across, though you'll do a little of the work. Ask to import and an importer panel opens in the chat: you pick your CSV export, it's parsed in your browser, and you point its columns at date, food, meal, calories, protein, carbs, fat, fiber, total sugar, and caffeine yourself. Four apps' exports — MyFitnessPal, Cronometer, Lose It!, and MacroFactor — are recognised by their column names; Yazio isn't one of them, so expect to set that mapping once. Everything after it is the same: a preview of what will be added, then your confirmation.
The European quirks that defeat most importers are handled. A semicolon-delimited file whose numbers use comma decimals — the shape Excel produces in a German or Austrian locale — is read correctly, instead of the delimiter being mistaken for a decimal point or every macro being scaled by a thousand. The headings the mapper knows aren't English-only either: a German export's Datum, Kalorien, Eiweiss, Kohlenhydrate, Ballaststoffe, Zucker and Koffein are all recognised, and fiber, sugar and caffeine are matched in Spanish, French, Italian and Dutch as well — fibra, sucres, zuccheri, suikers, cafeína, caffeina — so a localised file often arrives part-mapped, leaving you fewer columns to set by hand. Quoted fields, line breaks inside a cell, blank-ish values, and stray totals rows are handled too, and the AI never reads the file, so no number can be mistyped in transit.
Dates and energy are confirmed rather than guessed. A DD/MM/YYYY column is read day-first, and where the values genuinely can't settle it — 05/06 being either May or June — the importer shows its reading beside a row from your own file so you can correct it. If the energy column is in kilojoules it's converted to kilocalories, with the unit shown as a control next to a worked example. Re-importing the same file adds nothing: each row carries a content fingerprint, so repeats come back as already logged as long as your timezone hasn't changed in between.