Migrate from iPresso to monday CRM

iPresso Contact records map to Items in a Monday.com People Board. We map standard fields (first name, last name, email, phone, address) to matching Column types. The iPresso lifecycle stage property migrates as a Status or Tag Column so the customer's sales team retains the original stage value. Contact ownership (hubspot_owner_id equivalent in iPresso) resolves by email match to a Monday.com User or Person Column on the Item. Custom contact properties migrate as additional Columns configured with the appropriate type before import. Records are imported in batches with a dedupe pass on email address before each batch to avoid creating duplicate Items.

iPresso Company records map to Items in a dedicated Companies Board in Monday.com. Company name, industry, website, and address fields map to matching text and link Columns. Industry classifications migrate as single-select Columns. We create the Companies Board before Contact import so that a Company lookup Column on the People Board can reference the correct Item during Contact import. If iPresso Companies reference an industry-specific configuration (FMCG, Finance, Education, Travel verticals), we flag these for manual setup review at the destination because Monday.com's native industry field does not carry vertical-specific logic.

iPresso Deal records map to Items in a Deals Board. The deal name becomes the Item name, deal amount maps to a Numbers Column, deal stage maps to a Status Column with values matching the original iPresso pipeline stages, and pipeline assignment maps to a separate Label or Group Column. We configure the Status Column values to match the original iPresso dealstage values before migration so that stage history is preserved without manual correction. Closed-won and closed-lost reasons migrate as text Columns. Owner assignment resolves by email lookup to the Monday.com User Column.

Each distinct deal stage value from iPresso becomes a named Status Column value in the Monday.com Deals Board. Stage order and color coding are replicated from the iPresso pipeline configuration during schema setup. If multiple iPresso pipelines exist with different stage sets, we create separate Status Columns per pipeline or separate Groups within the Deals Board to keep stage values scoped per business line.

iPresso contact segmentation tags migrate as values in a Monday.com Tag Column or Label Column on the relevant Board. Tags used for campaign audience segmentation migrate as Label Column values on the Deals or Contacts Board. Multi-value tags (contacts with multiple tags) migrate as comma-separated Tag Column entries. We apply a dedupe pass on tag names before migration so that tag inflation does not create fragmented label sets at the destination.

iPresso Campaign records map to Items in a dedicated Campaigns Board, with channel assignment (Email, SMS, Web Push, Print) preserved as a Label Column and audience segment size preserved as a Numbers Column. Campaign performance metrics (open rates, click rates) migrate as Numbers Columns if they exist as fields in iPresso. We note that Monday.com does not have a native campaign attribution engine; campaign tracking metrics are stored as historical values and do not auto-update post-migration. The customer's admin should evaluate whether a dedicated marketing analytics integration (Google Analytics 4, Segment, or a BI tool) is needed to replace active campaign reporting.

iPresso custom contact properties require explicit Column creation in the Monday.com People Board before migration. We create each custom field as a Column with a type that matches the iPresso field type (text, number, date, dropdown, checkbox, email, phone). Picklist or multi-select custom fields in iPresso map to Monday.com Dropdown or Tag Columns. We validate Column configuration against the destination plan tier (Custom Columns are available on Pro and above) and flag any fields that require an upgrade to accommodate.

iPresso custom company properties migrate as Columns on the Companies Board. Company-level industry configurations and regulatory compliance fields (common in Finance, FMCG, and Education iPresso deployments) map to Monday.com Dropdown or Checkbox Columns. Enterprise-tier iPresso configurations that use custom industry solution objects require a separate Board with a custom schema that we design during schema design and validate in a staging run before production migration.

iPresso multi-step automation sequences do not migrate as executable automation code. Monday.com's automation model (triggers, conditions, and actions scoped per board) is structurally different from iPresso's event-triggered workflow builder. We deliver a written inventory of every active iPresso Workflow with its trigger conditions, action steps, delay rules, and contact/channel references. The customer's Monday.com admin rebuilds these using Monday.com's Automation Center or an integration platform (Make.com, Zapier) post-migration. We do not offer workflow rebuild as standard scope.

iPresso email template HTML content migrates as a static text asset in a shared document (Google Docs, Notion, or a delivered CSV) so the customer's team can reconstruct the template in Monday.com or their email sending tool. Dynamic personalization tokens that reference iPresso contact properties require field name mapping to the new Monday.com Column names. We flag every token that requires updating so the team handles personalization corrections during template rebuild.

iPresso drag-and-drop landing pages do not export as reusable templates. We document the page structure, field mappings, and audience logic in a written handoff document. The customer's marketing team rebuilds landing pages in Monday.com's native page builder or an external tool (Carrd, WordPress, HubSpot) post-migration. We do not migrate page assets as code or template packages.