Migrate from BlinQ to Odoo CRM

Multi-profile card split creates duplicate email records in Odoo if not handled explicitly

BlinQ users with multiple card profiles (personal, work, event-specific) share the same email address across profiles. Odoo's res.partner model treats email as a soft uniqueness key for deduplication — if two BlinQ profiles with the same email are loaded without a profile-type discriminator, Odoo merges them into one record. We split each BlinQ card profile into a separate res.partner with a Profile_Type__c custom field and a composite external_id combining the BlinQ card ID and profile ID, preventing Odoo from collapsing distinct profiles. This requires the custom field to exist before data loads, so Odoo Studio field creation is Step 1 of the migration plan.

BlinQ tags do not map to Odoo crm.lead.partner_assigned_id — a separate tagging strategy is required

BlinQ's qualifier tags like 'Decision Maker' and 'Event Lead' have no built-in equivalent in Odoo's crm.lead model. Odoo has no contact-to-lead association label system — Opportunity Contact Roles are the closest native construct but those apply to opportunity records, not lead records. We map BlinQ tags to Odoo ir.model.data tags on res.partner and store the primary qualifier in a Qualifier__c custom Selection field. Teams that need granular association labels (e.g. 'Champion', 'blocker') must decide whether to collapse them into the Qualifier__c field or create a custom many2many relation to a dedicated qualifier-type model. This decision is surfaced in the migration plan before data loads.

BlinQ meeting notes and AI conversation summaries lack a native Odoo field — they land in mail.message with no searchable conversation view

BlinQ stores AI-generated meeting notes and conversation context as a structured note attached to each connection record. Odoo has no native 'conversation note' field on res.partner — the closest storage location is a mail.message record with subtype='comment'. This means meeting notes from BlinQ appear in Odoo's chatter as generic message entries, not in a dedicated notes panel, and are not surfaced in Odoo's lead scoring or activity reporting by default. We preserve the full note body, original meeting date, and BlinQ meeting ID, but teams relying on BlinQ's conversation-summary UI will need a custom Odoo widget or a separate notes module to replicate that experience.

BlinQ's credit-based billing model has no Odoo equivalent and does not carry over — billing context is lost unless preserved manually

BlinQ legacy plans charge $5 per badge scan and $5 per CRM sync, creating a credit-consumption record that tracks how many times a contact was scanned or pushed to a CRM. Odoo CRM has no billing-flag equivalent — there is no native field that records how many times a partner was 'synced' or 'scanned.' We do not migrate this credit-consumption history as it has nowhere to land in Odoo's data model. If your team uses scan-count data for ROI reporting on event networking spend, this metric must be rebuilt in Odoo using the custom BlinQ_Scan_Count__c field we migrate, combined with a dashboard query — but the historical credit ledger from BlinQ is not transferable.

Odoo XML-RPC API rate limits require batch sequencing that extends migration time for large contact volumes

Odoo's XML-RPC external API enforces request-rate guidelines per Odoo Community and Enterprise documentation. For migrations with more than 10,000 BlinQ contacts, we batch records in groups of 200–500 per API call and introduce retry logic with exponential backoff to handle 429 Too Many Requests responses. Large BlinQ exports with meeting notes and enrichment data nested per contact increase payload size, which can trigger Odoo's worker memory limits on lower-tier Odoo.sh instances. We validate Odoo instance specs during the assessment phase and throttle batch sizes accordingly. This is handled automatically but disclosed because it directly affects the migration timeline for high-volume BlinQ exports.