Migrate from PlanPlus Online to Odoo CRM

PlanPlus Online Contacts map to Odoo res.partner records with is_company = False. The contact name, email, phone, mobile, street, city, state, zip, and country fields map directly. We preserve Franklin Covey priority quadrant assignments (urgent/important matrix) as a custom selection field on res.partner if present. Custom contact fields export as flat key-value pairs and map to custom res.partner fields we pre-create via Odoo's res.partner.fields API before migration. Owner (assigned user) maps to Odoo user_id via email match against Odoo's res.users table.

PlanPlus Online Company records map to Odoo res.partner with is_company = True. Company name becomes the partner's name field, industry maps to industry_id (from Odoo's industry classification), and website maps to website field. The contact-company linkage in PlanPlus Online becomes a parent_id reference on child res.partner records (contacts) pointing to the company res.partner. We preserve this via a mapping table assembled during the CSV export phase.

PlanPlus Online Deals map to Odoo crm.lead records. The deal name becomes the lead name, deal value maps to planned_revenue, and close date maps to date_deadline. Stage names (e.g., Prospect, Qualified, Proposal, Won, Lost) map to Odoo's stage_id within a configured sales team pipeline. We create a custom Odoo stage sequence matching PlanPlus Online's pipeline order before migration. Deals without a linked contact map as standalone leads; deals with a contact map with the contact_id resolved to the res.partner migration ID.

Each PlanPlus Online deal pipeline stage becomes an Odoo crm.stage record within a specific team. We configure the stage sequence, name, and fold status (is_won, is_unread) to match PlanPlus Online's pipeline view. Probability percentages from PlanPlus Online set the stage probability on each crm.stage.

PlanPlus Online calendar events (appointments, all-day events) map to Odoo calendar.event records. Start and end datetime, location, and description migrate directly. Attendee lists on PlanPlus Online events map to calendar.attendee records linked by email match against the migrated res.partner records. Time zone settings are normalized during export to avoid offset drift from the PlanPlus Online device sync issue documented in the source platform gotchas.

PlanPlus Online Tasks map to Odoo project.task records. Task name becomes the task title, description migrates to description, due date maps to date_deadline, and priority (high/medium/low) maps to priority. Subtasks map as child tasks via parent_id. If PlanPlus Online tasks are linked to Projects, they map to tasks under the corresponding Odoo project. If tasks exist without a project link, we map them to a default migration project created as a holding area for review. Franklin Covey priority quadrant values preserve as a custom field on the task.

PlanPlus Online Projects map to Odoo project.project records. Project name, description, and status (active/closed) migrate directly. Project milestones map as project.milestone records if Odoo's Timesheet app is activated. Task breakdowns within the project map as project.task records under the parent project. Project Summary Reports published as static webpages are captured as static HTML attachments on the project.project record rather than rebuilt as dynamic Odoo reports.

PlanPlus Online Users (Owners) referenced on Contacts, Companies, Deals, Tasks, and Projects map by email match against Odoo's res.users table. We extract all distinct owner IDs from the export dataset and reconcile against Odoo users before each import phase. Any PlanPlus Online Owner without a matching Odoo user goes to a reconciliation queue for the customer to provision the user before that phase of migration proceeds. Inactive PlanPlus Online users are flagged for the customer to decide whether to provision as inactive in Odoo.

PlanPlus Online custom fields export as flat key-value pairs in CSV. We map them to Odoo custom fields on the appropriate model (res.partner for contact/company custom fields, crm.lead for deal custom fields, project.task for task custom fields). Custom field types map to Odoo field types: text to char or text, number to float or integer, date to date, checkbox to boolean, dropdown to selection. Any custom field with no direct Odoo equivalent is flagged for manual review in the mapping document before import.

PlanPlus Online help desk tickets export with status, description, priority, and linked contact. If the customer activates the Odoo Helpdesk app, we map tickets to helpdesk.ticket records with the contact_id resolved to the migrated res.partner. Ticket status (open, pending, resolved, closed) maps to stage_id in the configured helpdesk team pipeline. If Helpdesk is not activated, tickets map to crm.lead with a custom ticket_type field to distinguish them from prospect leads.

PlanPlus Online FAQs from the Support Portal export as article records. They map to Odoo Knowledge (knowledge.article) if the customer activates that app, or as plain text notes attached to the relevant res.partner records if Knowledge is not in scope. FAQ ordering and category structure map as article tags in Odoo Knowledge.

PlanPlus Online sync connections to Google Calendar, Microsoft 365, and Outlook are authentication configurations that do not carry over to Odoo. We document which external systems were connected, the sync scope (calendar, contacts, tasks), and the last sync timestamp. The customer manually reconnects OAuth integrations in Odoo Settings after migration. This is not a data migration; it is a configuration handoff documented in the migration completion report.