Migrate from Leadtrekker Lead Management to Odoo CRM

Leadtrekker stores all prospects as a single Lead type with name, email, phone, status, lead source, and owner assignment. Odoo splits the lifecycle into crm.lead (unqualified inbound) and crm.lead (opportunity, qualified pipeline). We map the Leadtrekker status and source to Odoo Lead fields (stage_id, tag_ids, source_id) preserving attribution. The customer defines the qualification rule during scoping — typically Leadtrekker status New maps to Odoo New Lead, and status Qualified maps to an Odoo pipeline stage. Custom fields on Leadtrekker Leads are reconstructed from extracted record samples because the field taxonomy is not publicly documented; we build the full custom field map from the discovery probe before import.

Leadtrekker activities attach notes, call logs, and email events to a Lead with a timestamp and user attribution. Odoo stores these as mail.message records on the crm.lead chatter. We migrate each activity as a mail.message with message_type set to comment (notes), email (email events), or notification (system events). Activity timestamps and author attribution are preserved. Call disposition and duration from Leadtrekker call logs migrate to custom mail.message fields if defined, or are appended to the message body.

Leadtrekker user accounts store login credentials and profile data. We export the user roster (name, email, active status) and map to Odoo res.users records by email match. Passwords and session tokens do not transfer — the Odoo administrator provisions login credentials post-migration. Active/inactive status on Leadtrekker maps directly to the active flag on res.users.

Leadtrekker groups define which users can view and edit specific lead subsets. Odoo uses res.groups for access control across all apps. We extract the full group membership roster, map each Leadtrekker group to the closest Odoo access group (Sales / Administrator / Custom), and deliver a written mapping table. Permission logic is reconfigured manually in Odoo Settings > Users > Access Rights because the semantics differ — Leadtrekker uses lead-level scoping while Odoo uses record-rule domain filtering per group.

Leadtrekker tracks lead attribution by source (website form, campaign, referral) as a Lead property. Odoo uses the UTM (utm.source, utm.medium, utm.campaign) model for attribution tracking linked to crm.lead records. We migrate source labels as utm.source records and set the source_id on each Lead during import. If Leadtrekker tracks medium and campaign separately, we map those to utm.medium and utm.campaign.

Leadtrekker follow-up reminders carry a due date and owner. Odoo stores scheduled follow-ups as mail.activity records on crm.lead with activity_type_id, date_deadline, and user_id. We convert each Leadtrekker reminder to a mail.activity, preserving the due date and assignee. If the Leadtrekker reminder type (call, email, meeting) is captured, we map it to the corresponding Odoo activity_type.

Leadtrekker does not publish a stable field taxonomy in its public documentation, and the custom field schema requires discovery during migration scoping. We probe the Leadtrekker API with a representative record export, identify all fields beyond the standard set (name, email, phone, status, source, owner), and build an explicit field-level mapping table. Custom fields migrate to Odoo as custom ir.model.fields — type-mapped (text to char, number to float, date to date) and deployed via Odoo Studio or data migration scripts before record import begins.

Leadtrekker uses a flat status property on Lead (New, Contacted, Qualified, Lost). Odoo uses crm.stage within a crm.team sales process. We map each Leadtrekker status value to the nearest Odoo stage and, where Leadtrekker has fewer stages than Odoo's pipeline, collapse intermediate Odoo stages out of the active pipeline or create a simplified pipeline matching the source status count.

Leadtrekker's one-tag website integration for form-based lead capture has no direct Odoo equivalent that migrates as data. We document every active Leadtrekker form and website integration (URL, form fields, submission endpoint) so that the customer can rebuild the equivalent in Odoo website builder or connect the existing form to an Odoo crm.lead creation endpoint. Lead capture via Odoo forms or inbound email aliases replaces the Leadtrekker integration post-migration.

Leadtrekker SMS and email notification settings are platform-runtime preferences and are not stored as exportable records. We document every notification-trigger event observed during extraction — assignment alerts, response-time triggers, autoresponder templates — and deliver a written guide to rebuilding equivalent mail.template records in Odoo. The administrator configures the SMTP server and SMS gateway (Odoo SMS or a third-party provider) during post-migration setup.

Leadtrekker tracks response time as an accountability metric tied to lead assignment. Odoo does not have a native response-time field on crm.lead, but the metric can be rebuilt using automation rules that log the first activity date on a Lead and compare it to create_date. We document the Leadtrekker response-time configuration for the admin to implement in Odoo Studio as a computed field and activity trigger.

Leadtrekker's marketing ROI measurement ties campaign spend to pipeline outcomes. Odoo provides pipeline and revenue reports by UTM campaign in the CRM app, and full financial reporting when Odoo Accounting is installed. We map Leadtrekker campaign labels to utm.campaign records for ongoing attribution. The customer rebuilds budget-versus-revenue reporting in Odoo Reporting or a BI tool; we deliver the mapping from Leadtrekker campaign data to utm.campaign so the historical context is available.