Migrate from Bright to monday CRM

Bright automations do not migrate — they must be rebuilt in Monday's Automation Center

Bright workflow rules, triggers, and automated actions are not stored in a format compatible with Monday CRM. Any automation that sets field values, sends notifications, or moves deals between stages based on conditions must be rebuilt in Monday's Automation Center using recipe sentences (When-Then triggers). FlitStack exports Bright workflow definitions as a structured rebuild reference listing every trigger object, condition, and action so your Monday admin can recreate them step by step. This is the most common source of post-migration surprises for teams that relied heavily on Bright automations.

Monday API rate limits vary dramatically by plan — large migrations can hit DAILY_LIMIT_EXCEEDED

Monday CRM enforces rate limits that vary by plan tier: Basic and Standard accounts are capped at 1,000 API calls per day, Pro accounts at 10,000 (soft limit), and Enterprise accounts at 25,000 (soft limit). In addition to daily caps, Monday applies complexity limits per query, minute limits, and concurrency limits (40 concurrent for non-Enterprise, 250 for Enterprise). Migrations exceeding these limits receive DAILY_LIMIT_EXCEEDED or COMPLEXITY_BUDGET_EXHAUSTED errors. FlitStack handles this by batching API calls, paginating large record sets, and implementing exponential backoff — but migrations from Bright accounts with >50,000 records on Basic plans require a phased approach that may extend the timeline.

Monday lacks a native equivalent to Bright's relational contact-company-deal object model

Bright CRM stores contacts, companies, and deals as distinct relational objects with foreign-key references. Monday CRM represents all three using board items — contacts in the People board, organizations in the Organization board, and deals in the Deals board — linked via Person and Organization column types rather than relational keys. This means Bright's N:1 contact-to-company relationships map cleanly to Monday's Organization column on People items, but many-to-many relationships or shared contacts across deals require careful mapping. FlitStack surfaces these relationship patterns in the migration plan and resolves them using Monday's native linking columns.

Monday does not support multi-currency natively on the Deals board

Bright CRM supports multi-currency deal values with currency codes attached to individual deals. Monday CRM's Deals board Number column stores numeric values without a native currency field. Teams migrating from Bright with multi-currency deals need to add a Text or Status column for currency codes and ensure any reporting that depends on converted values is rebuilt using Monday's Dashboard widgets or a third-party reporting integration. FlitStack flags every deal with a non-default currency during the pre-migration audit and includes the currency code in the migration plan.

Bright's activity type taxonomy does not map one-to-one to Monday Updates

Bright distinguishes between call logs, email logs, meeting notes, and tasks as separate activity types, each with structured fields (duration, outcome, attendees). Monday stores all such records as free-text Updates on items or as items in a dedicated Activity board. The activity type is lost unless prefixed in the update text or stored as a Status column value. FlitStack prefixes every migrated activity with its Bright type tag (e.g., [Call], [Email], [Meeting]) in the Monday Update so teams can filter and search by activity type post-migration, preserving the semantic distinction.