Migrate from Perfectview to Odoo CRM

PerfectView Relation is the primary migration object and conflates organisation and individual contact data into a single entity. We split each Relation into two Odoo res.partner records: one with is_company=True (the organisation) and one with is_company=False (the individual). Role fields inside the Relation determine contact placement; address fields become the organisation address. When a Relation contains only a company with no individual contact, we create only the Company record. We validate the split against a sample of 200-500 records before bulk migration to avoid creating orphaned or duplicate partners.

PerfectView Activities (calls, emails, meetings, tasks) are well-structured and timestamped. They map directly to Odoo's mail.activity model with type field (call, email, meeting, task) preserved. Owner assignment maps to Odoo res.users by email match. Activity date and deadline migrate as activity_date_deadline. Linked Relation references are resolved to the split res.partner records after the Relation split is complete.

PerfectView Lead tracking (whether implemented as a distinct object or a Relation lifecycle stage) maps to Odoo crm.lead. Lead status values from PerfectView map to Odoo stage_id values via a stage mapping table created during scoping. Lead source maps to Odoo's source_id (utm.source). When the source field references a Relation, we resolve the parent res.partner after the Relation split.

PerfectView complaint management and support tickets map to Odoo helpdesk.ticket, which requires the Helpdesk app to be installed in the destination Odoo instance. Case status and priority migrate to ticket stage_id and priority fields. Conversation history inside PerfectView Cases migrates as mail.message records linked to the ticket. If the customer does not license the Helpdesk app, Cases map to crm.lead with a custom ticket_type field as a fallback.

PerfectView document storage migrates to Odoo ir.attachment records linked to the parent res.partner (for company documents) or crm.lead (for lead documents). Document metadata (filename, MIME type, size, created date) migrates from the PerfectView export. We retrieve documents via PerfectView's API where enabled, falling back to UI-based bulk export for bulk downloads. Odoo stores attachments in its database (filestore) by default; large attachment volumes may require the Odoo documents app for a file-system storage backend.

PerfectView Quotes migrate to Odoo sale.order records in draft state. Quote line items migrate as sale.order.line records with product_id resolved to Odoo product.product entries. Quote pricing and currency migrate as order_line with price_unit and discount fields. Quote-to-Relation links are resolved to res.partner after the Relation split. If the Odoo Sale app is not installed, we flag this during scoping as a prerequisite.

PerfectView invoice records migrate to Odoo account.move (with move_type=out_invoice for sales invoices) under the Odoo Accounting module. Invoice line items migrate as move_line records. Payment status from PerfectView (paid, open, cancelled) maps to Odoo payment_state field. Invoice numbers may need renumbering in Odoo due to sequence constraints in the accounting journal; we flag this before migration and the customer's accountant confirms the sequence configuration. This mapping is only available if the Odoo Accounting app is active.

PerfectView User records and owner assignments on Relation, Activity, Case, and Quote records migrate to Odoo res.users. We resolve owners by email match. Any PerfectView Owner without a matching res.users in the destination Odoo instance is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive PerfectView users map to Portal users (res.users with share=True) if the customer wants to grant the contact read-only access to their account.

Custom fields added to Relations in PerfectView are discovered during the discovery phase via export inspection. We pre-create the equivalent custom fields in Odoo using Developer Mode or an XML data file before migration. Field types are mapped (PerfectView text to Odoo char, PerfectView number to Odoo float or integer, PerfectView date to Odoo date). Selection fields in PerfectView become selection fields or many2one relations in Odoo depending on the number of distinct values.

PerfectView workflow rules, trigger conditions, and automated sequences are not publicly exportable through any PerfectView mechanism. We document all active workflows during the discovery call and deliver a written inventory with trigger, conditions, actions, and recommended Odoo Studio or ir.actions.server equivalent. Workflow reconstruction in Odoo is outside the data migration scope and should be handled by the customer's Odoo administrator or a certified Odoo partner as a separate engagement.

PerfectView Relations can contain multiple contact individuals with distinct roles (CEO, Sales Manager, Billing Contact). After splitting the Relation into a Company and individual Contact records, we preserve the role by linking the individual Contact to the Company via the parent_id field on res.partner. If multiple individuals share the same role, we create additional Contact records. Role labels from PerfectView are stored as a custom field on the individual Contact.

PerfectView stores email threads and communication history linked to Relations. These migrate to Odoo mail.message records attached to the parent res.partner (for company-level communications) or crm.lead (for lead-level communications). Email content and timestamps migrate intact. Attachments within communications migrate as ir.attachment records linked to the mail.message.