Migrate from Agillic to monday CRM

Agillic Recipients map to Monday.com CRM People entities. Every standard field (email, name, phone, address, company) maps directly. The critical discovery step is enumerating every custom recipient property the client has defined on their Recipients — Agillic allows unlimited custom fields with no fixed schema, so we cannot begin mapping until we have the complete property list from the Recipient API or Recipients Export. Missing a custom field at this stage results in silent data loss for that attribute.

Each Agillic custom recipient property maps to a Monday.com Person custom field. Text properties map to Text columns, numeric properties to Number columns, dates to Date columns, and multi-select checkbox properties to Tag columns. Enum or dropdown properties map to Dropdown columns with the original value options preserved.

Agillic stores every send, open, click, bounce, SMS delivery, and event trigger as a discrete Activity record with a timestamp and Flow Execution ID. We export Activity data per channel and date range, then represent it in Monday.com as either a chronological Updates thread on the Person item or as a separate linked Activity board with an Item-to-Person lookup relationship. The Flow Execution ID is preserved in a custom field for audit. Activity Export requires the Flow Execution ID setting to be enabled under Settings > System Settings > Export > Activity Exports — we verify this during discovery.

Agillic Global Data Tables are custom relational structures referenced within Flows. We export table schemas and all row data. In Monday.com CRM, each Global Data Table maps to a separate board with its own columns, and we create an Item-to-Item link or cross-board lookup relationship to connect it to the relevant Person or Deal item. Complex multi-column table structures may simplify to a linked board rather than a full relational replica.

Agillic Flows (campaign automation logic) cannot be exported as portable workflow definitions — there is no documented export endpoint and Flow logic is tightly coupled to Agillic's execution engine. We export Flow names, associated trigger events, and Activity history tied to Flow Execution IDs, but the branching logic, conditions, and wait-step configurations must be manually recreated in Monday.com's automation builder. We deliver a written Flow rebuild guide listing every active Flow with its trigger, conditions, and recommended Monday.com automation equivalent.

Agillic templates define layout and dynamic content fields for email, SMS, print, and push channels. We export template content and field mappings. HTML email templates require conversion to the destination email platform's format — Monday.com CRM has no native email template engine, so teams use integrations like Gmail, Outlook, or a dedicated email platform. We deliver a template content inventory with field mappings to guide the rebuild.

Content Blocks are modular HTML/text fragments used across multiple Agillic templates. We export block content and metadata. Monday.com has no native content block library; blocks must be recreated as text snippets or external CMS fragments. We provide a content block inventory with character counts and dynamic field references for the customer's content team to rebuild.

Agillic can export micro-audience segments to Google and Meta in real time. We capture audience definitions and membership logic from Agillic. Monday.com CRM does not have native paid media audience activation. We document the current audience logic and recommend the equivalent setup in Google Ads audience manager or Meta Business Manager, flagging any differences in segment-building tooling.

Agillic Profiles aggregate all known data about a Recipient across touchpoints. We treat Profile data as equivalent to the Recipient record with enriched attributes pulled from Activity and custom data. The consolidated profile view in Monday.com CRM is achieved through the combined Person item and linked Activity board rather than a native profile aggregate object.