Migrate from HaystackCRM to Odoo CRM

HaystackCRM Contact maps to Odoo res.partner with company=False and a parent_id reference to the mapped Company Partner record. We export Contacts with their associated Company ID from the Haystack spreadsheet, then resolve the Company to its Odoo partner ID before inserting the Contact partner record. Standard fields (name, phone, email, street, city, state, zip, country) map directly. Tags map to Odoo Tags (mail.tag) with no hierarchy preserved from Haystack's flat tag model.

HaystackCRM Company maps to Odoo res.partner with company=True. This record is inserted before the Contact import so that parent_id references are satisfied at the moment of Contact insert. The Company name becomes the partner display name. Industry classification and any website data map to industry_id (res.partner.industry) and website fields respectively. Company records are processed before Contacts to preserve the lookup chain integrity across the spreadsheet reconstruction.

HaystackCRM Opportunity maps to Odoo crm.lead. The Opportunity's dollar value maps to planned_revenue, stage maps to stage_id (resolving the Odoo stage name against the target crm.team's stage set), and temperature priority maps to priority (a selection field: 0=Low, 1=Medium, 2=High, 3=Very High). The Contact or Company link in Haystack resolves to the Odoo partner_id and partner_name on crm.lead. We create crm.lead records with type='opportunity' to distinguish from Odoo's separate lead concept.

HaystackCRM Tasks linked to an Opportunity map to project.task records within a dedicated Odoo Project (created during migration to host all migrated Tasks). Tasks linked to a Contact or Company map to project.task records with no project_id but with partner_id set to the Odoo res.partner ID. Due dates, task status (open/closed), and title map directly. We export Tasks after Contacts and Opportunities so that parent record IDs are available for lookup resolution.

HaystackCRM Events map to Odoo calendar.event. The event title, start datetime, end datetime, and location fields migrate directly. Attendee resolution maps Haystack Contact IDs to Odoo partner IDs and creates calendar.attendee records. Calendar sync links (device calendar integration) cannot be reconstructed in Odoo and must be rebuilt manually in the Odoo calendar settings post-migration. We export Events as discrete date-bound records without assuming any recurring pattern unless the customer documents recurrence rules explicitly.

HaystackCRM Items in the catalog map to Odoo product.product records with type='product' for goods or type='service' for services. Pricing data maps to list_price. The Items catalog is migrated before Line Items if the customer uses Odoo Sale Orders; for CRM-only migrations the Items catalog is migrated as a reference dataset. Product SKU maps to default_code and the item description maps to description_sale.

HaystackCRM Quotes generated from Opportunities map to Odoo sale.order in draft state. We export quote line items as sale.order.line records linked to product.product. The Odoo sale.order is created without submitting or confirming it, so the customer can review and manually finalize pricing and terms before using Odoo's sale order workflow. PDF links from Haystack are preserved in a custom field on the sale.order for manual reference.

HaystackCRM Users (owners) map to Odoo res.users records. We resolve by email match against the destination Odoo instance's user table. Any HaystackCRM owner without a matching Odoo user goes to a reconciliation queue; the customer's Odoo administrator provisions the missing user before record import resumes. Owner assignments on Opportunities and Tasks map to Odoo user_id on crm.lead and project.task respectively.

HaystackCRM Teams map to Odoo crm.team records. Team membership and role assignments are exported and mapped to Odoo team member records on crm.team. We create one crm.team per Haystack Team and configure stage sets per team so that pipeline stage values remain scoped correctly. Territory and role granularity beyond basic grouping requires Odoo Administrator reconfiguration post-migration.

HaystackCRM's flat tag model maps to Odoo mail.tag as top-level tags with no nesting. Tags are linked to crm.lead records via crm.tag.rel. Tags applied to Contacts or Companies migrate as tags on the corresponding res.partner records. The customer should plan a tag consolidation or renaming session during pre-migration scoping because Haystack tag taxonomies tend to accumulate inconsistencies at scale.

HaystackCRM file attachments stored in Dropbox, iCloud, or OneDrive are exported as external URL references. We export the attachment URLs and map them to Odoo ir.attachment records with type='url'. Native Odoo attachment storage (stored in the database or filestore) requires the customer to configure their Odoo filestore path during setup. We flag this as a post-migration configuration step and include the full list of attachment URLs in the migration inventory document.

HaystackCRM dashboard metrics are computed dynamically from live data and do not exist as persistent records. We do not migrate dashboard snapshots. The Odoo CRM dashboard and any Odoo Reporting module (account_accountant, l10n reports) should be configured by the customer's Odoo administrator post-migration using the migrated data as the source. We provide record count summaries and pipeline value summaries from Haystack as reference targets for dashboard reconstruction.