Migrate from Atendare to Odoo CRM

Atendare Contacts with no associated Deal and no customer lifecycle stage map to Odoo Lead. Contacts with associated Deals, customer lifecycle stages, or historical transaction data map to Odoo Contact attached to an Odoo Account. We apply the split rule during extraction, preserve Atendare segmentation tags as Odoo Tags on the Lead or Contact record, and store the original Atendare contact ID in a custom field for cross-system reference. The split rule is defined during discovery based on the customer's Atendare lifecycle configuration.

Atendare Company records map directly to Odoo CRM Account. The Atendare company domain name populates the Account website field, and the company CNPJ or CPF identifier (common in Brazilian Atendare deployments) maps to a custom field in Odoo. We resolve the Account-Contact relationship during migration so that each Contact references its parent Account. If multiple Atendare Companies share the same domain, we create one Odoo Account with multiple Contact records.

Atendare Deals map to Odoo CRM Opportunity. The Deal value (amount), expected close date, stage name, and owner assignment migrate directly. Deal custom fields map to Odoo custom fields on the Opportunity object. The Atendare pipeline assignment maps to an Odoo Sales Team or pipeline-stage combination depending on how the Odoo destination is configured during schema design.

Atendare pipelines with named stages map to Odoo CRM pipeline configuration with stage names, sequence ordering, and probability percentages carried over. If the customer uses multiple Atendare pipelines for different lines of business, we create separate Odoo Sales Teams and assign each team to its corresponding pipeline. Stage probabilities migrate as Odoo stage probability values.

Atendare activities (calls, meetings, tasks) linked to Contacts or Deals map to Odoo CRM Activities. Meeting-type activities become Odoo Calendar Events with start and end datetime preserved. Task-type activities become Odoo Tasks with status (todo, in progress, done), priority, and owner assigned from the Atendare activity owner. Activity timestamps are preserved to maintain the historical timeline in the Odoo Activity view.

Atendare team members and deal owners map to Odoo Users by email address. We extract all distinct Atendare user references from Contacts, Companies, Deals, and Activities and resolve them against the destination Odoo User list by email. Users without a matching Odoo account enter a reconciliation queue for the customer's admin to provision before the migration phase that requires owner assignment resumes.

Atendare custom fields on Contacts, Companies, and Deals are detected during discovery and mapped to Odoo custom fields created via Odoo Studio before migration. Field types are matched: text properties become Odoo char or text fields, date properties become Odoo date fields, numeric properties become Odoo float or integer fields, and multi-select properties become Odoo tags or char fields with comma-separated values. We flag any Atendare custom properties with no Odoo equivalent for the customer's admin to resolve post-migration.

Atendare Proposals and Contracts (Enterprise tier only) map to Odoo CRM Quotations where accessible via confirmed API endpoints or exported documents. Quotation line items, totals, and status migrate as Odoo sale.order records. PDF attachments from Atendare Proposals are flagged as document attachments for manual upload to the corresponding Odoo Quotation record since document binary handling requires separate file processing.

Atendare Product Catalog entries (product names, SKUs, descriptions, and pricing) map to Odoo Product records. Product-to-Deal associations are preserved by linking the Odoo Product to the corresponding Odoo Opportunity Line Item created during the Deal migration phase. If Atendare pricing tiers apply per product, we store the pricing logic in a custom field on the Odoo Product for the admin to configure in Odoo's pricelist rules.

Atendare contact segments defined by filter rules migrate as Odoo CRM Tags applied to the corresponding Lead or Contact records. Segment membership is resolved by re-running the Atendare filter criteria against the migrated contact data and applying the resulting tag. If the customer requires dynamic lists rather than static tags, we document the original segment criteria for the admin to recreate as Odoo Scheduled Actions or domain-based filters.

Atendare's company-contact linking is preserved through the Account-Contact lookup in Odoo. The relationship is resolved at migration time by matching the Atendare company_id on each Contact to the corresponding Odoo Account created from the Company record. If a Contact in Atendare has no associated Company, it is migrated as a standalone Contact without an Account reference, and we flag it for the admin to link manually post-migration if needed.

Atendare Deal stage change history (stage name, probability at time of stage, timestamp) is extracted as activity log entries and stored in a custom Odoo activity log or chatter note on the Opportunity record. Odoo does not natively preserve stage-change audit trails across objects, so we document the history in a structured note for the customer's admin to reference. Stage change timestamps are preserved as Odoo Note creation dates.