Migrate from iPresso to Odoo CRM

iPresso Contact records map directly to Odoo CRM Lead. We use the Contact's internal iPresso ID stored as an external identifier field (x_ipresso_id) on the Odoo Lead to enable future sync reversals. Lifecycle stage from iPresso (New, Active, Inactive, Churned) migrates to a custom selection field on the Lead and is also preserved as a tag for pipeline segmentation reporting. All standard Contact fields (name, email, phone, address, company association) map to their Odoo equivalents.

iPresso Company records map to Odoo Contact records with the company_name field populated from the iPresso company name. Odoo does not have a separate Account object; Companies are represented as Partners (Contacts with is_company=True) and related individual Contacts are linked via the child_ids relationship. We set is_company=True on the migrated Company record and link individual Contact records to it as children.

iPresso Campaign records map to Odoo CRM Opportunity. The iPresso campaign name becomes the Opportunity name, and campaign status maps to Odoo stage (New, Qualified, Proposition, Won, Lost). We preserve campaign type (Email, SMS, Push, Print) and audience segment size as custom fields on the Opportunity for reporting continuity.

iPresso contact segmentation tags migrate to Odoo CRM tags using the tag_ids relationship on Lead and Opportunity. Tag names transfer directly as string values. Tags used for behavioral segmentation (campaign response, engagement score tier) are preserved alongside tags used for organizational labeling to maintain segmentation logic in Odoo reporting.

iPresso email engagement records (sends, opens, clicks, replies) migrate to Odoo Lead or Opportunity internal notes with a standardized format: [Email] Subject: {subject} | Status: {engagement_type} | Date: {timestamp}. We preserve open and click counts as custom fields on the note for audit purposes. Full email body content migrates as note body text.

iPresso SMS engagement records migrate to Odoo internal notes with [SMS] prefix and the SMS body text. Delivery status (Sent, Delivered, Failed) from iPresso migrates to a custom selection field on the Odoo note record. Odoo CRM does not have native SMS capability; customers requiring SMS functionality must install an Odoo SMS gateway app from the Odoo Apps store post-migration.

iPresso call engagement records (if tracked via iPresso's call logging) migrate to Odoo internal notes with [Call] prefix, duration, and disposition. Call disposition values from iPresso (Connected, No Answer, Voicemail, etc.) map to a custom selection field on the Odoo note record. Call recording URLs are stored as text links in the note body.

iPresso meeting engagements map to Odoo Calendar.Event records linked to the corresponding Lead or Opportunity via the res_id and res_model fields. Meeting title, start datetime, end datetime, location, and attendee list transfer directly. Odoo Calendar syncs with external calendar providers (Google, Outlook) post-migration.

iPresso note engagements (free-form notes attached to contacts or companies) migrate to Odoo internal notes on the corresponding Lead or Opportunity record. Note body text transfers directly. The original iPresso note creation timestamp is preserved as x_ipresso_note_date on the Odoo note record.

iPresso's behavioral event data (page views, form submissions, campaign interactions, last active date) is aggregated into a set of custom fields on the Odoo Lead record. We create fields including x_last_activity_date, x_total_engagements, x_email_open_count, x_sms_send_count, and x_first_campaign_name. This preserves behavioral scoring context without requiring a full event log migration that would be difficult to represent in Odoo's relational model.

iPresso custom contact properties (beyond standard fields) are created as custom fields on the Odoo CRM Lead model. Field types are mapped: iPresso text to char, iPresso number to float, iPresso date to date, iPresso checkbox to boolean, and iPresso picklist to selection. All custom fields are prefixed with x_ per Odoo convention and added to the Lead form view in Odoo Studio before migration.

iPresso custom company properties migrate to custom fields on the Odoo Contact model (the is_company=True record representing the migrated Company). Industry classifications, sector tags, and company-level custom metrics are preserved as char or selection fields on the Contact record.

iPresso email template HTML content migrates to Odoo CRM email templates using the mail.template model. We export the template subject, body HTML, and inline image attachments. Dynamic personalization tokens (such as {{contact.first_name}}) require manual update to Odoo's QWeb template syntax ({{object.partner_id.first_name}}) post-migration, which we document in the template handoff notes.

iPresso channel configurations (SMS sender IDs, SMS provider credentials, Web Push credentials) do not have a migration path to Odoo CRM because Odoo does not include multi-channel marketing automation in its standard CRM module. We document the current channel configurations as a written inventory so the customer can reconfigure SMS and push notification providers in Odoo Marketing (if installed) or a third-party Odoo Apps integration.