Migrate from OctopusPro to Odoo CRM

OctopusPro Customer records map to Odoo res.partner. The customer type (individual vs business) maps to Odoo's is_company flag. Address, phone, email, notes, and custom fields migrate directly. Odoo's partner record serves as both Contact and Account equivalent; commercial relationships use parent_id for hierarchical structures. We use email as the dedupe key during import and flag any duplicate partner records for customer review.

OctopusPro Bookings do not have a direct Odoo CRM equivalent. We map each Booking to an Opportunity (crm.lead) record, encoding booking metadata — service type, scheduled date and time, status, assigned field workers, and service address — into custom fields on the Opportunity. The original Booking ID is preserved in a custom field octo_booking_id__c for audit. Completed bookings with invoices become Closed Won opportunities; cancelled bookings become Closed Lost. This approach preserves the booking history while fitting within Odoo's pipeline model.

OctopusPro Field Worker records map to Odoo hr.employee records (for HR and timesheet context) and optionally res.users records (if the field worker also accesses Odoo CRM). We map by email match, flagging any field worker without a matching Odoo user for admin provisioning. Pay rates and location tracking preferences from OctopusPro are stored in custom fields on hr.employee.

OctopusPro Invoices map to Odoo account.move records in the out_invoice state. Invoice line items migrate as invoice lines with account_id, quantity, unit_price, and tax mapping resolved at migration time. Payment status (paid, partial, overdue) maps to Odoo's payment_state field. We resolve the customer partner_id from the Customer mapping and link each invoice to the related Opportunity via a custom field on account.move.

OctopusPro Payment records map to Odoo account.payment entries linked to the corresponding account.move invoice. Payment method, amount, date, and status migrate directly. Partial payments and refunds are preserved as separate account.payment records with negative amounts for refunds. Reconciliation runs post-import to match payments to invoices in Odoo's reconciliation module.

OctopusPro Quotes map to Odoo sale.order records in draft (quotation) state. Quote validity dates, line items, pricing, and accept/reject status migrate as Odoo quotation data. Accepted quotes are flagged for conversion to Sales Order; rejected quotes remain as cancelled or lost quotations. We resolve the customer partner_id and product lines at migration time.

OctopusPro Service definitions map to Odoo product.product records. Service name, description, base pricing, and duration migrate as product name, description, list_price, and a custom duration field. Odoo product variants handle service options and zone-based pricing from OctopusPro's custom field rates.

OctopusPro tenant-specific custom fields on Customer and Booking objects require schema discovery during scoping. We request a full field inventory from OctopusPro support and create equivalent Odoo custom fields via Studio or developer-mode field creation before data migration. Custom field type mapping (text, number, date, selection, multi-select) is resolved per field during scoping, and fields without an Odoo equivalent are flagged for manual recreation or approximation.

OctopusPro form and checklist data attached to bookings is captured as structured key-value pairs in custom fields on the corresponding Odoo Opportunity. Schema varies by service type; we map available fields during scoping and create custom fields to hold intake data. Photos and attachments migrate as Odoo ir.attachment records linked to the Opportunity.

OctopusPro Customer Portal is a configuration layer (booking access, invoice viewing, payment links, FAQ display) that does not store data independently. We do not migrate portal settings. The underlying Customer, Booking, Invoice, and Quote data that the portal surfaces migrates to Odoo. The customer's admin reconfigures a partner portal in Odoo Website or Odoo.sh using migrated data.

OctopusPro automation rules define trigger-action workflows for notifications, scheduling, and status changes. We capture the automation rule inventory during scoping and deliver a written map of every active automation with its trigger conditions, actions, and Odoo equivalent (Server Action, Automated Action via Odoo Studio, or ir.actions.server). Odoo automations use a different execution model from OctopusPro and are not migrated as code.

OctopusPro GPS fieldworker location tracking is runtime operational data that has no long-term value post-migration and no equivalent native storage in Odoo CRM. We do not migrate GPS tracking history. If the customer activates Odoo Field Service, real-time location tracking is enabled through the Field Service mobile app rather than migrated from OctopusPro.