Migrate from iPresso to Twenty CRM

iPresso Contact records map to Twenty People. We preserve name fields (firstName, lastName), email address, phone number, and lifecycle stage as a custom field ipresso_lifecycle_stage__c. Behavioral event history and campaign interaction counts migrate as JSON-serialized custom fields or as linked Note records so that historical engagement context is available without cluttering the People record. Channel subscription preferences (Email, SMS, Web Push) migrate to custom checkbox fields in Twenty.

iPresso Company records map directly to Twenty Company. Domain from iPresso's company domain field populates the Company website field and is used as the deduplication key during import. Industry classifications, custom company-level fields, and address data migrate as typed fields or custom fields in Twenty's Data Model. Company is created before People import so that the relationship lookup is satisfied at the moment of People insert.

iPresso Campaign records represent marketing initiatives with audience segments, channel assignments, and performance metrics. We map campaign metadata (name, status, start/end dates, channel) to a Twenty Custom Object named Campaign. Audience segment membership is preserved as a tag-like custom field or linked via a Custom Object relationship. Performance metrics (opens, clicks, conversions) migrate as numeric custom fields. If the customer has a large campaign history, we discuss archiving older campaigns versus importing all.

iPresso contact segmentation tags migrate to Twenty as either a multi-select picklist custom field on People (recommended for under 50 distinct tags) or as Twenty Topics with TopicAssignment records (recommended if tags number in the hundreds and serve content classification purposes). The customer chooses the strategy during scoping. Tag membership history per contact migrates as a comma-delimited or JSON-serialized custom field value.

iPresso custom contact properties migrate to Twenty custom fields on the People object. We create all custom fields in Twenty Settings → Data Model before importing any records, per Twenty's requirement that fields must exist before CSV import. Field types are mapped: text to text, date to date, number to number, picklist to select. Validation rules from iPresso custom fields require manual reconfiguration in Twenty's Data Model.

iPresso custom company properties migrate to Twenty custom fields on the Company object. Same approach as contact-level custom fields: pre-create in Twenty's Data Model before import, map field types explicitly, and note any picklist values that require translation. Industry-specific iPresso company configurations (Finance, FMCG, Education, Travel verticals) map to custom fields with appropriate data types or to a vertical-specific Custom Object.

iPresso Enterprise-tier industry-specific solutions (FMCG, Finance, Education, Travel) are custom-configured objects that exist only on higher iPresso plans. We map each to a corresponding Twenty Custom Object with fields matching the source schema. These require pre-creation in Twenty's Data Model with lookup relationships to Company and People. Not all iPresso industry configurations are directly migratable—some represent workflow logic rather than pure data, and those are documented in the automation inventory rather than imported.

iPresso email templates store HTML content and dynamic personalization tokens. We extract the HTML body and migrate it as a Note record attached to a Template-type Custom Object, preserving the template name and any field reference tokens for manual update in Twenty. Dynamic tokens (contact.firstName, contact.email) require field reference updates because Twenty uses different variable syntax. We do not migrate template rendering logic or A/B test configurations.

iPresso channel configurations (sender settings, SMS provider credentials, Web Push credentials) do not export as reusable data because they contain credentials and third-party API keys tied to the iPresso platform. We document the channel configuration settings in the handoff inventory so that the customer's admin can recreate them in Twenty or the appropriate channel provider. Email sending via Twenty uses the configured SMTP or email provider; SMS requires a Twilio or equivalent integration.

iPresso multi-step workflow sequences do not migrate. We deliver a written inventory of every active iPresso Workflow documenting its trigger conditions, steps, delays, CRM actions, and channel assignments. The customer uses this inventory to rebuild equivalent logic in Twenty's system. Twenty CRM does not include a native visual workflow builder as of 2026—automations require custom development or a third-party workflow tool integrated via API. This is a significant scope item that the customer should plan for separately.

iPresso drag-and-drop landing page assets do not export as reusable templates or HTML. We document the page names, URLs, associated campaigns, and form field configurations in the handoff inventory. The customer's admin rebuilds pages in their preferred landing page tool (Twenty does not include native landing page creation). Form field mappings are preserved as structured data so that the new landing page tool can reference the same field names.