Migrate from Mobile Worker to monday CRM

Monday API rate limits constrain migration throughput during the cutover window

Monday enforces a daily call limit that varies by plan tier — Free and Trial accounts are capped at 200 API calls per day, Basic and Standard at 1,000, Pro at 10,000, and Enterprise at 25,000. Additionally, Monday applies a complexity budget per query and a concurrency limit of 100 simultaneous requests on Pro (40 on other plans). If your migration includes more than 5,000 records across multiple boards, the bulk import may exceed the daily call limit on lower-tier plans. FlitStack paces the import using Monday's complexity headers returned in each response and retries with backoff on HTTP 429 responses. If you are on a Standard plan, we recommend upgrading to Pro before the migration run — the higher daily limit avoids split-batch imports that increase the risk of partial commits.

Automations do not migrate — every rule must be rebuilt in Monday's automation builder

Monday's automation infrastructure (triggers, conditions, actions) is not stored as data that can be exported and imported — it lives in Monday's application logic. Any dispatch rules in the source that auto-assign workers based on geofence entry, trigger notifications when a status changes to On-Site, or escalate overdue orders must be rebuilt as Monday automation recipes after migration. FlitStack exports your source automation definitions as a structured reference document (JSON or table format) listing each rule's trigger event, conditions, and actions so your Monday admin has a rebuild checklist. This is a platform-level limitation across all Monday products, not specific to CRM, and is explicitly flagged in Monday's own documentation.

Free-text status values require pre-mapping before Monday's Status column accepts them

Monday's Status column only accepts values from a defined set — you cannot bulk-import arbitrary text into a Status column. Many mobile-worker platforms store status as free-form text fields with dozens of team-specific values (e.g., 'Dispatched', 'Tech Assigned', 'Customer Confirmed', 'Parts Pending'). Before migration, FlitStack extracts every distinct status value from the source, deduplicates the list, and produces a mapping table that maps each source value to a Monday Status value. If the source has more than 20 distinct status strings, we recommend collapsing them into a smaller set of Monday Status values and storing the original text in a secondary Text column for audit reference.

File attachment re-upload counts against Monday workspace storage limits

Photos, signed forms, and PDF attachments from work orders re-upload to Monday's file storage. Monday does not offer unlimited file storage on lower plans — Pro includes 100GB per workspace, and Enterprise offers unlimited. If your source platform stores a large volume of large attachments (site photos, before/after images, signed PDF forms), the total upload size may exceed your Monday plan's storage allowance before the migration completes. FlitStack calculates total attachment volume during the discovery phase and surfaces a storage estimate before the migration run commits. If storage is a constraint, we can migrate attachments in batches matched to your Monday storage replenishment schedule.

Monday plan tier determines which column types are available for custom field migration

Monday's custom column types have plan-gated availability — Location, Dependency, Formula, Time Tracking, and Vote columns require Pro or Enterprise. If your source custom fields include any of these types, Monday requires a plan upgrade before those columns can be created and populated. FlitStack audits source custom fields during discovery, identifies any that require gated column types, and provides a plan-tier recommendation as part of the migration plan. We do not proceed with fields that require a higher plan without your explicit confirmation — data that cannot fit into a lower-tier column type stores as a Text column as a fallback.