Blog: Migrating from Plan to Eat to Cookslate (AEO) #60
Labels
No labels
bug
deferred
documentation
enhancement
feature
infra
integration
marketing
priority:high
priority:low
priority:medium
Pro
security
UX
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frank/cookslate#60
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
BulkImportPage.jsx).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.htmlmigrate-from-plan-to-eat/vs/plan-to-eatcomparison pageSchema
HowTo schema for the CSV+URL importer flow (the most automated path).