Migrate from Acquaint CRM to Odoo CRM

Acquaint contacts map to Odoo res.partner records. We set partner_type='contact' for individuals. Primary company link resolves via the Acquaint company association — Odoo parent_id is set to the matched res.partner company record. Contacts without a primary company land as standalone res.partner records. Email, phone, and address fields map directly; custom contact fields migrate to res.partner custom fields.

Acquaint companies map to Odoo res.partner records with partner_type='company'. Multi-branch companies: if Acquaint stores branch-level data, each branch becomes a separate res.partner company record linked via parent_id to the parent company. Company website, industry, and employee count map to custom fields or direct equivalents where Odoo provides them.

Acquaint property listings are a property-vertical concept with no direct Odoo equivalent. For sales/letting listings, we migrate to product.product with type='product' and custom fields for listing_status, property_type, tenure, bedrooms, and asking_price. For development sites or land parcels tracked as pipeline items, Acquaint Property migrates to crm.lead as a lead with property details in custom fields and property_address in the standard contact address fields.

Acquaint deals map to Odoo crm.lead records. Open and Under Offer deals become active crm.lead entries; Sold and Sold STC deals become crm.lead records with stage set to the Odoo Won stage. Acquaint deal amount maps to Odoo's expected_revenue field. Each Acquaint deal stage requires a corresponding Odoo crm.stage record created before migration runs — stage probability and forecast_category are set per stage in the Odoo stage configuration.

Acquaint stage names (Open, Under Offer, Sold STC, Sold, Withdrawn) require pre-creation of matching Odoo crm.stage records within the target Odoo sales team. Each crm.stage carries name, sequence, probability, and on_change flags. The Acquaint stage-to-Odoo-stage mapping is a value-mapping step executed during migration — the migration plan specifies which Acquaint stage maps to which Odoo stage ID before data loads.

Acquaint property objects carry listing_status, property_type, tenure, number_of_bedrooms, number_of_bathrooms, asking_price, and vendor_source as native fields. These have no Odoo native equivalent and must be created as custom fields on product.product (for listings) or crm.lead (for development deals). Custom field creation on the Odoo side is a prerequisite step — we deliver a field creation spec before migration runs.

Acquaint notes and tasks associated with contacts, companies, or deals migrate as Odoo mail.message records with message_type='comment', preserving the original note body, author (by email match to Odoo res.users), and create_date timestamp. Tasks with a due date migrate as Odoo mail.activity records linked to the target res.partner or crm.lead. The migration plan distinguishes notes from tasks and maps them to the appropriate Odoo model.

Acquaint owner records (sales staff or branch managers assigned to contacts, companies, or deals) are resolved by email match against Odoo res.users. Unmatched owners are flagged in the migration plan — your team either creates Odoo user accounts for them first or assigns their records to a fallback user (admin or a dedicated migration user). Owner resolution is required before crm.lead records load because Odoo's crm.lead requires a user_id field to be set.

Files attached to Acquaint contacts, companies, and properties (photographs, floor plans, EPCs, documents) migrate to Odoo ir.attachment records. The file binary is downloaded from Acquaint's API and re-uploaded to Odoo via XML-RPC. We preserve the original filename, mimetype, and parent record links (res_model + res_id pointing to the migrated res.partner or crm.lead). Large files are chunked to stay within Odoo's attachment size limits.

Acquaint uses branches (offices) as a top-level grouping entity for contacts, properties, and deals. Odoo separates crm.team (sales team/group) from individual user ownership. We map each Acquaint branch to a crm.team record — branch name, location, and primary contact email transfer. Deals and contacts can then be assigned to the crm.team and an individual res.users owner. If Acquaint stores branch-level data (branch-wide targets, branch manager), we surface it for Odoo team configuration.

Acquaint property alerts or saved search records are a property-specific concept without a CRM equivalent in Odoo. We migrate them as res.partner records with a custom boolean flag x_property_alert__c set to True, plus the saved search criteria stored in a custom text field x_saved_search_criteria__c. These records are flagged for manual review in Odoo since the alert matching logic cannot be auto-migrated.

Acquaint supports N:N contact-to-company associations where one contact belongs to multiple firms. Odoo res.partner uses a single parent_id for the primary company and child_ids for additional contacts. We migrate the most-recently-modified Acquaint company association as the primary company (parent_id), and store remaining company associations as a custom multi-select field x_additional_companies__c for manual reconciliation in Odoo.