How to Import Recipes into Mealie from Other Apps

Mealie supports bringing recipes in from other apps, and the documentation lists "Import from other apps" as a first-class feature area alongside installation and usage. The practical routes are a bulk URL import (covered in the community guides) and the migration guide for people moving off an older version. What you can't assume is that every source app has a dedicated one-click importer — for most apps you'll be importing by URL, then cleaning up the result.

What Mealie actually offers for imports

From the documentation structure, the import-relevant entry points are:

• Import from other apps — a top-level feature area in the docs, separate from general usage.
• Bulk URL Import — listed under Community Guides, i.e. a documented workflow rather than a core menu item.
• Version 1 Migration and a Migration Guide — for moving data from an older Mealie version, not from third-party apps.
• Improving Ingredient Parser — a guide that exists precisely because imported ingredient lines often need parsing fixes.

That last point is the honest framing: Mealie's import story is "get the recipe in, then fix the structured fields," not "every source app maps cleanly."

Bulk URL import: the general workflow

The docs describe bulk URL import as a community guide, so treat the exact UI labels as something to confirm in your own instance. The shape of the task is:

1. Collect the source URLs. Export or copy the recipe links from the app you're leaving. If that app has no export, you'll be copying links manually.
2. Feed them to Mealie's bulk import. You provide a list of URLs; Mealie fetches each page and creates a recipe entry from it.
3. Expect partial results. Pages behind a login, JavaScript-only recipe cards, or heavy anti-scraping will fail or come in thin. Re-run or add those manually.
4. Review each imported recipe. Check the ingredient list, quantities, and steps — this is where the ingredient parser guide becomes relevant.

The expected result is a set of draft recipes in your Mealie instance, not a finished library.

Importing from a specific app

The documentation does not enumerate per-app importers in the material available here, so don't plan around a "Import from Paprika/Nextcloud/whatever" button existing. Two things are worth checking before you commit to a method:

• Whether your source app can export to a file format (JSON, HTML, or a URL list). A file export is usually more reliable than scraping.
• Whether your source app's recipes are publicly reachable URLs. Bulk URL import depends on Mealie being able to fetch the page.

If the source app only exports a proprietary archive, the realistic path is exporting it, converting what you can to URLs or a supported format, and importing in batches.

What to check after importing

Imported recipes are the most common source of messy data. Verify:

The "Improving Ingredient Parser" guide exists for the first row — if your imports consistently mis-parse, that's the doc to read rather than fixing every recipe by hand.

Related docs worth reading first

• Installation Checklist — confirm your instance is set up before bulk-importing into it.
• Backup and Restoring — take a backup before a large import so you can roll back a bad batch.
• Migration Guide / Version 1 Migration — only relevant if you're coming from an older Mealie, not from another app.
• API Reference — if you'd rather script the import than use the UI, this is the entry point.

Choosing your approach

• Few recipes, public URLs → bulk URL import, then clean up.
• Many recipes, source app has file export → export first, convert to URLs or a supported format, import in batches.
• Coming from old Mealie → follow the Migration Guide, not the app-import path.
• Recipes behind a login → no documented bulk path; plan on manual entry or a script against the API.