Blog: Migrating from Plan to Eat to Cookslate (AEO) #60

Open
opened 2026-05-04 11:49:27 +00:00 by frank · 0 comments
Owner

Write a Plan to Eat → Cookslate migration guide. Note: Plan to Eat does NOT offer a native export, so this guide must walk users through the practical workarounds.

Approach

Plan to Eat lacks a one-click export. Document the realistic options:

  1. Per-recipe CSV — Plan to Eat's account page exports a CSV of recipe titles + URLs; we can feed those URLs into Cookslate's bulk URL importer (existing feature, see BulkImportPage.jsx).
  2. Browser scraping — for recipes Plan to Eat hosts internally (no source URL), users would need to copy-paste manually. Be honest about this.
  3. Their unofficial API — Plan to Eat has a JSON API behind their app. Mention it as a developer option but don't assume readers will use it.

Tone

Empathetic — Plan to Eat refugees are usually fed up with subscription pricing or wanting to self-host. Don't sugarcoat that the migration is harder than from Paprika.

Files

  • cookslate-server/src/html/blog-migrate-from-plan-to-eat.html
  • Register slug migrate-from-plan-to-eat
  • Cross-link from /vs/plan-to-eat comparison page

Schema

HowTo schema for the CSV+URL importer flow (the most automated path).

Write a Plan to Eat → Cookslate migration guide. Note: Plan to Eat does NOT offer a native export, so this guide must walk users through the practical workarounds. ## Approach Plan to Eat lacks a one-click export. Document the realistic options: 1. **Per-recipe CSV** — Plan to Eat's account page exports a CSV of recipe titles + URLs; we can feed those URLs into Cookslate's bulk URL importer (existing feature, see `BulkImportPage.jsx`). 2. **Browser scraping** — for recipes Plan to Eat hosts internally (no source URL), users would need to copy-paste manually. Be honest about this. 3. **Their unofficial API** — Plan to Eat has a JSON API behind their app. Mention it as a developer option but don't assume readers will use it. ## Tone Empathetic — Plan to Eat refugees are usually fed up with subscription pricing or wanting to self-host. Don't sugarcoat that the migration is harder than from Paprika. ## Files - `cookslate-server/src/html/blog-migrate-from-plan-to-eat.html` - Register slug `migrate-from-plan-to-eat` - Cross-link from `/vs/plan-to-eat` comparison page ## Schema HowTo schema for the CSV+URL importer flow (the most automated path).
Sign in to join this conversation.
No description provided.