Data portability
Your restaurant data is yours. Migration planning includes export expectations up front, and MarginKind keeps portability part of the operating conversation instead of a renewal surprise.
Migration guide
Switching from TouchBistro to MarginKind
Treat the switch as a chance to connect FOH service patterns with recipe, inventory, labor, and owner reporting before opening the new system to the team.
Import-led path
Move the menu before you move service
TouchBistro migrations are a structured rebuild today. Automated TouchBistro import is roadmap-tagged, while exported menus and reports can still drive the staged review process.
Capability tag: shipped for Toast/Square import and AI recipe-generation during import; roadmap for automated imports from other vendors.
Step 1
Document FOH workflows
Capture table, coursing, modifier, staff, reservation, and reporting patterns that managers rely on during service.
- Export menu and modifiers
- Capture table and coursing rules
- List add-ons in active use
Step 2
Connect margin workflows
Map sellable items into recipe, stock, labor, and reporting structures before training service staff.
- Attach recipes to top sellers
- Configure inventory units
- Map labor permissions
Step 3
Run FOH and BOH rehearsal
Validate table service, KDS handoff, receiving, close-out, and manager exception paths together.
- Run table-service tickets
- Check kitchen tickets
- Compare close-out reports
Migration confidence pack
What MarginKind does vs. what your team owns
MarginKind helps with
- Maps exported menu and item data into a staging tenant before service is affected.
- Helps review recipes, ingredients, modifiers, staff roles, and reporting assumptions before cutover.
- Keeps roadmap-only migration work labeled separately from shipped import and review workflows.
Your team provides
- Exports current menu, modifier, staff-role, and reporting reference data from the incumbent system.
- Chooses a low-risk service window for rehearsal and production cutover.
- Keeps the incumbent available during the first live services while managers compare close-out reports.
Parallel running
For most operators, the safest path is at least two rehearsal services plus two to five live service days where managers can compare tickets, menu behavior, payments, and close-out reporting before relying on the new system alone.
Want help pressure-testing the plan?
Bring your current menu, staff role list, and one week of close-out reports. We can map the riskiest cutover points before you commit.
Plan a migration call