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.

See the import story Why switch from Toast

Import-led path

Move the menu before you move service

Toast menu exports are part of the shipped import path. MarginKind can stage imported items, queue AI-assisted recipe drafts, and keep review/commit decisions visible before production service.

Capability tag: shipped for Toast/Square import and AI recipe-generation during import; roadmap for automated imports from other vendors.

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

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.

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.

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