Migrate from AllClients to Odoo CRM

AllClients Contacts map directly to Odoo res.partner records of type 'contact'. The Contact's email becomes the partner's email field and serves as the dedupe key during import. First name, last name, phone, address fields, and owner assignment migrate to the equivalent Odoo partner fields. AllClients Tags embedded in the contact row are parsed and applied as Odoo partner tags after the base record insert so that the contact is available for tag assignment on the same migration pass.

AllClients Notes export as a separate Notes.csv that must be rejoined to the main Contact CSV before Odoo import. We use contact email as the primary join key and AllClients record ID as a fallback where email is missing or changed. Each Note becomes a mail.message record posted to the res.partner's Chatter thread with message_type = 'comment', preserving the original note body and timestamp. Note records without a matching contact after the join are held in a review queue for manual resolution.

AllClients Custom Field definitions discovered via the UpdateCustomFields API during scoping map to custom ir.model.fields entries on the res.partner model in Odoo. Field types are mapped: text fields become char or text, numeric fields become float or integer, date fields become date. Custom field values from the AllClients contact export are written to the corresponding Odoo custom field after the res.partner record is created. Multi-value custom fields (e.g., checkbox groups) map to Odoo many2many tags or selection fields depending on value cardinality.

AllClients Tags applied to contacts are embedded in the contact CSV export as comma-separated values. We parse the tag list for each contact and create corresponding res.partner.category records in Odoo if they do not already exist, then create res.partner.category.rel records linking the contact to each tag. Tags used for group membership are distinguished from content-classification tags and preserved with a category prefix so the customer can filter by source after migration.

AllClients Groups have no independent export — group membership is established by filtering the contact export by group name. We capture group membership for each contact as a named tag (group name prefixed with 'Group:') applied to the Odoo res.partner record. If the customer requires formal Odoo Sales Teams, we materialize the group-to-owner relationship: each AllClients Group maps to an Odoo crm.team, and contacts in that group are assigned to the corresponding team lead (mapped from the AllClients Group's owner).

AllClients Users are captured from the admin export with Name, Email, and role/permissions. We match each AllClients Owner referenced on a Contact record by email to an existing Odoo User record. If the Odoo destination does not yet have a matching User for an AllClients owner, the contact is temporarily assigned to the migration admin and flagged for the customer's Odoo admin to provision the User record before final owner_id resolution. Active vs inactive status maps directly.

AllClients Email Templates stored under the Email Marketing section export as HTML blobs. We import them into Odoo's mail.template model with the original HTML preserved as body_html. Inline image references that point to AllClients-hosted URLs are flagged for the customer to re-host or upload to Odoo's ir.attachment storage; we document each external URL for manual follow-up. Template subject lines map to subject field, and name maps to name.

AllClients Campaigns represent scheduled email sends linked to contact segments. Campaign names and linked segment definitions migrate as named Odoo crm.tag records. Campaign history (send dates, open rates, click rates) is metadata attached to the campaign record rather than a discrete relational object in AllClients and cannot be programmatically extracted, so we document the known campaign names and segment sizes for the customer's admin to recreate in Odoo's email marketing or CRM campaign model.

AllClients Tasks and Follow-up Reminders export from the Tasks section with title, due date, completion status, and owner assignment. We map them to Odoo crm.activity records with activity_type derived from the task category (call, email, meeting, generic). Completed vs pending status maps to Odoo's activity_date_done field. Tasks created as part of AllClients Workflow sequences are migrated as standalone crm.activity records; the workflow automation itself does not carry over.

AllClients file attachments associated with Contact records are downloaded from AllClients storage and re-uploaded to Odoo's ir.attachment model with res_model = 'res.partner' and res_id pointing to the migrated contact record. Binary files over 10 MB are chunked for download and upload to stay within typical HTTP timeout thresholds. Attachments with no parent contact after the migration (orphaned files) are flagged for manual review.

AllClients Landing Pages and Popup Forms are available on Premium and Elite tiers but are not exposed via the AllClients API or export tools. HTML content, form field definitions, and submission data cannot be programmatically extracted. We skip these objects and flag them during scoping so the customer is aware they must rebuild landing pages and forms in Odoo's Website builder or Forms module post-migration.

AllClients Workflow definitions (triggers, conditions, actions, delays) are captured during scoping as a JSON-serialized template. Execution state — which contacts are enrolled, which steps have completed, historical run data — is not available via AllClients export or API and cannot be migrated. We deliver the workflow definitions as a written configuration inventory with a description of each trigger, condition branch, and action for the customer's Odoo admin to rebuild as Odoo Automated Actions or Studio Workflows. Contacts enrolled in active workflows at migration time are not automatically re-enrolled; we recommend a manual high-priority re-enrollment process post-migration.