Migrate from Planports CRM to Odoo CRM

Planports Leads map to Odoo crm.lead records. We extract the full field set including source attribution (Meta Instant Form, Google Ads, TikTok), assignment rules, and status. The Planports lead score and custom fields (health tourism referral source, real estate lead type, digital agency campaign tag) transfer as custom Char or Selection fields in Odoo after the customer installs a custom module defining those fields on the crm.lead model.

Planports Contacts map to Odoo res.partner records. Standard fields (name, email, phone, company) migrate directly. The WhatsApp phone number stored on the Contact card transfers to res.partner's phone or mobile field, but the full WhatsApp conversation thread (stored in Meta's infrastructure) cannot be extracted via Planports export and is not migratable. We document the limitation and recommend re-authorizing the WhatsApp Business API channel in Odoo post-migration.

Planports Deals map to Odoo crm.lead records in the opportunity stage. The Planports pipeline stage (e.g., Qualified Lead, Proposal Sent, Negotiation) maps to an Odoo CRM Stage ID that we configure during schema setup. Industry-specific pipeline stages (health tourism treatment stage, real estate viewing schedule stage) require custom stage creation in Odoo's CRM pipeline configuration before migration. We preserve the Planports deal value, expected close date, and loss reason as crm.lead fields.

Each Planports pipeline becomes an Odoo CRM Stage within the Pipeline. We create stages in the same order, with matching probability percentages, and assign them to the CRM pipeline view. If Planports uses multiple parallel pipelines, we configure multiple Odoo CRM pipelines (or a single pipeline with stage groups) to match the customer's deal management structure. Color and sequence order are preserved.

Planports Quotes map to Odoo sale.order records in draft state. Line items migrate as sale.order.line records with product reference, quantity, and unit price. Approval status from Planports transfers as a note or custom state flag on the sale.order because Odoo's standard quote approval flow is a separate configuration. Quote validity dates migrate to sale.order.validity_date.

Planports Orders map to Odoo sale.order records with state set to sale (confirmed). The linked Contact (Planports) maps to the sale.order partner_id (res.partner). Order status, quantities, and linked Deal reference migrate as order lines and a note field. Financial settlement and payment data may require accounting-specific review if the customer uses Odoo Accounting; we flag this for the customer's admin during scoping.

Planports Activities (calls, emails, meetings, tasks) map to Odoo mail.message records linked to the parent crm.lead or res.partner. Call duration and disposition migrate to custom fields on the mail.message record. Meeting scheduling migrates to mail.event with start and end timestamps. Task status, priority, and due date migrate to the Odoo standard task structure. Activity timestamps are preserved for timeline ordering.

Planports Notes attached to Contacts or Deals migrate as Odoo mail.message records with message_type = comment. The note body migrates as HTML-formatted mail.message.body. We link each note to the parent res.partner or crm.lead via res_id and model. If the customer uses Planports Notes as standalone records not attached to a parent, we map them to a dedicated Odoo note.pad configure note project or a generic mail.activity record.

Planports Process boards map to Odoo project.task records under a dedicated project per board. Each Kanban column becomes a project.task.stage. Card records migrate as task records with the original stage assignment preserved. Conditional automation rules attached to columns do not migrate; we inventory every Process board rule during discovery and deliver a written handoff document for the customer admin to rebuild in Odoo Project automation. The Process board structure (column count, card order, assignment rules) is recreated manually in Odoo Project or via a project configuration script.

Planports industry-specific custom fields (health tourism treatment packages, real estate property IDs and viewing schedules, digital agency campaign IDs and ad spend) require an Odoo custom module to persist because Odoo does not expose dynamic custom field creation on standard models without developer mode or a custom addon. We audit every custom field during the pre-migration data review, document the field name, data type, and picklist values, and deliver a field specification for the customer's Odoo developer to install as a custom module before the production data load. Without this module, custom field values are not migratable.

Files uploaded to Planports Contact or Deal cards can be exported individually per record. Bulk attachment migration from Planports requires API access ($62/month add-on) and may be limited by plan tier. We extract files as binary blobs and attach them to the corresponding Odoo res.partner or crm.lead record via ir.attachment. If Planports attachment count is large (over 500 files), we batch the import and validate attachment-to-record linkage during the staging migration phase.

Planports Users map to Odoo res.users records. We resolve owners by email match across Planports Contacts, Deals, Activities, and Notes. Any Planports user without a matching Odoo user account goes to a reconciliation queue for the customer's admin to provision before the production load. Deal ownership, activity attribution, and note ownership transfer as Odoo res.users references, preserving the original rep attribution on crm.lead and mail.message records.