Migrate your recipes to Savvy
Paprika, Mela, AnyList, Notion, a spreadsheet. Whatever you’ve been keeping your recipes in, there’s a route into Savvy that doesn’t involve retyping a single one. Pick your app below for the step-by-step.
Three steps, and your own assistant does the hard one.
Get your recipes out of the app you’re in
Every app has a way out. Most hand you a file; your app’s page below says exactly which menu and what comes out of it.Hand the file to an AI assistant with the prompt
ChatGPT, Claude, Gemini — whichever one you use, and a free account will do. It reads your export and writes it out in the shape Savvy reads. Each app’s page carries its own prompt.Paste what comes back into Savvy
The whole library arrives as one job, not one job per recipe. Two hundred recipes take about as long as one.
Savvy publishes a prompt rather than an importer for each app. That’s the same way the cookbook toolkit already works, and it’s why five apps cost roughly what one would.
Every app, its own route.
Paprika
Export your library as HTML, hand it to an AI assistant with the prompt, and paste the result in. Nothing retyped.
Mela
Export Mela’s own recipe file, unzip it, and convert it the same way. Your ingredient headings survive the trip.
AnyList
AnyList has no bulk export, so this one’s different: print your recipes to PDF and Savvy reads them directly. Slower, and honestly so.
Notion
Export your database as Markdown & CSV and convert it, whatever shape your pages are in. Your own columns are matched by meaning.
A spreadsheet
Save it as CSV — columns in any order, names of your own choosing — and let the conversion sort them out. Nothing to unpack.
Somewhere else? The prompt doesn’t care much what it’s handed, so anything readable is worth trying — start from the app above that’s closest to yours. If your app isn’t here and the export defeats it, write to me.
Savvy exports your archive in the format it imports.
Open Settings, go to General, and under Appearance there’s a row called Export archive with a Download JSON button on it. Press it. That’s the whole procedure — what lands is one JSON file, named for the day you asked for it. Free on every plan, including the free one, and there’s no version of Savvy where that button goes away.
What’s in the file
Every recipe you own, in the units it’s stored in. Its cover and its photos. Its meal type, its cuisine, the collection it sat in, and the links between recipes that reference each other. Your own cook log, with the pictures you took.
The file reads back into Savvy
One format, both directions, so the file you take out can also seed someone else’s collection.
Your numbers survive the trip
Quantities come out as they went in. Export, re-import, export again, and you get the same figures back — not a recipe that has drifted through two unit conversions.
Only your own cook notes come out
On a recipe you share with other people, theirs stay behind.
Images travel as links rather than as bundled files, so an export is a portable copy of a live archive rather than a cold backup on a shelf. It’s worth knowing which one you’re holding.