Migrate from Aritic Sales CRM to Odoo CRM

Aritic Contacts map to Odoo res.partner records of type 'contact'. The primary Company association becomes the parent partner_id on the Contact. Aritic's flexible relationship model that lets any Contact link to any unrelated Company creates secondary associations we handle as additional Contact records (each Aritic-linked Company that is not the primary becomes a related partner record) and a custom field note aritic_secondary_companies__c storing the comma-separated list of additional Company IDs for manual verification post-migration.

Aritic Companies map to Odoo res.partner records of type 'company'. Company name, address, industry, and size map to name, address fields, industry_id, and company_size respectively. We import Companies first to establish partner_id references for downstream Contact imports. Multi-company records in Aritic that represent the same legal entity are consolidated into a single Odoo Company record with the aritic_source_id__c custom field holding the original Aritic Company ID.

Aritic Deals map to Odoo crm.lead records of type 'opportunity'. Deal name becomes opportunity name, amount maps to planned_revenue, and stage maps to stage_id. The Aritic pipeline assignment maps to an Odoo Team (crm.team) that we configure before migration. Closed-Lost and Closed-Won statuses translate to Odoo's Lost and Won stage states. Conversion probability from Aritic becomes a custom field probability_override__c since Odoo calculates probability automatically from stage unless overridden.

Each Aritic Pipeline becomes an Odoo Sales Team with its own Kanban stage sequence. We configure crm.team records during scoping and map Aritic pipeline names to team names. Within each team, Aritic pipeline stages become Odoo crm.stage records with their sequence order preserved. Automation triggers attached to pipeline stages in Aritic do not migrate and are flagged as workflow gotchas.

Aritic pipeline stages map to Odoo crm.stage records within the corresponding Sales Team. Stage names, sequence order, and win/loss criteria migrate directly. Stage-level automation triggers (automatic task creation, email sends, stage-change actions) do not transfer; we document each stage-level automation in the workflow inventory for Odoo Action Rules rebuild.

Aritic lead score values migrate as a custom integer field aritic_lead_score__c on the Odoo res.partner record. The numeric score at migration time is preserved; the active Aritic scoring model (rules, weights, criteria, auto-update triggers) does not export because it is stored in Aritic's proprietary automation engine. We provide a scoring-rule inventory sheet listing each rule's name, criteria, weight, and recommended Odoo Automated Action equivalent for the customer to rebuild.

Aritic activity records (call, email, meeting) map to Odoo mail.activity records linked to the target res.partner or crm.lead. Activity type, subject, date, duration (for calls), and body content migrate. Odoo's mail.activity model supports Today, Planned, and Overdue states. Meeting location and attendee information migrate as a note attached to the activity record. If Aritic activity records exceed 50,000, we chunk migration using Odoo's xmlrpc batch import with rate-limit handling.

Aritic Tasks map to Odoo project.task records linked to the corresponding crm.lead via the project_id context. Task title, description, due date, assignee (user_id), and completion status (stage_id) migrate. Completed task history preserves but activity log entries beyond the task record are not migrated. Task automation triggers (automatic creation on deal stage change, assignment rules) do not transfer and are flagged in the workflow inventory.

Aritic tags applied to Contacts and Deals migrate to Odoo tags stored in the crm.tag model. Tags are created as Odoo Tag records during import and linked to the crm.lead via tag_ids. Tags stored as multi-checkbox picklist values on Aritic custom properties are handled the same way. Segmentation rules built in Aritic (dynamic lists based on tag combinations and conditions) do not export and require rebuild as Odoo Automated Actions with domain filters.

Aritic Owners map to Odoo res.users records matched by email address. We extract every distinct owner_id referenced on Contact, Company, Deal, and Task and resolve against the destination Odoo instance's user table. Any Aritic Owner without a matching Odoo User is held in a reconciliation queue; the customer's Odoo admin provisions missing users before record import resumes. Inactive Aritic users are created as inactive Odoo users to preserve historical assignment.

Customer-defined custom fields on Aritic Contacts, Companies, and Deals are enumerated during scoping and pre-created in Odoo as custom ir.model.fields before migration runs. Field type mapping follows Odoo's type system: Aritic text fields become char/text, picklists become selection fields, numeric fields become float or integer, date fields become date. Any custom field with formula-type behavior in Aritic is flagged as requiring a computed field or onchange method in Odoo Studio.

Aritic File Manager documents linked to Deals or Contacts migrate as Odoo ir.attachment records linked via res_model and res_id to the corresponding res.partner or crm.lead. Files are downloaded from Aritic storage (or from referenced URLs if stored externally), organized by record ID, and re-uploaded to Odoo. URL-based attachments from expired external links are flagged as broken links in the migration report for the customer to resolve manually.