CalcMenu · Migration
Leaving your old system without losing a single recipe
A legacy ERP, a POS back-office nobody supports anymore, a folder of supplier PDFs, or a decade of Excel sheets — we have a migration path built for it. Nothing goes live until someone has checked it.
Book a migration callWherever your data lives today
01
Legacy back-office & POS systems
Old kitchen-management or point-of-sale software, often no longer maintained by its publisher. We export the underlying database directly — no manual re-entry.
02
ERPs & finance systems
Article masters, supplier prices and cost centres held in your ERP. We connect through whatever export or integration layer your IT team is comfortable with.
03
Supplier catalogues — Excel, PDF, EDI
Price lists, technical spec sheets and allergen declarations, in whatever format your suppliers actually send them. Structured or not, we parse it.
04
Paper recipe cards & binders
Photographed or scanned recipe cards. Text and ingredients are read automatically and turned into structured recipes.
How a migration actually works
The same five steps whether we are moving 50 recipes or an entire multi-site estate.
1. Export
We pull the raw data straight from your current system — database tables, spreadsheet exports, PDF spec sheets — without touching the original.
2. Normalise
Units, ingredient names, supplier codes and languages are reconciled into one consistent structure. Duplicates get merged, not multiplied.
3. Stage & validate
Data sits in a staging area first, never live. An automated check catches duplicate codes, orphaned ingredients and missing references before anyone sees it.
4. Pilot
One kitchen or outlet goes live first. Costing, allergens, labels and translations are checked against reality before anyone else moves.
5. Full rollout
Once the pilot is validated, the rest of the sites or brands follow — one at a time, on a schedule your teams control.
Nothing is marked verified unless we can prove it
For allergen and nutrition data especially, a guess is worse than a gap — so we never let one pass as fact.
Confirmed vs. inferred, always labelled
A product is only marked "confirmed" if the allergen data comes from an official source — a supplier spec sheet, a supplier email, a manufacturer's website. Anything guessed from a product name alone stays flagged "inferred," permanently, until someone verifies it.
Raw data never touches production directly
Everything passes through a staging layer first. What goes live has already been checked — not just imported.
Missing data triggers a request, not a guess
When a product has no verifiable source, we draft a request to the supplier automatically, in their language, and track the reply — instead of filling the gap with an assumption.
Two migrations, two very different starting points
Five-star hotel · Zurich
Consolidating allergen and nutrition data across a dozen suppliers
Close to 900 products, with allergen and nutrition data scattered across supplier PDFs, spreadsheets and years of manual notes. We rebuilt a single verified reference file, chased the suppliers who had never sent an official spec sheet, and brought officially-confirmed coverage from a patchwork of partial data to over 85% — with everything still pending clearly flagged, never hidden.
900 products · 12 suppliers · 85%+ officially confirmed
Multi-brand restaurant group · Zurich
Migrating four restaurant brands off a 20-year-old back-office system
Close to 30 locations across four concepts, all running on a legacy system no longer supported by its publisher. We exported the full article and recipe database, normalised years of inconsistent naming and units, and piloted the new system at one location before rolling out brand by brand.
30 locations · 4 brands · piloted before full rollout
What a migration project looks like
Discovery call
We look at what you have today — system, format, size — and scope what a safe migration looks like for you.
Export & staging
Your data is exported and normalised into a staging environment. Nothing is live yet.
Validation & pilot site
One site goes live first. We check costing, allergens and labels against what your team already knows to be true.
Full rollout & handover
The rest of your sites follow on a schedule you control, with your team trained and a support contact in place.
Tell us what you are leaving behind
15 minutes to describe your current system — we'll tell you honestly what the migration looks like.
Book a migration call