Migration guide
Switching from Clover to MarginKind
Plan around hardware, permissions, and inventory cleanup. Clover environments often grow through device setup and apps; MarginKind migration is a chance to simplify the operating map.
Step 1
Document devices and apps
List Clover devices, payment flows, kitchen routing, employee permissions, inventory apps, and any third-party add-ons in active use.
- Inventory devices by station
- Export item and category data
- List third-party apps and dependencies
Step 2
Translate operations, not screens
Rebuild the workflows your team actually needs: order entry, KDS, receiving, waste, staff permissions, and reporting.
- Map menu categories to MarginKind modules
- Build stock and recipe records
- Configure staff roles by unit
Step 3
Stage payment and service cutover
Validate hardware/payment assumptions separately from service workflows so a payment decision does not block operational training.
- Confirm payment approach
- Run a mock service
- Train managers on close-out and exception handling
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