Migrate from Lead Guerrilla to Odoo CRM

Lead Guerrilla Contacts map directly to Odoo CRM Lead records via the Odoo External API (xmlrpc/2/object). We preserve name (split into firstname and lastname if combined), email, phone, address fields, and any custom contact properties. Lead scoring values from Lead Guerrilla migrate as a custom integer field lg_lead_score__c on the Odoo crm.lead model. Tags from Lead Guerrilla migrate as Odoo Tag records linked via res.partner.category with the tag applied to the corresponding Lead record.

Lead Guerrilla Company records map to Odoo Partner records with the customer flag set (partner_type = company). The Company name becomes the Account name; the Company domain becomes the Website field used for deduplication during import. In Odoo, Companies and individual Contacts share the same res.partner table differentiated by is_company flag, so we preserve the Contact-to-Company linkage by setting the parent_id field on each Contact Partner record to reference the corresponding Company Partner record.

Lead Guerrilla multi-channel Campaigns map to Odoo CRM Team (for ownership and pipeline assignment) and Odoo Mailing (mailing.mailing model) records for email campaign delivery. Campaign timing rules and channel assignments from Lead Guerrilla are catalogued and documented for manual rebuild in Odoo's Marketing Automation app. The enrollment triggers (form submit, page visit, tag applied) have no direct Odoo equivalent and are documented as automation rebuild actions in the handoff playbook.

Lead Guerrilla Segments define dynamic contact groups based on form source, behavior, or demographic criteria. We export segment definitions including filter conditions and member counts. Each Segment is translated into an Odoo Tag (res.partner.category) plus an Odoo Domain expression on a static List or an Act Window action so the customer's team can reproduce the behavioral grouping logic. We deliver a field-level segment-to-domain mapping table as part of the rebuild playbook.

Lead Guerrilla calculates lead scores from website behavior, form submissions, and campaign interactions. We export the current numeric score per contact as a custom integer field on the Odoo crm.lead model. The scoring model itself (point values per action, threshold levels) does not transfer; we document the point matrix in the handoff playbook so the customer's Odoo admin can configure equivalent lead scoring rules in Odoo's CRM app using its native Lead Scoring feature.

Lead Guerrilla tracks email opens, page visits, form submissions, SMS sends, and tweet engagement as Activities with timestamps and event types. We export the full activity history and post it to Odoo CRM Lead records via the mail.message model using the Odoo External API. High-volume activity records are chunked into batches of 500 and rate-limited with exponential backoff to respect Odoo's API throughput limits on the customer's plan tier.

Lead Guerrilla Tags on Contacts and Companies migrate to Odoo Tags via the res.partner.category model. Tag naming conventions are preserved exactly as-is to maintain segmentation continuity. Tags applied to Companies attach to the corresponding res.partner record; Tags applied to Contacts attach via partner_id on the tag record or a dedicated tag-relation table if Odoo version uses a many2many field.

Lead Guerrilla User accounts (campaign owners, assignment recipients) map to Odoo User records by email match. We extract the user list including name and email during discovery. Odoo User provisioning is the customer's responsibility (requires admin access and license assignment), but we reconcile the owner_id field on every migrating record against the resolved User ID and hold unmatched records in a reconciliation queue until the customer's admin provisions the missing Users.

Lead Guerrilla Landing Page metadata (title, URL slug, published status, redirect rules) migrates as documentation for rebuild. The actual page HTML content, form embed scripts, and A/B testing configurations are not portable. We deliver a page-by-page inventory with field-level mapping so the customer's Odoo admin can rebuild each landing page in Odoo's Website app builder. Redirect rules from Lead Guerrilla are preserved as Odoo website.redirect records pointing to the new Odoo page URLs.

Lead Guerrilla Web Form field definitions, submission mappings, and redirect behavior migrate as documentation. Form logic (conditional field visibility, required field enforcement, submission triggers) is catalogued in the rebuild playbook. Odoo's Website app supports form building with the website_form module; the customer's marketing team rebuilds forms using the field-level inventory we deliver. Form submission data that arrived in Lead Guerrilla migrates as CRM Lead records created from the form submission date.

Any custom fields defined on Lead Guerrilla Contacts beyond the standard name/email/phone/address set are catalogued by name, type, and options during discovery. We create matching custom fields on the Odoo crm.lead model (ir.model.fields with track_visibility and related settings configured) before record import begins. Custom field types are mapped to nearest Odoo field types: text properties to char/text, numeric properties to float/integer, date properties to date/datetime.

Because Lead Guerrilla is built by 1CRM Systems Corp and its Contact and Company records share internal identifiers with the 1CRM database, cross-references between marketing data and CRM data can become orphaned when migrating to a non-1CRM destination. We audit every record that carries a 1CRM cross-reference ID during scoping, flag each pair for manual relinking, and resolve the relationship (or remove the orphaned reference) before final production import. If the customer is simultaneously migrating away from 1CRM, we recommend sequencing the CRM migration first, then the marketing automation migration, to prevent cascading relinking work.