Migration guide

Switching from Square to MarginKind

Use the migration to move beyond payment-first operations into a connected restaurant system. Preserve the simple service patterns your team likes while adding recipe, inventory, labor, and reporting depth.

See the import story Why switch from Square

Import-led path

Move the menu before you move service

Square JSON import is part of the shipped import path. MarginKind can map Square item data into reviewable menu and recipe work instead of asking managers to rebuild every item by hand.

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

Step 1

Export the Square foundation

Collect item libraries, categories, modifiers, team roles, location settings, and inventory reports.

Export items and modifiers
Document current team permissions
Capture inventory counts and low-stock alerts

Step 2

Model workflows in MarginKind

Map items into menus and recipes, connect stock and receiving flows, and configure service roles for each location.

Create business units
Attach recipes to menu items
Validate labor and reporting permissions

Step 3

Run a service rehearsal

Before go-live, run a mocked lunch or dinner flow through POS, KDS, payments, inventory, and close-out.

Run sample tickets
Check KDS routing
Compare end-of-day reporting

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