Guides
Switching from one meal delivery system to another
Counter-intuitively, migrating from software is often harder than migrating from a spreadsheet. A sheet is ambiguous but readable; another system’s export is precise and shaped for a model that is not yours.
Structured does not mean compatible
Two systems can both model subscriptions and disagree about what a pause is, whether a term extends, how a skipped day is represented, or whether delivered history is editable. An export lands cleanly and means something subtly different.
The mapping work is therefore conceptual rather than technical, and it is best done by someone who understands your operation rather than by whoever runs the import.
Ask before you commit
Can you export everything?
Customers, plans, selections, delivery history and invoices. A system you cannot leave is a system you should be careful entering.
What happens to delivered history?
It is your evidence in any billing dispute. Losing it in a migration is losing the ability to answer questions about the past.
How are terms represented?
The field most likely to be mapped incorrectly, and the one whose error means cooking for people who stopped paying.
What does a pause mean in each system?
Extension or forfeiture. If they differ, some customers will be materially better or worse off after the switch.
Tell customers what changes
If pause semantics or cut-off timing differ between the old system and the new one, some customers will experience a rule change. Discovering it themselves, mid-plan, is how a technical migration becomes a trust problem.
A short message explaining what is changing and when costs nothing and prevents most of the resulting conversations.
Common questions
- Why is switching systems harder than leaving a spreadsheet?
- Because the data is already structured in someone else’s model. A clean export can still mean something subtly different — particularly around pauses, terms and whether history is editable.
- What should I check before signing with any vendor?
- That you can export customers, plans, selections, delivery history and invoices. A system you cannot leave is one to enter cautiously.
- Do customers need to be told about a migration?
- If pause rules or cut-off timing change, yes. Customers discovering a rule change mid-plan turns a technical migration into a trust problem that costs far more than the message would have.
See how this works in practice
The home page walks through the same mechanics against a real admin loaded with a demonstration kitchen: production, packing, routes and the customer side.
Related reading
- GuidesMigrating meal plan customers into new softwareNames and emails move in an afternoon. What takes real time is the two fields that matter most operationally, because in most kitchens they are prose.
- GuidesImplementing meal delivery software without a bad weekThe risk in this migration is not data loss. It is the week where half the operation is in one system and half in another, and nobody is certain which is authoritative.
- GuidesHow to choose meal delivery softwareMost software evaluations start with a feature comparison, which is the wrong end. Start from where your current week breaks, because that is what you are actually buying a fix for.
- SolutionsManaging mid-cycle subscription changes without re-typing themSelling the subscription is the easy part. The work is everything that happens after, when a customer changes something and five downstream systems need to hear about it before Tuesday.