Skip to content

Importing and exporting recipes

Move recipe data in controlled batches, keep a backup and review every mapped field before replacing a production workflow.

Updated August 2026

01

Prepare a safe migration

  • Back up the database and uploads before importing.
  • Use a staging website that mirrors the active theme and relevant plugins.
  • Export a small representative sample first, including groups, images, nutrition and unusual units.
  • Document the source plugin and its version.

02

Map fields deliberately

Match title, summary, yield, time fields, ingredient groups, instructions, media and taxonomies to their Plany Recipes equivalents. Do not force unsupported data into a visually similar but semantically different field.

03

Import in a small batch

  1. 1

    Import a handful of recipes and retain their source identifiers.

  2. 2

    Open each recipe in the editor and compare every structured field.

  3. 3

    Review image ownership, file URLs and alternative text.

  4. 4

    Preview mobile, desktop and print output.

  5. 5

    Only expand the batch after the sample passes the same checks.

04

Keep a portable export

Use structured export as an additional portability layer, not as a replacement for full WordPress backups. Store exports with a date and the Plany Recipes version that created them.

Still need help?

Send the affected URL and your WordPress setup to product support.

Contact support