Migrate from Panacea to Odoo CRM

Panacea stores client name, email, phone, and address directly on job records. We extract unique client records and create res.partner entries with type='contact'. If a client has multiple jobs, we deduplicate by email and create one partner record with the most recent job data merged in.

Panacea's supplier framework records map to res.partner with type='company'. Supplier name, domain, and category_id (industry) migrate as Odoo partner fields. If Panacea tracks supplier contact persons separately, those become child res.partner records linked via parent_id. We also migrate supplier rating or certification data as custom fields on the company partner record where present.

Each Panacea job becomes a crm.lead record. The job name maps to crm.lead.name, job status (Quote, Proof, Print, Delivered) maps to crm.stage via value_mapping, and the client contact from the job links to crm.lead.partner_id. Original job number preserved as x_panacea_job_ref custom field.

Panacea status values (New Quote, Awaiting Proof Approval, In Production, Delivered, Invoiced) map one-to-one to Odoo stage names. We create stages per Odoo team if Panacea has separate job queues. Probability values are assigned per stage using Odoo's stage probability field.

Panacea quote line items with product name, quantity, and unit price cannot map to Odoo sale.order without creating sale.order records first. We preserve line items as a JSON-formatted custom field (x_quote_lines) on the crm.lead and surface the data for manual import into Odoo Sale Quotation once the opportunity converts.

Panacea's supplier pricing calculators involve multi-dimensional matrices that have no Odoo native equivalent. We extract the active price matrix as a custom field (x_supplier_price_matrix) on the supplier's res.partner record. Rebuilding the calculator logic requires Odoo Python scripting or a third-party pricing app.

Panacea records proof uploads and approval events as activity entries. We migrate these as mail.message records linked to the corresponding crm.lead, preserving the original timestamp, author (from user email match), and message body. Odoo chatter displays these as activity timeline entries.

Panacea user records (sales reps, project managers) are matched to Odoo res.users by email address. Unmatched users are flagged and assigned to a fallback Odoo user (admin) with a custom field (x_original_owner) preserving the Panacea username for audit purposes. Role and permission levels from Panacea are documented in the migration reference document for manual Odoo access configuration post-migration.

Panacea job type values (Brochure, Business Card, Large Format, Packaging) migrate as a custom selection field (x_job_type) on crm.lead. Selection options are created in Odoo before migration to avoid import errors on the picklist field. Any job type values not matching predefined options are flagged for admin review and added to the selection list prior to data import.

If a Panacea job has a delivery address distinct from the client contact address, we create a separate res.partner address record of type='delivery' linked to the client's parent company partner. Odoo's address model supports multiple addresses per partner, allowing separate records for billing, shipping, and delivery locations. All address fields including street, city, state, and postal code are preserved during migration.

Panacea file attachments (proof PDFs, print-ready files) are downloaded and re-uploaded to Odoo as ir.attachment records linked to the corresponding crm.lead. File size limits follow Odoo's default 25MB per attachment. Inline images in notes are extracted and hosted as Odoo attachments.

Panacea internal notes on jobs migrate as Odoo mail.message records with message_type='notification' linked to the crm.lead. Original note body and create date are preserved. These appear in Odoo's chatter thread for the opportunity. Attachments referenced in notes are migrated separately as ir.attachment records and linked to the corresponding message thread.