Migrate from Essential MD Software Suite to monday CRM

Monday API rate limits throttle large migrations

Monday CRM enforces per-plan API rate limits that directly constrain how fast FlitStack can import records. The Basic and Standard plans cap daily API calls at 1,000 per day, which is insufficient for large Essential MD accounts with tens of thousands of contacts and activity logs. A 20,000-contact migration on a Standard plan can require batching over multiple days, extending the overall timeline. We throttle API calls, implement exponential backoff on 429 errors, and split large record sets across days. Teams with Pro or Enterprise plans receive 10,000 or 25,000 daily calls respectively, which substantially reduces batching overhead and cutover duration.

Essential MD workflow rules and automation logic have no export path

Essential MD does not expose workflow definitions, automation rules, or trigger conditions through its API or data export. Monday CRM has no native mechanism to import automation logic from an external source — automation recipes must be authored manually within Monday or rebuilt in a third-party integration platform. Teams that relied heavily on Essential MD automated lead routing, stage-change notifications, or task generation will need to recreate those recipes in Monday's automation center or in Make/Zapier. FlitStack provides a workflow-definition export summary from the source account to serve as a rebuild reference, but the rebuild itself is a separate configuration step outside the data migration scope.

Monday's export does not include sub-items or activity updates by default

The native monday.com account data export (available from the Administration panel) exports board items and column values but excludes sub-items, activity log entries, and update threads by default unless specifically selected during export configuration. If Essential MD activity records are structured as sub-items or if activity history is stored in updates, a naive Monda export misses them. FlitStack queries the monday.com API directly for sub-items and updates during the migration, ensuring activity history is preserved as separate activity items on the Activities board rather than relying solely on the account export zip file.

Monday file size limits require pre-migration triage for large attachments

Monday CRM caps file uploads at 250MB per file. Essential MD accounts that store large proposal PDFs, media files, or scanned documents attached to contacts, companies, or deals will encounter import failures for files exceeding this threshold. We scan file attachment sizes during the discovery phase, flag files over 250MB, and store them in a cloud storage location (Google Drive, SharePoint, or S3) with a URL reference stored in a Monday URL column instead of re-uploading the file directly. This preserves record linkage while working within Monday's storage constraints.

Monday board structure must be designed before records can be imported

Unlike Essential MD where custom fields are added to existing objects, Monday CRM requires each new column type to be created on the target board before records land. If the Monday boards (Contacts, Companies, Deals) do not have the required columns set up, the API import will omit those field values. FlitStack generates a Monday-side schema setup plan during the discovery phase — listing every custom column required, the column type to select, and the dropdown options for pick-list fields — so the Monday admin can pre-create columns before the migration run begins. This prevents partial imports where field data silently drops during the load.