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 SpotOn to MarginKind
Plan the migration around the bundled workflows your team actually uses: ordering, payments, team operations, online channels, inventory integrations, and reporting.
Import-led path
Move the menu before you move service
SpotOn migrations are a structured rebuild today. Automated SpotOn import is roadmap-tagged, while current exports and reports can still anchor a staged workflow review.
Capability tag: shipped for Toast/Square import and AI recipe-generation during import; roadmap for automated imports from other vendors.
Step 1
Inventory the bundle
Document POS, payment, online ordering, team, marketing, reporting, and integration dependencies before deciding what moves.
- List active integrations
- Capture hardware/payment assumptions
- Export menu and report references
Step 2
Map the operating system
Rebuild the daily manager loop in MarginKind: menu, KDS, labor, inventory, reporting, and close-out.
- Map menus to modules
- Configure labor roles
- Review reporting needs
Step 3
Lower cutover risk
Run a controlled rehearsal and compare service, close-out, and payment assumptions before production traffic.
- Run a mock service
- Compare daily reports
- Keep prior references available
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