Migrate your Toast data

Orders are the primary transaction record in Toast and include full item-level detail, payment status, and server attribution. We export Orders via SFTP nightly exports or real-time API where available. The schema includes order ID, timestamps, revenue, taxes, and discounts. Migration support is standard and reliable.

Payment records in Toast capture transaction-level payment method, card type, authorization codes, and settlement status. We map these to the destination payment object and preserve payment processor references. Toast's proprietary processing means payment processor attribution is tied to Toast's gateway.

Menu Items are configurable objects with pricing, categories, availability windows, and modifier associations. We map Items to the destination catalog but note that item-level images, descriptions, and allergen data require separate export handling. Menu hierarchy (categories, subcategories) is preserved where present in exports.

Modifiers are linked to Menu Items and define add-on pricing, required/optional flags, and max-select constraints. Toast's modifier schema supports nested modifiers. We map modifier groups to the destination item customization model but complex conditional modifiers may require field-level translation.

Employee records include names, roles, contact information, and permissions. Toast does not expose full compensation history or payroll data via the standard API. We migrate employee profiles and role assignments, but compensation, benefits, and PTO balances require separate export and are not part of the standard migration set.

Time Entries are available via Toast's nightly SFTP export and include clock-in, clock-out, break duration, and hours worked. We map these to the destination time-tracking object. Overtime flags and tip allocation data are included in the labor export where configured.

Shifts define employee scheduling windows and role assignments. Toast scheduling data is part of the HR module and can be exported. We map Shifts to the destination scheduling object, though shift-swap notes and approval workflows do not export cleanly and are noted as manual reconciliation items.

Table and section configuration defines restaurant floor layout, server assignments, and turn times. These are exportable as configuration data. We map table records to the destination floor-plan or table management object, but real-time table status is not historical data and does not migrate.

Toast's vendor management and purchase order functionality is limited and not exposed via public API exports. Inventory receiving and vendor ledger data are not reliably extractable. We do not migrate vendors or purchase orders from Toast; these must be recreated or sourced from separate inventory systems.

Toast provides inventory tracking features as part of the POS and back-office suite. Product mix reports and inventory counts are available via SFTP exports. We map stock levels and usage data to the destination inventory object, but real-time inventory reconciliation may require manual post-migration validation.

Guest profiles capture visit history, preferences, and loyalty program data. We map Customer Profiles to the destination contact or guest object, preserving loyalty points and visit frequency. Email and phone opt-in status is preserved as a contact property in the migration.

Checks (bills) represent a table session's order grouping and include payment allocation, tip application, and refund status. We map Checks as the session-level object tied to the Order. Check-level tip reporting is preserved for payroll reconciliation.

Cash drawer tracking, bank deposits, and cash-over-short reports are part of Toast's cash management module. These are available via SFTP exports. We map cash management records to the destination accounting or float-tracking object, preserving daily reconciliation totals.

Tax configuration includes rates by jurisdiction, inclusive vs. exclusive tax handling, and tax-exempt rules. We map tax codes to the destination tax configuration, but tax jurisdiction assignments per item require validation against destination tax rules.