Migrate from ConSol to monday CRM

ConSol nested case hierarchy requires flattening before import into monday CRM items

ConSol supports parent-child case relationships where a sub-case inherits context from its parent and can have its own SLA, assignee, and activity log. Monday CRM's item model is flat — sub-items exist but do not carry independent SLA timers or deep hierarchy. FlitStack flattens sub-cases into monday CRM sub-items linked to their parent item via a custom Parent_Item_ID__c field. SLA hours and timestamps are preserved as custom fields on each sub-item. If your ConSol setup has more than three levels of case nesting, we recommend splitting those levels across separate monday CRM boards with cross-board links rather than relying solely on sub-items, which monday CRM limits to one level deep.

Monday CRM API daily call limits cap bulk ingestion speed on lower plans

Monday CRM enforces daily API call limits that vary by plan: 1,000 calls/day on Basic and Standard tiers, 10,000 calls/day on Pro, and 25,000 calls/day on Enterprise. A ConSol instance with 50,000 cases plus attachments can require hundreds of thousands of individual API calls when counting nested records, file uploads, and update logs. FlitStack handles this by batching records, using monday CRM's bulk-friendly mutation endpoints where available, and respecting per-minute concurrency limits (40 for non-Enterprise, 100 for Pro, 250 for Enterprise). Large migrations on Basic/Standard plans may take longer because we pace calls to avoid DAILY_LIMIT_EXCEEDED errors — this affects timeline estimates for high-record-volume migrations.

SLA tiers and escalation timers have no native monday CRM equivalent and must be rebuilt

ConSol CM tracks SLA tiers with named stages (First Response, Resolution), configurable timers, and escalation rules triggered when timers breach. Monday CRM has no native SLA column type or time-tracking for case items — the platform does not automatically trigger escalations based on elapsed hours. FlitStack migrates SLA tier names and hour values as custom columns on monday CRM items. SLA escalation automations must be rebuilt in monday's automation builder (Pro and Enterprise tiers support time-based triggers). This is a business-process decision that your monday CRM admin should scope after reviewing the migrated data, not a data-loss issue.

Monday CRM automations are board-scoped and cannot replicate ConSol cross-entity BPM rules

ConSol workflows can span multiple case types, trigger on SLA breaches across entities, and route cases between service queues based on complex conditions. Monday CRM automations are scoped to a single board — there is no cross-board automation or global workflow engine in the CRM module. FlitStack exports ConSol automation definitions as JSON that your monday CRM admin can use as a rebuild reference. The practical constraint is that multi-entity escalation chains and cross-board routing must be redesigned in monday CRM rather than directly ported.

File attachments on ConSol cases require download and re-upload to monday CRM storage

ConSol stores file attachments in its own document management layer. Monday CRM attaches files to items using its own storage system. FlitStack downloads ConSol attachments, preserves original filenames, and re-uploads them to monday CRM items. File size limits depend on your monday CRM plan — Standard includes 5GB account storage and Pro includes 100GB. Very large attachments (CAD files, high-resolution images) that exceed monday's per-file upload limits must be stored externally with a link stored in the monday CRM item description field.