Switch apps. Keep your history. The AI picks up where you left off.
Years of Hevy, Strong, or Fitbod logs shouldn't die in an export folder. Drop your CSV in Arvo's chat and your completed workouts come across — deduplicated, unit-converted, RPE mapped to RIR. Got a coach's program on paper or PDF instead? Import that too, and it becomes your active split.
TL;DR: Switching to Arvo in 3 steps: export your CSV from Hevy, Strong, or Fitbod → attach it in Arvo's chat (auto-detect, duplicate-safe) → the AI anchors your next targets on your real history instead of a cold start. Coach's plan on PDF, photo, or text? One attachment makes it your active split.
Three Steps, About a Minute
No spreadsheet surgery, no manual re-entry. The chat is the import surface.
Export your CSV
Hevy: Settings → Export Data (emailed CSV/TSV). Strong: Profile → Export Workouts → CSV. Fitbod: export WorkoutExport.csv from settings. Save the file to your phone or cloud drive.
Attach it in Arvo's chat
Tap the paperclip, pick the file, send. No caption needed — the parser detects the format from the header row and rejects nothing it recognizes. Chat reads CSVs up to about 2 MB; for bigger exports use the in-app import, which takes files up to 10 MB.
The AI continues your progression
Imported sessions land as completed workouts. The progression engine reads your last 60 days of working sets per exercise — historical max, average, most recent sets — so your first Arvo workout starts from your real numbers, not a cold-start guess.
What Each Import Actually Does
One parser, three formats, auto-detected from the header row. Here is precisely what happens to your file.
Hevy
Settings → Export Data
Reads CSV and TSV (delimiter auto-sniffed). Weight column in kg or lbs, converted to your Arvo unit. Set labels mapped: normal → working, warmup kept, drop sets imported as working sets, failure sets become RIR 0. RPE converts to RIR (10 − RPE). Localized dates parse in English, Italian, Spanish, French, German, and Portuguese.
Strong
Profile → Export Workouts → CSV
Handles both the older and newer Strong column layouts (Duration vs. Workout Duration). Weight-unit column respected, RPE → RIR conversion, per-set notes and workout notes preserved, workout durations parsed from formats like '1h 12m'.
Fitbod
WorkoutExport.csv
Fitbod exports one row per set. Arvo groups rows into workouts by their shared timestamp, keeps isWarmup flags as warm-up sets, sums per-set durations into a session duration, and reads the weight column in kg or lbs depending on your export.
Dedup and re-import safety
Every workout is checked against your existing history by start time (one-minute tolerance) plus workout name. Already-imported sessions are skipped and counted in the summary — so re-importing a fresh export each month just appends the new sessions.
Bring Your Coach's Plan — From Paper to Active Split
The migration path almost no other app has: the program your PT wrote — on paper, in a PDF, in a WhatsApp screenshot — becomes the split Arvo trains you on.
Attach or paste
Photo, screenshot, PDF, Word or Excel file in the chat — or paste the program as plain text. Handwritten pages work; the vision AI reads them in any language.
AI extracts the structure
Days, session names, exercises, sets, reps, rest times, and notes are extracted with a confidence score. Unreadable parts are flagged honestly — the AI never invents exercises to fill gaps.
Preview in chat
An import card shows the parsed plan inside the conversation. Check the days and exercises, then confirm or cancel right on the card.
It becomes your active split
On confirm, your previous plan is archived and the imported one activates. Your coach's exact exercise list is preserved in the workouts Arvo generates — the AI adds targets and progression on top, it doesn't rewrite the program.
Plan import from photo/PDF uses AI vision and has a monthly allowance that scales with your plan. Pasting the plan as text works too.
What Does Not Come Across
An honest migration page lists the gaps. Here they are.
Routines and templates
CSV import brings your completed history, not your saved routines. To carry a program over, use the document import — that path exists precisely for plans.
Media and social
Photos, videos, likes, and comments aren't in the source CSVs, so they can't follow you. Your numbers travel; your feed doesn't.
Exercise names stay verbatim
Names are imported exactly as exported. Names that exactly match your Arvo exercises merge into the same history automatically; any other name stays as-is until you rename it, and until then its history won't merge with the matching Arvo exercise.
Strong sets carry no set-type label
Strong's CSV doesn't distinguish warm-up from working sets. Imported Strong sets appear fully in your history and charts, but the set-by-set progression engine anchors on labeled working sets — which Hevy and Fitbod exports provide.
Frequently Asked Questions
How do I switch from Hevy to Arvo?
Three steps. 1) In Hevy, open Settings → Export Data — Hevy emails you a CSV (or TSV on some plans; Arvo reads both). 2) Open Arvo's chat and attach the file. 3) The parser auto-detects the Hevy format from the header row and imports your completed workouts and sets. Duplicates are skipped automatically, so the whole move typically takes about a minute.
Can I import my Strong workout history?
Yes. In Strong, open Profile → Export Workouts and pick CSV, then attach the file in Arvo's chat. Arvo detects both the older and the newer Strong column layouts automatically, respects the weight-unit column, converts RPE to RIR (RIR = 10 − RPE), and keeps your set notes and workout notes.
Does Arvo import Fitbod data?
Yes. Attach Fitbod's WorkoutExport.csv in chat. Fitbod exports one row per set, so Arvo groups rows into workouts by their shared timestamp, keeps warm-up flags as warm-up sets, and sums the per-set durations into a session duration. The weight column is read in kg or lbs depending on your Fitbod export.
Can I import my coach's training plan from a PDF or photo?
Yes — this is Arvo's near-unique migration path. Attach a photo, screenshot, PDF, Word or Excel file of your program in chat, or paste the plan as text. A vision AI extracts the split structure — days, exercises, sets, reps, rest — even from handwritten pages, and shows a preview card in chat. When you confirm, the plan becomes your active split and your coach's exact exercise list is preserved in the workouts Arvo generates.
Will the AI continue my progression from imported history?
Yes. Arvo's progression engine reads your last 60 days of working sets per exercise — historical max, average, and your most recent sets — to anchor the next target weight and rep range. Imported Hevy and Fitbod sets carry working/warm-up labels and feed this engine directly; Strong CSVs don't label set types, so those sets appear in your history and charts while set-by-set suggestions anchor on labeled working sets.
What does NOT get imported?
Routines and templates from Hevy, Strong, or Fitbod are not imported — only your completed workout history. If you want to bring a program, use the document import instead (photo, PDF, text). Photos, videos, likes, and comments don't travel either — they aren't in the source CSVs. Exercise names are kept exactly as exported: names that exactly match your Arvo exercises merge automatically; the others stay in your history as-is and can be renamed.
Is the import free?
CSV history import is free on every plan — no subscription needed to bring your data across. In chat, CSVs are read up to about 2 MB; larger exports go through the in-app import, which takes files up to 10 MB. The plan-from-photo import uses AI vision and has a monthly allowance that depends on your plan tier.
What happens if I import the same CSV twice?
Nothing breaks. Arvo deduplicates by workout start time (with one-minute tolerance) plus workout name, so already-imported sessions are skipped and reported in the summary. Duplicates inside the same file are caught too. Re-importing a newer export only adds the workouts you logged since the last import.
