Migrate from LocaliQ to Odoo CRM

LocaliQ Dash leads map to Odoo crm.lead (the Lead object). We extract lead records via the LocaliQ Contacts API with AI scoring attributes (Dash score, lifecycle stage, engagement timestamps) preserved in custom fields on the Odoo lead. Dash source channels (call, form, chat, SMS) migrate to Odoo's lead_type and lead_ids source tracking. The customer may optionally run Odoo's Lead-to-Contact wizard post-migration to convert qualified leads; we document this as a post-migration step rather than performing mass conversion during migration.

LocaliQ Contacts map to Odoo res.partner records. Standard fields (name, email, phone, address) map directly. LocaliQ custom contact properties (industry, company size, acquisition channel) migrate as Odoo custom fields on res.partner. Contact-company relationships from LocaliQ map to res.partner parent_id (contact under company) or remain standalone contacts in Odoo depending on the customer's chosen Odoo partner hierarchy model.

LocaliQ Companies map to Odoo res.partner records with the company_type flag set to company. We use the company name as the partner name, website, and dedupe key. Custom company properties migrate to Odoo res.partner custom fields. The company-contact relationship graph is preserved by setting child contact records to reference the parent company partner via parent_id. Odoo allows both individual contacts and company partners in a single table, unlike platforms with separate Contact and Account objects.

Dash pipeline stages (lead, qualified, proposal, negotiation, won, lost) map to Odoo crm.stage records. We preserve stage ordering via Odoo's sequence field and assign stages to the relevant crm.team. Custom stage names and probability percentages (where Dash provides them) migrate to Odoo stage properties. Stage probability settings in Odoo control automated revenue forecasting, so we align Odoo stage probabilities with the original Dash stage progression percentages.

LocaliQ campaigns map to Odoo crm.tag records for simple tagging use cases, or to Odoo's utm.mixin tracking fields (utm_source, utm_medium, utm_campaign) on crm.lead and res.partner. The mapping approach depends on whether the customer uses Odoo's native UTM tracking for marketing attribution or relies on campaign tags for reporting. We confirm the preferred approach during scoping and configure UTM campaigns in Odoo before migration if the customer selects the UTM approach.

LocaliQ call records (sourced from the Contact Interactions API which includes call recording URLs and transcripts) map to Odoo crm.phonecall. We preserve call duration, disposition, recording URL, and timestamp. Odoo's crm.phonecall model is part of the CRM app and can be linked to the related crm.lead or res.partner via the partner_id field. Call outcomes from LocaliQ (connected, voicemail, missed) map to Odoo's call_duration and state fields.

LocaliQ email engagement records map to Odoo mail.message records linked to the related crm.lead or res.partner. Email subject, body (plain text or HTML), sender, and recipient migrate. The LocaliQ Contact Interactions API provides email transcripts and form submissions which migrate as mail.message records with subtype note. Odoo's mail_thread model on res.partner and crm.lead provides the activity timeline for displaying these records.

LocaliQ meeting engagements map to Odoo calendar.event records. Meeting title, start and end times, location, and attendee list migrate. Odoo's calendar integration links events to crm.lead or res.partner via the partner_ids field. Recurring meeting series are not preserved as recurring patterns; each instance migrates as an individual calendar.event record.

LocaliQ notes associated with leads or contacts map to Odoo note.note records. We link notes to the related crm.lead or res.partner via the res_id and model fields. Note body, creation date, and author migrate. If LocaliQ stores notes as rich text with attachments, the attachment URLs migrate as text references for manual retrieval rather than as Odoo attachments.

LocaliQ task records (follow-up actions, reminders) map to Odoo project.task records under the customer's default project if Odoo Project is installed, or to note.note records if Project is not in scope. Task status, priority, due date, and assignee migrate. Assignee mapping resolves LocaliQ owner email to Odoo res.users login for task ownership.

LocaliQ custom fields on leads, contacts, and companies require pre-creation in Odoo before migration. We inventory all custom fields from LocaliQ (Dash AI scores, industry verticals, campaign sources, acquisition channels, custom scoring attributes) and create corresponding custom fields on the crm.lead and res.partner models in Odoo using the Settings > Technical > Database Structure > Fields interface or via CSV import. Field data types map from LocaliQ (text, number, date, dropdown) to Odoo field types (char, float, datetime, selection). The crm_custom_fields Odoo module (available on the Apps Store) can automate Lead-to-Contact custom field propagation if the customer converts leads post-migration.

LocaliQ products referenced in leads or campaigns map to Odoo product.product records. Product name, SKU, description, and list price migrate. We create the product in Odoo before lead migration if products are linked to leads, so that the product.product records exist as valid foreign keys.

LocaliQ Dash AI agent configurations (Voice greeting scripts, SMS templates, chat routing rules, agent availability schedules) are platform-native settings that do not have a migration path to Odoo CRM. Odoo does not include a native multi-channel AI agent module in its base CRM. We document the full agent configuration (greeting text, routing logic, business hours, SMS templates) in a written handoff document for the customer's admin to evaluate Odoo-compatible third-party telephony and chat integrations (Odoo's VoIP module, Twilio, or a partner AI agent app). Migration of agent configurations is out of scope.

LocaliQ automation sequences and trigger conditions do not migrate as functional code. Odoo CRM includes basic stage automation and server actions, but these are not equivalent to LocaliQ's event-triggered workflow builder. We deliver a written inventory of every active LocaliQ workflow with its trigger condition, action sequence, delay steps, and enrollment criteria, mapped to Odoo automated action equivalents where applicable. The customer's admin rebuilds workflows in Odoo using IrActionsServer, base.automation, or a certified Odoo partner.

LocaliQ multi-directory citation data (listing details, verification status, citation URLs across 100+ directories) exports as a static record inventory. The syndication mechanism does not transfer: Odoo has no native directory syndication module, and listings must be re-verified at each platform individually. We deliver the complete listing inventory with directory URLs, verification status, and citation text so the customer's team can re-claim and update listings at the destination. Migration of live syndication connections is out of scope.

LocaliQ review data (ratings, content, dates, response history) migrates as a reference inventory linked to the related company partner record. Review content and metadata export as structured records; the native review-response workflow does not replicate in Odoo CRM. We link review records to the corresponding res.partner via a custom Many2many field or note attachment, and the customer's team manages review responses manually or through a dedicated reputation management tool post-migration.

LocaliQ references to connected Google Ads and Yelp Ads accounts (campaign IDs, account metadata, attribution settings) are documented as a written integration inventory. Odoo does not include native Google Ads or Yelp sync; re-authentication of ad platform integrations happens directly in the destination platform (Google Ads, Yelp Dashboard, or a third-party Odoo connector). We provide the account connection metadata so the customer's team can re-establish integrations post-migration.