Migrate from Plexus Software to Odoo CRM

Plexus Customer records map directly to Odoo res.partner. Plexus stores company name and primary contact in one object; during migration, FlitStack splits these into separate res.partner records — one with is_company=True for the organization and one for the primary contact — matching Odoo's partner architecture.

Plexus Customers flagged as billing contacts receive a dedicated res.partner record with the invoice address type. Odoo allows multiple address records per partner; the billing contact becomes a child address record rather than a separate partner, preserving the billing relationship without duplicating the company record.

Plexus Work Orders map to Odoo project.task records. The Odoo Project app must be enabled in the destination database before migration. Each Plexus work order becomes one task; Plexus job-line items map to project.task records under a parent task or to deliverable-based task descriptions. The original Plexus work order number is stored in task name or a custom reference field.

Plexus Employee records map 1:1 to Odoo hr.employee. Employee email in Plexus becomes hr.employee.work_email, which FlitStack uses to resolve owner assignment by matching against Odoo res.users.email. Unmatched employees are flagged before migration so your team can create Odoo user accounts first.

Plexus Time Entries migrate as Odoo analytic-account lines (account.analytic.line), which is the underlying data model for Odoo Timesheets. Each time entry is linked to the analytic account of the corresponding project.task derived from the Plexus work order. Original start/end timestamps, employee assignment, and billable/non-billable flags are preserved.

Plexus Quote records map to Odoo sale.order in draft state. Line items from the Plexus quote become sale.order.line records with product, quantity, and price_unit. Tax handling requires mapping Plexus tax configuration to Odoo fiscal positions and tax accounts during field-level validation.

Plexus Expense records migrate to Odoo hr.expense. Amount, description, employee assignment, and expense date transfer directly. Category or expense-type values from Plexus are mapped to Odoo hr.expense.sheet cost-center values via value_mapping during migration setup. The Plexus expense category strings such as mileage, materials, and meals map to corresponding Odoo hr.expense.product product records that carry the default account and tax configuration needed for accurate expense reporting.

Plexus custom fields like trade_type, license_number, or service_area_flag have no Odoo standard equivalent. FlitStack creates Odoo custom fields on res.partner (or project.task for work-order-specific fields) using Odoo Studio conventions before writing data. Custom field creation is confirmed with your Odoo admin during the schema-setup phase.

Plexus file attachments on work orders, customers, or quotes are downloaded and re-uploaded as Odoo ir.attachment records linked to the corresponding res.partner, project.task, or sale.order. File names and original upload timestamps are preserved as display metadata. Binary content is stored in Odoo's filestore directory.

Plexus workflow rules, dispatch automations, and schedule-triggered notifications have no Odoo equivalent at the data layer. FlitStack exports Plexus workflow definitions as a structured JSON reference document your Odoo administrator can use to rebuild equivalent rules in Odoo Studio or via Python automation scripts.

Plexus Owner fields on Work Orders and Customers resolve to Odoo res.users by email match. Plexus user accounts that do not have a matching Odoo res.users record are assigned to a fallback owner designated by your team before the full migration run commits.

Plexus Schedule records with start/end dates and assigned employees map to project.task planned_date_start and date_deadline fields. The Odoo Project Planning (/planning) module uses these fields to generate shift calendars. If full scheduling-board fidelity is required, FlitStack can also populate the calendar.planning_slot model but this requires the Planning app to be installed.