Migrate from Claritysoft to Odoo CRM

Claritysoft Contacts map to Odoo res.partner records with partner_type = 'contact'. We preserve first name, last name, email, phone, mobile, and street/city/state/zip/country address fields. The Claritysoft Account (company) association maps to a parent res.partner record with partner_type = 'company', and the Contact maps as a child of that company partner. We deduplicate on email address during import and flag any duplicates for customer review before commit.

Claritysoft Accounts map to Odoo res.partner with partner_type = 'company'. Company name, website, industry, annual revenue, phone, and address fields migrate directly. We use the Claritysoft Account name as the res.partner display name and the domain from the website field as a secondary dedupe key if email deduplication yields no match.

Claritysoft Leads with lifecycle stages (New, Contacted, Qualified) map to Odoo crm.lead records with type = 'lead'. The Claritysoft lead_status property maps to Odoo stage_id assignment. Any lead score or qualification rating stored in Claritysoft custom fields migrates to a custom Char or Integer field on crm.lead that we define during schema setup.

Claritysoft Opportunities map to Odoo crm.lead with type = 'opportunity'. Fields that map directly: name (deal name), planned_revenue (amount), probability (from Claritysoft probability %), stage_id (from Claritysoft pipeline stage), expected_closing_date (expected close date), and description. We resolve the linked Claritysoft Account to an Odoo res.partner partner_id and the Claritysoft Owner to an Odoo res.users user_id at migration time.

Each Claritysoft pipeline becomes an Odoo Sales Team (crm.team) with its own crm.stage sequence. We preserve stage names, display order, and probability percentages as Odoo stage attributes (sequence, probability). If Claritysoft uses multiple pipelines, we create one Odoo crm.team per pipeline and assign stages to the corresponding team.

Claritysoft Activities (Tasks, Calls, Meetings with timestamps and owners) map to a combination of Odoo mail.message records (for the activity body and metadata) and project.task records (for actionable tasks with due dates). Calls and Meetings with specific start/end times migrate as calendar.event records. All activity parent references resolve to the linked crm.lead or res.partner at migration time.

Claritysoft Documents attached to Contact, Account, Lead, or Opportunity records migrate to Odoo ir.attachment linked via res_model and res_id to the corresponding crm.lead or res.partner. We extract file binary content, preserve the original filename, and set the attachment's res_field to the Odoo field name that holds the attachment reference.

Claritysoft custom fields (text, number, date, picklist, checkbox, calculated) on Contacts, Accounts, Leads, and Opportunities map to Odoo ir.model.field definitions that we create during schema setup. We map Claritysoft field types to Odoo field types (Char, Integer, Float, Date, Selection, Boolean, Many2one). Calculated Custom Fields on Claritysoft Accelerator/Enterprise do not migrate as logic; we migrate the last-calculated value as a static field and document the calculated field definition for rebuild in Odoo Studio.

Claritysoft Custom Modules (available on Accelerator and Enterprise tiers) map to Odoo custom models via ir.model. We create the Odoo model definition, add all custom fields as ir.model.field records, and import the module data into the corresponding Odoo table. Custom Modules are only migratable if the source account is on Accelerator or Enterprise; Professional-tier accounts must first upgrade or accept that Custom Module data cannot be accessed via API.

Claritysoft Projects (available on Accelerator and Enterprise) map to Odoo project.project. Project name, description, start date, deadline, and status migrate directly. Project tasks migrate to project.task linked to the parent project. We resolve Claritysoft task assignees to Odoo res.users by email match.

Claritysoft Helpdesk Tickets (Accelerator and Enterprise) map to Odoo helpdesk.ticket with title, description, priority, status, and assignee fields. Ticket conversation threads migrate as mail.message records linked to the ticket. Custom ticket fields map using the same ir.model.field approach as other custom objects.

Claritysoft Users who own records map to Odoo res.users by email match. We generate a user mapping table and flag any Claritysoft Owner without a matching Odoo User for the customer's admin to provision. The Claritysoft Access Profile and User Group model has no direct Odoo equivalent; we document the profile-to-Odoo security group mapping for the admin to configure post-migration in Settings > Users > Access Rights.