Migrate from Encharge to monday CRM

Encharge People records map to Monday.com CRM Contacts. Standard fields (email, name, phone, address) map to the corresponding Contact columns. Custom person fields migrate as custom Columns on the Contacts board, with type mapping applied (text fields to Text columns, date fields to Date columns, numeric fields to Number columns). Tag assignments from Encharge migrate as Labels on the Contact record. We export all tag history per Person and reapply as Monday.com Labels, preserving the full tag list on each contact record.

Encharge Accounts map to a Companies board in Monday.com CRM. Company name, domain, industry, employee count, and custom company fields migrate to matching Columns on the Companies board. Company custom fields become custom Columns with their respective types. Places (location data) attached to Accounts map to the Address column type if the Monday.com plan supports it, or to a structured Text column. The Companies board must be populated before Contacts import to satisfy the Account reference on Contact records.

Encharge Tags are flat string labels applied to People. We export the full tag assignment history per contact and reapply as Monday.com Labels on the CRM Contacts board. Tags do not carry any hierarchical structure in Encharge, so the mapping is direct. If a contact has multiple tags, all labels are preserved on the migrated record.

Encharge Segments are dynamic filter-based groups of People. We export the segment definition including filter rules, operator logic, and field criteria. In Monday.com CRM, we recreate each segment as a Saved Filter on the Contacts board with equivalent conditions. Segments do not auto-update in Monday.com the way they do in Encharge unless the customer enables a third-party integration or rebuilds the segment logic using Monday.com Automations.

Encharge Custom Objects (Deals, Orders, Invoices, or any customer-defined entity) map to Monday.com custom Boards. The schema is customer-defined, so we perform field-level mapping for each Custom Object: Encharge custom fields become typed Columns on the destination Board, and any lookup relationships between Custom Objects are modeled as Connect Boards columns referencing the related Board. The customer must define the destination schema during scoping because Custom Objects lack a standard target in Monday.com CRM.

Encharge Activities record behavioral events (email opens, page views, custom product events, payment status changes). Monday.com CRM has no native behavioral activity log; we map Activities to Item Updates on the relevant Contact or Company record. Each Activity generates a timestamped Update with the event name and any associated metadata. Event names are normalized to a consistent string format. Note that Monday.com Item Updates lack the structured field mapping of a dedicated CRM activity log; this is a functional flattening compared to Encharge.

Encharge Email Templates store HTML with subject lines, sender names, and inline styles. We export templates as HTML files and import them into Monday.com's Email Template library. Inline images are exported as separate assets and re-hosted or attached. Template metadata (subject, sender name, preheader text) is preserved in the Monday.com template record. Note that Monday.com Email Templates are used within CRM automations and manual outreach; they do not carry Encharge's merge tag logic and must be reviewed for placeholder syntax after migration.

Encharge Campaigns group emails and automation steps. We export campaign names, status, and associated contact counts. In Monday.com CRM, Campaigns are mapped to a dedicated Board with Items representing each contact in the campaign, or to Groups within an existing board, depending on the customer's preferred structure. The campaign-to-automation association does not export and must be rebuilt using Monday.com Board Automations.

Encharge Forms capture new People and trigger enrollment into Flows. We export form field definitions and webhook configurations. Form URLs and embed codes do not migrate and must be updated in the destination system post-migration. Monday.com CRM Forms are set up separately and map to the Contacts board.

Encharge Flows store automation logic as JSON configuration referencing triggers, conditions, and downstream actions with no documented export endpoint. We document every Flow during scoping: trigger type, condition branches, wait-step durations, and action sequence. The output is a written inventory with step-by-step descriptions that the customer's team uses to rebuild each Flow in Monday.com Board Automations. This is a manual rebuild, not a data migration.