Migrating from Toast POS to the Turtini Restaurant module

Moving your restaurant operations off Toast and into Turtini's Restaurant module takes 30-60 minutes and can run alongside Toast in shadow mode for a week before you cut over.

What we import:
• Menu (categories, items, sizes, modifiers, prices)
• Floor plan (tables, sections, seat counts)
• Reservations (open and historical for the chosen window)
• Orders (last 90 days by default; up to 2 years available)
• Inventory items (raw ingredients with current stock + cost)
• Recipes (item → ingredients with quantities, where you've configured them in Toast)
• Loyalty members and balances (mapped to Turtini Contacts)
• Staff (mapped to Workforce — payroll history stays in your provider)

What we don't import:
• Payment processor relationships — you'll connect Stripe (or Toast's own processor if you keep it) separately.
• Hardware / printer assignments — re-pair printers from Restaurant → Settings → Hardware after migration.
• Pending splits or open checks at the moment of export — close out checks in Toast before exporting.

Step by step:
1. Sign into Toast Web → Reports → Data Export → request "Full Export". Toast emails a .zip with menu CSVs, sales JSONL, reservations CSV, etc.
2. In Turtini, /setup/migrate → find Toast → click "Connect & import".
3. Upload the .zip.
4. Pick history window — "Last 90 days", "Last year", "Last 2 years". Reservations import separately and default to "Open + last 90 days".
5. Pick whether to enable shadow mode — when enabled, Turtini imports everything and lets you exercise the floor plan, register, and reservations without exposing them to your real customers. Toggle off when you're ready to go live.
6. Click "Run import". Progress shows in /setup/migrate/imports.

Shadow mode:
With shadow mode on, the Restaurant module is fully operational but the QR-ordering page (patron-facing) and reservation booking widgets are hidden. Use this to:
• Train staff on the new register
• Verify the menu reads correctly (prices, modifiers, photos)
• Test the floor plan against your actual room
• Run a few staff-only test orders to feel the close-out flow

Cutover:
When you're ready to go live:
1. Restaurant → Settings → Cutover → "Go live now".
2. The patron QR ordering page activates, reservations widgets unhide, and your published Builder site picks up the live menu block automatically.
3. Stop Toast — once Turtini is live, point your printers / KDS at Turtini and disable Toast's hardware sync. Cancel Toast on the next billing cycle.

Common issues:
• "Menu items missing photos" — Toast exports photos at low resolution; we keep what's there. Restaurant → Menu → click any item → upload a higher-res photo.
• "Modifiers don't match" — Toast and Turtini structure modifiers slightly differently. Restaurant → Menu → review modifier groups; the import flags any group that needed manual reconstruction.
• "Loyalty balances off" — Toast loyalty has multiple types (points, dollars, visits). The import maps them onto Turtini's points system; adjust balances per-member from Contacts → [member] → Loyalty if needed.

After cutover:
• Connect Stripe for card processing (Settings → Integrations).
• Set up Wally tools — restaurant_smartCascade86, recipe-driven inventory depletion (see "Menu modifiers" and "Recipe-driven inventory depletion" articles).
• Publish the menu to your Builder site if you have one — drop a Restaurant Menu block on the right page.