Migrate from Trade Service Pro to monday CRM

Monday CRM only supports specific import column types — custom Trade Service Pro fields may require post-migration manual entry

Monday's import process restricts column types to Text, Numbers, Date, Timeline, Phone, Location, Email, Checkbox, and Status. Trade Service Pro custom fields that use non-matching types (such as formula fields, multi-select tags, or rich-text notes) cannot be imported directly. FlitStack flags each non-standard field before migration and either maps it to the nearest Monday column type or documents it for manual entry after the Board structure is live. This is a pair-level gotcha because any CRM-to-Monday migration hits this limitation, but the severity depends on how many custom fields Trade Service Pro has in use.

Trade Service Pro automations and workflow rules do not transfer to Monday CRM — logic must be rebuilt manually

Monday CRM's automation builder uses a recipe model with triggers (column changed, date arrived, status updated) and actions (notify user, update column, create item). Trade Service Pro's automation logic (email-on-schedule, status-triggered notifications, recurring job generation) has no direct equivalent in Monday's export format. FlitStack exports your Trade Service Pro automation configurations as a plain-English rebuild reference document listing each rule's trigger condition and action. Your Monday admin uses this to recreate automations in Monday's no-code builder. This is pair-level because the rebuild work is specific to the destination's automation architecture.

Monday's daily API call limits vary by plan — high-volume migrations may require batching or Enterprise rate-limit exceptions

Monday CRM enforces daily API call limits: 1,000/day on Basic/Standard, 10,000/day on Pro, and 25,000/day on Enterprise. Trade Service Pro exports with large record counts (jobs, invoices, line items, attachments) can exceed Standard plan limits if the migration tool runs bulk API operations. FlitStack uses Monday's batch endpoints and respects per-plan rate limits by throttling writes. If your migration volume exceeds your plan's daily cap, we recommend upgrading to Pro for the migration window or requesting a temporary Enterprise rate-limit exception from Monday support.

Timesheet and time-tracking data has no native Monday equivalent — a custom Board or third-party integration is required

Trade Service Pro's timesheet module tracks clock-in/clock-out times, break durations, and job-linked timers. Monday CRM has no native time-tracking object — time tracking is available only via the Pro plan's Time Tracking column on individual boards, which is designed for task duration, not employee timesheets. FlitStack migrates timesheet records as items on a dedicated Time Tracking Board. For ongoing time capture, your team either uses Monday's manual Time Tracking column on each board or connects a third-party integration (Clockify, Toggl, etc.) via Zapier or Monday's native integration marketplace.

QuickBooks sync configurations do not migrate — invoice data moves, but the accounting connection must be rebuilt

Trade Service Pro offered native QuickBooks synchronization for customers, products, invoices, and payments. Monday CRM has a QuickBooks integration that must be reconnected after migration. FlitStack migrates your Trade Service Pro invoice records (invoice number, total, balance, line items) into Monday Deals and Products, but the QuickBooks connection — including chart-of-accounts mapping, payment reconciliation rules, and QB user permissions — must be reconfigured from scratch in Monday's integration settings. This is pair-level because the connection logic is specific to each platform's QuickBooks implementation.