Migrate from Toast to Recruit CRM & ATS

Toast Employee records (name, email, phone, role, permissions, hire date) map to Recruit CRM Candidate records. Toast role assignments (server, cook, manager) have no direct Recruit CRM equivalent and are stored in a custom text field toast_original_role__c. Toast does not expose full compensation history via the standard API, so wage rates and payroll data are not migratable. We archive any compensation data extracted from SFTP exports to JSON for the customer's HR records.

Toast Customer/Guest profiles (name, email, phone, visit frequency, loyalty points) map to Recruit CRM Contact records. Toast-specific fields like dining preferences and allergen notes have no Recruit CRM equivalent and are preserved in a custom text field toast_preferences__c if the customer requests it. Note that these are restaurant guests, not recruitment contacts — the mapping preserves the data but the contact records require manual categorization post-migration if they represent candidates or clients.

Time Entry records (clock-in, clock-out, break duration, hours worked, overtime flags) have no Recruit CRM equivalent. Recruitment CRMs track candidate availability windows, not labor time punches. We export all Time Entries to a dated JSON archive with employee_id reference for audit and HR compliance purposes. The archive is delivered alongside the migration but does not populate Recruit CRM.

Toast Shifts (scheduling windows, role assignments, location) have no Recruit CRM equivalent. Recruit CRM's scheduling features cover interview calendars and candidate availability, not restaurant floor labor scheduling. We export all Shift records to JSON with employee_id references and deliver them as a standalone archive. Customers with active labor scheduling needs retain Toast or implement a dedicated scheduling tool.

Order records (item-level detail, server attribution, payment status, order type) have no equivalent in Recruit CRM. Recruit CRM's Deals represent placement revenue, not restaurant transactions. We export Orders to JSON from Toast's SFTP nightly exports, preserving item detail and server attribution. This archive serves compliance and historical reporting needs but does not populate Recruit CRM.

Payment records (transaction method, card type, authorization codes, settlement status) have no Recruit CRM equivalent. Recruit CRM does not track payment processing. We export Payment records to JSON from Toast, keyed by order_id. The customer retains Toast's payment history for financial reconciliation through Toast's standard reporting or their accounting system export.

Toast Menu Items, Modifier Groups, and nested Modifiers define the restaurant product catalog. Recruit CRM has no product catalog or inventory management equivalent — Jobs and Candidates are the catalog objects, and they represent talent, not food and beverage. We do not migrate Menu Items or Modifiers. Customers should pull a Toast menu export via SFTP for their own records before cutover if the menu needs to be preserved for external use.

Toast Tables and Sections define restaurant floor layout, server assignments, and turn-time tracking. Recruit CRM has no floor plan or table management equivalent. We do not migrate Table configuration. This data is not relevant to a recruitment CRM and has no archiving value unless the customer operates a hospitality-adjacent business that needs it elsewhere.

Toast's vendor management and purchase order data is not exposed via the public API. We do not migrate Vendor or Purchase Order records. Recruit CRM has no vendor management module. This data should be extracted from Toast's back-office reporting or accounting integration if the customer needs to preserve it.

Toast inventory tracking data (stock levels, usage, product mix reports) has no Recruit CRM equivalent. Recruit CRM is a talent platform, not an inventory management system. We do not migrate inventory data. Product mix and usage reports should be exported from Toast's SFTP nightly exports for the customer's financial and supply chain records.

Toast Checks (session-level order grouping, payment allocation, tip application, refund status) have no Recruit CRM equivalent. Recruit CRM does not track session-based transactions. We export Checks to JSON keyed by order_id for financial reconciliation purposes. Tip data in particular may be relevant to the customer's HR or payroll team if tips are pooled or redistributed.

Toast Cash Management records (drawer tracking, bank deposits, cash-over-short reports) have no Recruit CRM equivalent. Recruit CRM is not a financial management or accounting tool. We export Cash Management records to JSON for the customer's finance team to reconcile through their accounting system or Toast's standard reporting.

Toast Tax Codes and jurisdiction assignments define restaurant tax compliance configuration. Recruit CRM does not manage tax jurisdiction or compliance settings. We do not migrate tax configuration. Customers with multi-jurisdiction tax compliance requirements should retain this configuration within Toast or transfer it to their accounting system directly.

Restaurant groups using Toast's multi-location Enterprise module may have Company-level records representing individual locations. These map to Recruit CRM Company records as client or organization records. Location-specific operational data (sales, inventory, staffing) does not migrate — only the Company name, address, and contact information transfers to Recruit CRM as a client organization record.