Migrate from Pure Chart to Odoo CRM

Pure Chart contacts map directly to Odoo res.partner. Partners of company type=false represent people; those with company=True represent organizations. The primary company link uses parent_id on res.partner — Pure Chart's primary-company flag drives which partner receives parent_id for proper hierarchy.

Pure Chart companies map to res.partner with company=True. Parent-child hierarchies in Pure Chart map to Odoo's parent_id on res.partner — the top-level company in a hierarchy has no parent_id set. Multi-company networks collapse to a flat partner tree with the hierarchy preserved via parent links.

Pure Chart deals become Odoo crm.lead records with type='opportunity'. The crm.lead model carries all opportunity fields — name, planned_revenue, probability, date_deadline — in one record. Pipeline association is indirect via crm.team membership, which Odoo derives from the sales team assigned to the record.

Pure Chart pipelines do not have a direct Odoo equivalent — each pipeline maps to a crm.team whose stage definitions (crm.stage) represent the pipeline stages. The crm.team record holds the sales team name and member list; the crm.stage records attached to that team define the Kanban columns visible in the pipeline view.

Pure Chart stage names map value-by-value to Odoo crm.stage records scoped to the target crm.team. Stage probability values map to the probability field on each stage. Custom stage names in Pure Chart require new crm.stage records to be created in Odoo before data import begins.

Pure Chart calls, emails, and meetings merge into two Odoo constructs: crm.activity holds the scheduled next activity (next_activity_id) and planned date, while mail.message stores the actual logged communication body with the original timestamp. Owner links map to Odoo res.users matched by email.

Pure Chart notes and file attachments map to Odoo ir.attachment records linked to the res.partner or crm.lead via the res_model/res_id pattern. Rich-text formatted notes in Pure Chart store as HTML in mail.message.body on the related record. Large attachments re-upload to Odoo's filestore under the attachment store path.

Pure Chart owner_id on every record resolves to Odoo res.users by email match. Unmatched owners are flagged before migration; their records receive a fallback user assigned during the migration plan phase. This prevents orphan records that would block Odoo record access rules from evaluating correctly.

Pure Chart custom objects require new Odoo ir.model definitions created before migration begins. Each custom object becomes its own Odoo model; N:N associations between custom objects and standard objects map to Odoo's rel-style ir.property or explicit many-to-many columns defined in the model.

Pure Chart quotes attached to deals map to Odoo sale.order records linked to the crm.lead via the opportunity_id field. Odoo sale.order.line items require an existing product.product catalog in Odoo — we flag missing products before migration so they can be created or the quote lines stored as notes.

Pure Chart tags migrate to Odoo crm.tag records and linked via crm.lead.tag_ids. Tags with no Odoo equivalent are created during migration setup. Tag names with special characters are sanitized to Odoo's name-cleaning rules for tag_id field compatibility in the target system.

Pure Chart campaigns that track deal sources map to crm.team as a sales-unit construct. If a campaign tracks marketing lists separate from sales pipeline, we store it as a crm.tag for reference and note that Odoo's native marketing automation apps handle list management separately in the marketing module.