How moving works
Almost every recipe app can make an export: a file with all your recipes. Pick that file in Savour under “From another recipe app”. Savour recognises which app it came from by itself.
Apps with their own import
Each app has a page on how to make the export:
- Paprika: .paprikarecipes and .paprikarecipe
- Mela: .melarecipes and .melarecipe
- Mealie: .zip with JSON
- Tandoor: .json or .zip
- Recipe Keeper: .zip
- Copy Me That: .zip with HTML
- Crouton: .zip with .crumb
- MasterCook: .mx2 and .mxp
- Cookmate: .mcb
- Living Cookbook: .fdx and .fdxz
- Evernote: .enex
- Google Keep: .zip from Google Takeout
- Flavorish: .zip
- CookBookManager: .zip with .yml
- Plan to Eat: .csv
- Pepperplate: no export file
Your app is not listed?
Check whether your app can export as CSV, HTML, JSON (schema.org), Word, PDF or text; Savour almost always reads those. See Excel and CSV, JSON and schema.org and Text files. If it doesn’t work, get in touch and send a sample of your export.
Cancelling your old app
Keep your old app next to Savour for a while until you have checked everything. Keep the export file as a backup.
Comparing
Still deciding? Savour vs Paprika, Meez and Galley lists the differences and who each app is for.
Importing into Savour
Then in Savour:
- Choose “Add recipe” in the menu and then “Import recipe”.
- Choose “From another recipe app” and pick the export file. There is no need to unzip a zip first.
- Choose “Process”. Savour reads all recipes from the file.
- Check the recipes in the review screen and choose “Save all recipes”.
Category
The category: if a keyword of one of your categories appears in the recipe name, Savour picks that one. Otherwise Savour uses the app’s category if you have a category with exactly that name, and if not, “My recipes”. You change it per recipe in the review screen.
Import recipes from Paprika
What you need
An export from Paprika: a .paprikarecipes file (all recipes) or a .paprikarecipe file (one recipe).
Exporting from Paprika
In Paprika, select the recipes you want to take along (or all) and choose Export. Choose “Paprika Recipe Format” as the format. On a computer Export is in the File menu; on a phone or tablet in the share menu. The exact place differs per version.
What comes across
Savour takes over: the name, ingredients, method, yield (servings), notes (at the end of the method) and the recipe photo.
As HTML too
If you exported from Paprika as HTML, you can pick those files or the zip as well; Savour reads the recipes from the HTML.
Import recipes from Mela
What you need
An export from Mela: a .melarecipes archive (several recipes) or a .melarecipe file (one recipe).
Exporting from Mela
On a Mac, right-click “All” in Mela’s left-hand menu and choose to export all recipes. Choose where to save the .melarecipes archive. Export a smaller selection the same way from another category, such as Favourites. Share a single recipe as .melarecipe.
What comes across
Savour takes over: the name, ingredients, method, yield, notes and the first photo. Headings in your ingredients or method (“# Sauce”) become parts of the recipe, such as “Sauce:”.
Import recipes from Mealie
What you need
An export from Mealie: an export of your recipes as JSON, on its own or in a .zip.
Exporting from Mealie
Export your recipes from Mealie as JSON. Depending on your version you find this under exporting recipes or under data management. You get a .json file or a .zip with JSON files.
What comes across
Savour takes over: the name, ingredients (also when quantity, unit, food and note are stored separately), method, yield and notes.
Import recipes from Tandoor
What you need
An export from Tandoor: an export as .json, or a .zip with JSON files.
Exporting from Tandoor
Open the settings in Tandoor and choose Export. Choose an export type with recipes as JSON in schema.org form, choose “All recipes” or a selection and download the file when it is ready.
What comes across
Savour takes over: the name, ingredients, method (including steps), yield and notes. Photos are not part of such an export.
Import recipes from Recipe Keeper
What you need
An export from Recipe Keeper: the .zip file Recipe Keeper makes when you export.
Exporting from Recipe Keeper
In Recipe Keeper, choose the export of your recipes in the settings. You get a .zip file. Don’t unzip it.
What comes across
Savour takes over: the name, ingredients, method, yield, category and notes, as they are in the export.
Import recipes from Copy Me That
What you need
An export from Copy Me That: a .zip export with the HTML option.
Exporting from Copy Me That
In Copy Me That, choose the export of your recipes in your account and pick the “HTML” option. You get a .zip file.
What comes across
Savour takes over: the name, ingredients, method, yield and notes. If a recipe is not in a structured form in the HTML, the Savour reader reads the text.
Import recipes from Crouton
What you need
An export from Crouton: a .zip of .crumb files, or a single .crumb file.
Exporting from Crouton
Open Crouton on iOS or macOS and go to the settings. Choose the export of your recipes (the exact name differs per version). You get a .zip with a .crumb file per recipe.
What comes across
Savour takes over: the name, ingredients with quantity and unit, method, yield and notes.
Import recipes from MasterCook
What you need
An export from MasterCook: an .mx2 file (MasterCook XML) or an .mxp file.
Exporting from MasterCook
Open the cookbook in MasterCook and choose File → Export. Choose MasterCook (.mx2) or the older text export (.mxp) as the format.
What comes across
Savour takes over: the name, ingredients with quantity and unit, method, servings and notes. The Savour reader reads an .mxp file as text; check those recipes a little more closely.
Import recipes from Cookmate
What you need
An export from Cookmate: an .mcb file, the export from Cookmate (formerly My Cookbook).
Exporting from Cookmate
In Cookmate, choose the export or backup of your recipes. Save the .mcb file on your phone or computer; Savour reads it without unpacking.
What comes across
Savour takes over: the name, ingredients, method, yield, comments (at the end of the method) and the photo if it is in the export.
Import recipes from Living Cookbook
What you need
An export from Living Cookbook: an .fdx or .fdxz file.
Exporting from Living Cookbook
In Living Cookbook, export your cookbook or recipes in the FDX or FDXZ format (FDXZ is a compressed version with photos). Savour cannot read an .lcb file (the cookbook database itself).
What comes across
Savour takes over: the name, ingredients with quantity and unit, method steps, servings, comments, tips and the photo.
Import recipes from Evernote
What you need
An export from Evernote: an .enex file with your recipe notes.
Exporting from Evernote
In Evernote, select the notes with your recipes (or a whole notebook) and choose File → Export Notes. Choose the .enex format and save the file.
What comes across
Each note becomes one recipe, with the note title as the recipe name. The Savour reader reads the text: ingredients, method and yield. Notes without ingredients or method (a list, for example) are marked for review so you can remove them easily in the review screen. Tags and attachments don’t come across.
Import recipes from Google Keep
What you need
An export from Google Keep: a .zip from Google Takeout with your Keep notes.
Exporting from Google Keep
Go to Google Takeout (takeout.google.com), select only “Keep” and create the export. Download the .zip when Google tells you it is ready.
What comes across
Each note becomes one recipe, with the note title as the recipe name; the date above it is left out. Checklists become one line per item. Notes without a method (a shopping list, for example) are marked for review so you can remove them in the review screen.
Import recipes from Flavorish
What you need
An export from Flavorish: the .zip file Flavorish makes when you export.
Exporting from Flavorish
Open the Account tab in Flavorish. Under “Import & Export” choose to export your recipes. You get a .zip with your recipes and photos.
What comes across
Savour takes over: the name, ingredients and method in the right order, headings as parts of the recipe, servings, notes and the photo.
Import recipes from CookBookManager
What you need
An export from CookBookManager: the YAML export from CookBookManager.com: a .zip with one .yml file per recipe.
Exporting from CookBookManager
On CookBookManager.com choose the export of your recipes and pick the YAML format. Save the .zip.
What comes across
Savour takes over: the name, ingredients, method, servings, notes (with a video link if there is one) and the first tag as category. An ingredient line ending in a colon becomes a part of the recipe.
Import recipes from Plan to Eat
What you need
An export from Plan to Eat: a .csv export of your recipes.
Exporting from Plan to Eat
In Plan to Eat, choose the export of your recipes as CSV in your settings and download the file.
What comes across
Savour reads the columns for title, ingredients, method, servings and notes. How Savour recognises columns is in Excel and CSV.
Moving recipes from Pepperplate
Why there is no dedicated import
Pepperplate does not make an export file with structured recipes. Other apps fetch recipes by logging in with your Pepperplate password. Savour deliberately doesn’t: Savour never asks for your password to another service.
Recipes from websites
If a recipe originally came from a website, import it again with the link: see Recipe from a website.
Your own recipes
Open the recipe in Pepperplate, copy the text and paste it under Enter text. You can paste several recipes in a row; leave a blank line between them.
Many recipes
With hundreds of recipes and no time to copy them, the import service moves them over for you.