Migrate from ForceManager CRM to Odoo CRM

ForceManager Companies map to Odoo Res.Partner records with the is_company checkbox enabled. The ForceManager company name maps to Odoo's name field; phone, email, website, address, and rating fields map to their Odoo equivalents. We set partner_latitude and partner_longitude from ForceManager GPS coordinates if available, enabling Odoo's geo-codable address model. Company-type z_ fields are recreated as Odoo custom fields on res.partner via Studio before import.

ForceManager Contacts map to Odoo Res.Partner records with is_company disabled and a parent_id reference to the mapped Company Partner. We resolve the parent_id by matching the ForceManager company_id on the Contact to the imported Company Partner. Contact title (Mr./Ms./Dr.) maps to res.partner's title field; job_title maps to function. Z-prefixed custom Contact fields are recreated on res.partner and populated during the Contact import phase.

ForceManager Opportunities map to Odoo crm.lead records. The opportunity's stage maps to Odoo's stage_id with stage names translated from ForceManager pipeline stages to Odoo CRM stage names during the transform step. Expected revenue and probability map to Odoo's expected_revenue and probability fields. partner_id (the customer) is resolved by matching the Opportunity's linked Company to the imported Partner. lead_id is set for Leads; opportunity_id is set for qualified Opportunities.

ForceManager deal pipelines map to Odoo Sales Teams (crm.team). Each ForceManager pipeline becomes an Odoo crm.team record, and the pipeline's stage set becomes the Odoo team's stage_ids. Stage probability percentages from ForceManager map to Odoo's stage probability values. If ForceManager has multiple pipelines with distinct stage sets, each becomes a separate crm.team in Odoo.

ForceManager call Activities map to Odoo mail.activity records with activity_type_id set to the built-in 'Call' type. Duration, outcome, and notes from ForceManager map to Odoo's note field as structured text. The activity is linked to the Odoo res.partner or crm.lead record that corresponds to the ForceManager Contact or Opportunity. Activity date and owner are preserved from the ForceManager timestamp and owner_id.

ForceManager meeting Activities map to Odoo calendar.event records. Start datetime, end datetime, location, and attendee list are preserved. The ForceManager GPS location from field visits is stored in the event's description field as structured metadata (latitude/longitude). Meeting-linked Contacts resolve to Odoo partner_ids on the event via the attendee mapping.

ForceManager Activity notes map to Odoo mail.message records with message_type='comment' posted on the relevant res.partner or crm.lead. The note body migrates as the message body; attachments on the ForceManager note are flagged as manual export items because the attachment API endpoint is inaccessible. We preserve the note creation timestamp as mail.message's date field.

ForceManager Calendar Events map to Odoo calendar.event records separately from meeting Activities. The event name, date/time, location, and GPS coordinates migrate directly. Attendee associations from ForceManager Events become Odoo calendar.attendee records linked to the event, with each attendee mapped to the corresponding Odoo res.partner by email match.

ForceManager Tasks map to Odoo project.task records within a dedicated CRM project (project.project) that we provision during schema setup. Task status (open/closed) maps to Odoo stage_id within the project. Due date, assignee (owner), and priority migrate directly. Closed tasks retain their completion date in Odoo's date_last_stage_update field.

ForceManager Sales Order and Sales Order Line entities map to Odoo sale.order and sale.order.line. The order header (customer, date, currency, totals) maps to sale.order fields; line items (product, quantity, price) map to sale.order.line with the product resolved via SKU match to Odoo's product.product. If the destination Odoo instance does not include the Sale module, we map Sales Order data as custom fields on crm.lead for the customer's admin to migrate to sale.order manually.

ForceManager Users map to Odoo res.users records via email match. Owner assignments on Companies, Contacts, and Opportunities reference ForceManager user IDs that we resolve to Odoo user IDs during the import phase. Users without a matching Odoo account are held in a reconciliation queue; the customer's Odoo admin provisions missing users before record import resumes. Active/inactive status is preserved from ForceManager.

All ForceManager custom fields with z_ prefix are recreated as Odoo Studio custom fields on the relevant model (res.partner for Contact/Company custom fields, crm.lead for Opportunity custom fields). We query ForceManager's Fields endpoint during extraction to capture label-to-prefix mappings, then create Odoo fields with human-readable internal names. Field types are mapped: z_text maps to char, z_number to float or integer, z_date to date, z_checkbox to boolean, z_picklist to selection.

ForceManager Views (saved list filters) are configuration rather than data. We document the filter structure, field criteria, and sort order for each active view during scoping. These are not migrated as executable records; we provide a written guide for recreating the equivalent Odoo custom filters and list views in the CRM dashboard. The customer's admin recreates views manually in Odoo's filter and grouping interface.

ForceManager List membership (static and dynamic segments) is reconstructed in Odoo as crm.tag records applied to the relevant res.partner and crm.lead records. Dynamic lists (filter-based membership) do not migrate as live filters; we document the filter logic so the admin can recreate the equivalent Odoo segmentation via Custom Filters or domain-based searches.

ForceManager Workflows are Business-tier-gated and are not exposed via the public REST API. They cannot be extracted or migrated as automation logic. We document every active ForceManager workflow during scoping, capturing its trigger condition, action steps, assignment rules, and stage-transition logic. This inventory is delivered as a written handoff for the customer's Odoo admin to rebuild in Odoo Automated Actions (available at all Odoo tiers). Workflow documentation includes the ForceManager trigger type and the recommended Odoo Automated Action equivalent.