Migrate from Ayna to Odoo CRM

Ayna Contact records map directly to Odoo CRM Contact. Standard fields (name, email, phone, company association) migrate via XML-RPC create operations with duplicate detection on email. We map Ayna's custom contact properties to Odoo custom fields on res.partner, preserving data types (text, selection, date, integer). Owner assignment from Ayna's user records maps to Odoo's create_uid and user_ids fields.

Ayna Company records represent brands or businesses being protected and map to Odoo CRM Partner records with the company_type field set to 'company'. The company_name field captures the brand name; street, city, country, and website migrate as standard address fields. We use Odoo's address normalization during import to ensure country and state fields conform to Odoo's configured localization settings.

Ayna Channels represent communication and social platforms connected to the brand. Odoo CRM does not have a native Channel object. We map active channels to Odoo Tags on Contact (crm.tag) and archived channels to a separate inactive_channels custom field on Partner. Channel-to-contact associations migrate as tag assignments. We flag active versus archived channels at cutover to prevent duplicate tag import.

Social account connections for brand monitoring require re-authentication in the destination platform and cannot be transferred as credentials. We document the current social account connections (platform, URL, access level) during discovery and deliver a re-authentication checklist for the customer's admin to complete post-migration in Odoo's social media integration apps or third-party social management tools.

Ayna website domains tied to website synchronization and brand protection map to Odoo Partner custom fields (domain_name, domain_ownership_verified, domain_registration_date). We preserve domain ownership metadata intact during migration. Full domain monitoring and DNS change tracking requires Odoo's website builder or a third-party domain monitoring app post-migration.

Ayna custom fields on contacts and companies use Ayna-specific naming conventions that map to Odoo custom fields on res.partner. We extract the Ayna field schema during discovery, map each custom field to an Odoo ir.model.field record with matching data type (char, text, selection, many2one, date, datetime, integer, float), and create the destination schema before import. Selection field option values map to Odoo selection fields with the same key-value pairs.

Ayna User records (email, name, role assignment) map to Odoo res.users. We resolve owners by email match. Any Ayna Owner without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Active/inactive status migrates to the Odoo active field.

Attachments to brand protection records (screenshots, legal documents, brand assets) may be exported as file references. We note that Odoo stores attachments as ir.attachment records linked to the parent model. File content migration depends on the destination's attachment storage configuration (database or filestore). We deliver a file inventory with source URLs and recommended Odoo attachment placement for manual review.

Ayna brand protection records are central to its value proposition and have no direct Odoo CRM equivalent. We map these to Odoo CRM Leads with a custom brand_protection boolean flag and custom fields capturing the brand protection record type, status, and metadata. Customers with high brand protection record volume may choose to use Odoo Field Service or a custom brand protection module from the Odoo Apps marketplace post-migration.

Ayna email engagements map to Odoo mail.message records linked to the parent Contact or Partner via model=res.partner and res_id. Email body, subject, and timestamp migrate as mail.message fields. We preserve sender and recipient information in the message author and partner_ids fields. Attachments to emails migrate as mail.message.attachment records.

Ayna call engagements map to Odoo CRM Lead or Partner phonecall records. Call disposition, duration, and outcome migrate to custom fields on crm.phonecall. Activity timeline ordering is preserved by setting create_date to the original Ayna timestamp. If the customer does not have the crm_phonecall module installed, calls migrate as crm.lead notes with a phonecall prefix.

Ayna meeting engagements map to Odoo calendar.event records. Start datetime, end datetime, location, and description preserve. Attendee mapping links to calendar.event records pointing at the related Contact or Partner records via partner_ids. We set the event's user_id to the owner resolved from the Ayna user mapping.

Ayna Notes migrate to Odoo mail.message records with message_type=notification on the parent Contact or Partner. Note body migrates as plain text with any embedded URLs preserved. We set create_date to the original Ayna note timestamp to preserve activity timeline ordering.

Ayna task engagements map to Odoo project.task if the customer licenses Odoo Project, or to CRM Lead notes if not. Task status, priority, due date, and description migrate directly. Task assignment resolves the Ayna owner to the Odoo user mapping established during User provisioning. The customer chooses task strategy during scoping.