MarginKind

Migration guide

Switching from Toast to MarginKind

Treat the migration as an operating-model cleanup, not just a POS swap. The safest path is to export current menus, staff, inventory, and reporting assumptions before rebuilding them into connected MarginKind workflows.

Step 1

Inventory the current Toast setup

Document menus, modifiers, KDS routing, online ordering settings, staff roles, tax setup, and payment workflows before touching live service.

  • Export menu and modifier data
  • Capture KDS routing by station
  • List staff roles and permissions

Step 2

Rebuild the operating model

Create MarginKind business units, menus, recipes, labor roles, and reporting groupings in a staging tenant.

  • Map Toast menus to MarginKind modules
  • Validate recipes and allergens
  • Run side-by-side reporting checks

Step 3

Cut over by service window

Pick a low-risk service period, train managers on exception handling, and keep exported Toast references available during the first week.

  • Schedule manager training
  • Freeze menu edits before cutover
  • Run first close-out with both reports in hand

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