Migrate from Clientjoy to Odoo CRM

Clientjoy Leads map to Odoo crm.lead records. We use crm.lead fields (contact_name, email_from, phone, street, city, country, description) with Clientjoy custom field values mapped to Odoo custom fields created via Studio before import. Any Clientjoy Lead with a status indicating it has been qualified or converted maps to crm.lead with the won status; unqualified Leads remain as crm.lead with the new or qualifier stage. Original Clientjoy lead source is preserved in a custom field for reporting continuity.

Clientjoy Customer records map to Odoo res.partner with address and contact details preserved. The Clientjoy Customer's email, phone, company name, and billing address map to res.partner fields (email, phone, name, street, city, zip, country). For B2B contexts where the Customer represents an organization rather than an individual, we create a res.partner of type company with the person's contact details on a related res.partner record of type contact.

Clientjoy pipeline stage definitions are exported via the API and re-created in Odoo as crm.stage records within the relevant crm.team. Stage names, sequence order, and probability percentages carry over. Clientjoy's pipeline-level lead scoring maps to a custom float field on crm.lead created in Odoo Studio before migration. If multiple Clientjoy pipelines exist (Agency tier), we create corresponding crm.team records in Odoo and scope stages per team.

Clientjoy invoices (one-time and recurring) map to Odoo account.move records in the Odoo Accounting module. We export invoice headers, line items, tax rates, currency codes, and payment status. Recurring invoice schedules are preserved as metadata in a custom field on account.move so the customer's accountant can re-create the recurrence rule in Odoo Accounting. The Odoo Accounting app must be installed and configured before invoice import; we confirm this during scoping. Multi-currency invoice amounts map to account.move with the original currency stored per Odoo accounting standards.

Clientjoy document templates with merge fields are exported as raw content and field association metadata. Odoo uses QWeb templates for reports and documents, which is a different rendering engine from Clientjoy's template system. We deliver the exported template content and field mapping table as a written handoff document; rebuilding templates as Odoo QWeb reports is a configuration task for the customer's Odoo admin or a developer. The document builder reliability issues documented on Clientjoy mean that we recommend a fresh template build in Odoo rather than attempting a direct template translation.

Clientjoy custom field definitions (available on Agency plan and above) are exported with field names, types (text, dropdown, date, number), and all populated values. We create corresponding Odoo custom fields via Odoo Studio before data import, matching field types as closely as possible (text to char, dropdown to selection, date to date, number to float or integer). Fields gated to the Agency plan on Clientjoy are noted during scoping; Starter-plan accounts would not have custom field data to migrate.

Clientjoy Email Sequences (steps, timing rules, trigger conditions) are exported as a structured configuration table with step order, delay, template content, and trigger event. Odoo does not have a native sequence cadence model; the replacement pattern is mail.template for email content and ir.actions.server for automated trigger logic built in Odoo Studio. We deliver the Email Sequence inventory as a written document with each sequence mapped to a recommended Odoo mail.template plus server action combination, and the customer's admin configures the automation post-migration.

Clientjoy Client Portal configurations including white-label settings, custom domain, CSS styling, and embedded widgets are exported as configuration data. Odoo's portal functionality is tied to the Odoo Website and Website Portal modules. We export the portal settings and page structure as a written configuration inventory; white-label settings, custom domain, and portal styling require manual reconfiguration in Odoo Website settings by the customer's admin. Clientjoy's Agency plan branding removal (removing 'Powered by Clientjoy') does not have a direct Odoo equivalent but is handled by Odoo's white-label hosting options on the Custom plan.

Clientjoy appointment records migrate as Odoo calendar.event with date, time, invitee, duration, and status preserved. Booking page configurations (available times, appointment types, location or meeting link) are exported as a configuration table and re-created in Odoo via the calendar.appointment module. The Odoo Appointment feature requires the calendar app and optionally the website app for public booking pages, both of which are standard Odoo modules available from Standard tier.

Clientjoy web form definitions and field mappings are exported as a form schema with field labels, types, and required flags. Odoo replaces web forms with the website.form module and website.form.configurator, which map submitted data to crm.lead or custom models. We deliver the form field mapping as a written configuration document. Form-to-Lead field routing is preserved in the mapping table so leads submitted post-migration route to the correct Odoo model.

Clientjoy Owner records map to Odoo res.users by email match. We resolve Clientjoy hubspot_owner_id equivalents to Odoo res.users id during import. Any Clientjoy Owner without a matching Odoo res.users record enters a reconciliation queue for the customer's admin to provision the User before record import resumes.

Clientjoy engagement records (calls, emails, meetings, tasks, notes) map to Odoo's mail.message thread on the relevant crm.lead or res.partner record, with calendar.event for meeting records and project.task for task records. Email content, call duration, meeting attendee lists, and task status all transfer to Odoo's chatter and calendar. Activity timestamps are preserved to maintain the chronological activity timeline on each crm.lead record. Note that Odoo Community does not include a native call recording attachment store; we migrate call metadata but not recording files unless Odoo VoIP or a third-party telephony module is installed.