Migrate from Pipz to Odoo CRM

Pipz Contacts map to Odoo res.partner records with type=contact. Email, phone, custom properties, and tags migrate to corresponding Odoo fields. The Pipz lifecycle stage property (prospect, customer, evangelist, etc.) migrates as a selection field x_pipz_lifecycle_stage on res.partner. The Customer Engagement Index numeric value migrates to a custom float field x_customer_engagement_index on partner for reporting and segmentation in Odoo. Company-linked contacts get parent_id set to the mapped company partner.

Pipz Companies map to Odoo res.partner with type=company. The company domain becomes the partner's website field and is used as a dedupe key during import. Child contacts under the company link via parent_id to the company partner record, preserving the contact-to-company relationship graph from Pipz.

Pipz Deals map to Odoo crm.lead with type=opportunity. Deal name becomes crm.lead name, deal value (amount) becomes planned_revenue, and the Pipz pipeline stage maps to stage_id on crm.lead using a stage name match we pre-create in the destination Odoo database. Owner assignment maps from Pipz user email to Odoo res.users id via the User reconciliation step.

Pipz pipeline stages map to Odoo crm.stage records within the customer's crm.team. We transfer stage names and sequence ordering. Probability percentages for each stage transfer to Odoo's stage_proability field. If Pipz stages have custom automation triggers or notification rules, we flag these for manual Odoo Studio or code-based rebuild because triggers do not migrate.

Pipz engagement events (email opens, link clicks, page views, in-app chat messages) migrate to Odoo mail.message records linked to the contact's res.partner record via model=res.partner and res_id=partner_id. Each event type maps to a mail.message subtype (email, meeting, call, note) for proper chatter rendering. Timestamps preserve the original Pipz event time. Chat conversation threads migrate as grouped message sequences.

Pipz email campaign records (name, subject, send date, status, open rate, click rate) migrate as a custom campaign record x_pipz_campaign with metadata preserved. The linked contact list migrates as mail.mass_mailing contacts or a res.partner tag group. Campaign performance metrics (opens, clicks, unsubscribes) store in custom fields on the campaign record for Odoo reporting.

Pipz tags applied across contacts, companies, and deals migrate to Odoo res.partner.category records. Tag-to-record associations preserve across objects. If a tag applies to both contacts and deals, we create both a partner category and a crm.tag entry and map associations separately per object type.

Pipz Smart Segments built from demographic, tag-based, and behavioral rules do not migrate as saved filters because Pipz's segment logic (login activity, email engagement, tag combinations) has no direct Odoo equivalent. We extract the full segment definition including rule structure, criteria types, and logical operators (AND/OR/NOT) and deliver a written segment mapping document specifying which Odoo saved filters or reports reproduce each segment's output.

Pipz custom fields on contacts, companies, and deals map to Odoo ir.model.fields created as custom columns on the respective model. Field type mapping: text to char or text, number to float or integer, date to date, checkbox to boolean, dropdown to selection. We create the destination fields in the Odoo database before any data import and map values during the transform phase.

Pipz users assigned as owners to contacts, deals, and automation flows map to Odoo res.users. We resolve by email match. Any Pipz user without a matching Odoo res.users record enters a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Pipz users map to Odoo users with active=False to preserve assignment history.

Pipz automation flows and workflow triggers do not migrate as logic. These are built on Pipz's proprietary automation engine and have no equivalent Odoo construct that accepts a direct import. We extract every active automation with its trigger, conditions, and actions and deliver a written automation inventory specifying the recommended Odoo Studio equivalent or custom ir.actions.server rebuild.

The Pipz Customer Engagement Index is a proprietary composite score derived from login frequency, in-app actions, and email engagement. It has no Odoo equivalent. We extract the numeric CEI value and store it as a custom float field x_customer_engagement_index on res.partner. The raw engagement events (email opens, page views, chat interactions) migrate separately as mail.message records to preserve the underlying behavioral data for future Odoo-based scoring rebuilds.