Migrate from Zuper to monday CRM

Zuper Workflow Builder has no Monday CRM equivalent — automations must be rebuilt

Zuper's Workflow Builder uses a node-based graph with IF/Else branching, Copy Custom Fields nodes, and cross-module triggers that activate when specific field values change. Monday CRM's Automation Center operates on recipe sentences — When [column changes] Then [action]. There is no Monday equivalent to Zuper's Copy Custom Fields node, which copies field values from one record to another within the same module. Teams that rely on Zuper's workflow logic for job routing, automatic customer record updates, or team assignment triggers will need to rebuild these rules manually in Monday's Automation Center. FlitStack exports your Zuper workflow definitions as a structured JSON document your Monday admin can reference during the rebuild phase. This is not a FlitStack limitation — it is a structural difference between the two automation models.

Monday CRM's daily API call limits cap migration throughput

Monday CRM enforces a daily call limit that varies by plan: 1,000 calls per day on Basic/Standard, 10,000 on Pro, and 25,000 on Enterprise. FlitStack's migration engine respects these limits by tracking remaining call budget and pausing between batches. For accounts with 50,000+ records, this means the migration run may span multiple calendar days as the engine paces itself. If your Monday account is on a lower tier plan, FlitStack will recommend upgrading to Pro or Enterprise for the migration window, then you can downgrade afterward. The Monday.com admin can also request a temporary limit increase through Monday's support team for Enterprise accounts.

Job-to-Customer linking requires Monday item linking configuration

Zuper stores a customer_id foreign key on each Job, creating a natural parent-child relationship. Monday CRM has no native foreign-key model between Items on separate boards — there is no equivalent to Salesforce's AccountId lookup field. FlitStack addresses this by creating a Contact Reference column on each Deal Item that stores the source Zuper customer name and ID. Where your Monday account has item linking enabled, we wire each Deal Item to its corresponding Contact Item directly. If Monday's native linking is unavailable on your plan, the Contact Reference column acts as a manual-link placeholder. Your admin maps the reference column to a Monday integration or Lookup formula post-migration to restore the link programmatically.

Monday.com full account export can take up to 24 hours to generate

Monday.com's native Export Account Data function (available in the admin panel) generates a zip file containing all boards, items, and file references. According to Monday's support documentation, large account exports can take up to 24 hours to become available for download. FlitStack does not rely solely on this export path — we use direct API fetches for real-time data retrieval during migration. However, if your team plans to use Monday's native export as a reference or backup, factor this 24-hour generation window into your migration timeline. The FlitStack migration does not wait for this export to complete.

Per-seat pricing model requires seat planning before migration

Monday CRM charges per seat, and migrating all Zuper team members into Monday means you will need a Monday seat for each active user. Monday's per-seat pricing ranges from $12/seat/month on Basic to custom Enterprise pricing. If Zuper has 15 active technicians and 2 admin users, you will need at minimum 17 Monday seats post-migration. FlitStack surfaces the user count from Zuper's Teams module before migration so your team can confirm seat requirements and select the appropriate Monday plan. Adding seats mid-migration requires plan upgrades that incur prorated charges — we recommend resolving seat count before the migration run begins.