Migrate from Serviceform to Odoo CRM

Serviceform Leads (name, email, phone, source, qualification status) map to Odoo crm.lead records. The lead_source property from Serviceform maps to Odoo's source_id (linked to crm.tracking.source). Lead score from Serviceform's AI qualification migrates to a custom float field x_serviceform_lead_score__c on crm.lead. If the lead is already a qualified contact in Serviceform, it can be mapped directly to res.partner with the Convert to Opportunity action deferred until Odoo admin review.

Serviceform leads marked with qualification status 'qualified' or 'customer' are candidates for direct res.partner creation rather than crm.lead staging. We create a res.partner record (contact type) from the Serviceform lead email, name, and phone, and flag it with a custom field x_migrated_from_serviceform__c for audit. The decision to use crm.lead versus res.partner as primary contact model is confirmed during scoping based on the customer's Odoo pipeline workflow.

Serviceform conversation logs (visitor messages, bot responses, timestamps, channel) map to Odoo crm.activity records with subtype for chat, or to mail.message records on the related crm.lead or res.partner. Each message pair is stored as a separate crm.activity line with body text containing the visitor and bot exchange. Channel metadata (web, email, SMS) maps to a custom selection field x_serviceform_channel__c. We offer full transcript migration or summary migration based on scoping volume.

Serviceform form submissions create crm.lead records in Odoo via Odoo's website lead form or via an incoming API payload. Form field names map to crm.lead fields (email, partner_name, phone, description). Conditional field visibility rules from Serviceform forms are documented during discovery and provided as a written specification for rebuilding via Odoo website form builder or custom module.

Serviceform chatbot flows consist of nodes, intents, and response rules. We export chatbot flow metadata and conversation tree structure. The outcome of the chatbot interaction (qualification result, booked meeting flag, selected intent) migrates as custom fields on the linked crm.lead record (e.g., x_chatbot_intent__c, x_meeting_booked__c). The chatbot flow logic itself cannot migrate as executable code; we deliver a node-by-node map of the original flow for rebuilding in Odoo's automation tools.

Serviceform user accounts with roles and seat assignments map directly to Odoo res.users. We resolve by email match. Active status migrates as boolean active. If a Serviceform user has no corresponding Odoo user at migration time, they enter a reconciliation queue for the Odoo admin to provision before contact and lead imports proceed.

Serviceform's ATS module stores applicant profiles and resume data separately from the main chatbot flows. If the destination Odoo instance has the HR Recruitment module installed, applicants migrate to hr.applicant with name, email, partner_phone, and resume file attached via ir.attachment. If Odoo Recruitment is not installed, we deliver applicant records as a structured CSV with the same schema for manual import or HRIS integration.

Serviceform live chat session logs (visitor info, agent assignment, resolution status) map to Odoo helpdesk.ticket if the Helpdesk module is active. Session records without a resolution (bot-only sessions) map to crm.activity on the related crm.lead. We resolve agent assignment to res.users by email match. Resolution status maps to ticket stage in Odoo.

Serviceform integration connections to third-party CRM, email, and analytics tools are stored as configuration references. We extract the list of active integrations and deliver a written inventory that maps each Serviceform integration to an equivalent Odoo app or external connector. For example, a Serviceform-to-Google Analytics integration would be documented for rebuild as an Odoo Google Analytics connector or custom tracking script.

Serviceform aggregated analytics (conversion rates, chatbot performance metrics, session duration averages) are calculated at read time from conversation data and are not independently stored records. These cannot be migrated. We migrate the underlying conversation records so that equivalent reports can be built in Odoo CRM's pivot, graph, and reporting views using crm.activity data.

Serviceform chatbot nodes support custom properties that store visitor-provided data or conversation context beyond standard lead fields. These custom properties are not well-documented in Serviceform's schema. During discovery we extract all custom property keys observed in conversation exports and create equivalent custom fields on crm.lead (x_serviceform_prop_<key>__c) before migration. Field type is inferred from data sample (string, integer, boolean, date) and validated against Odoo's allowed field types.

Serviceform's AI agent Mira produces a lead qualification score or status on each lead. This score migrates to a custom float field x_serviceform_score__c on crm.lead. If Serviceform provides a categorical qualification tier (e.g., cold, warm, hot), this maps to a selection field x_serviceform_qualification__c. The Odoo admin can use these fields in Odoo CRM's stage automation or lead scoring workflows post-migration.