Migrate from CRM Runner to Odoo CRM

CRM Runner Contact records map 1:1 to Odoo CRM Lead or Contact depending on qualification status. We extract contact name, email, phone, address, and custom fields during scoping. If the contact has associated Companies, we map to Odoo Contact under a Partner record; if the contact is a standalone prospect, it lands as a Lead. We preserve any CRM Runner custom field definitions as Odoo custom fields on the partner model using Odoo Studio before import.

CRM Runner Company records map to Odoo Partner records with the Company Type flag set. The Partner record becomes the parent of any related Contact records migrated in the previous phase. We use company name as the Odoo Partner name and preserve the domain, address, and any company-level custom fields. Parent-company hierarchies in CRM Runner map to Contact-type Partner records with parent_id set to the Company-type Partner.

CRM Runner Job is the primary field-service record carrying work order details, assigned team members, location, job status, and embedded time entries. We map each Job to an Odoo Project record, with individual job line items or sub-tasks as Odoo Task records within that Project. Job status maps to Project stage; assigned team members map to Odoo Project assignees. Jobs without sub-items map to a single Task under a Project. This split is the most significant structural transformation in the migration and requires careful stage and user mapping during schema design.

CRM Runner Team Members map to Odoo User records. We extract role, department, and permission level during scoping and map them to Odoo's access rights groups. CRM Runner's admin account (which does not count toward seat licenses) maps to an Odoo administrator account with full access rights. Team Members without a clear Odoo role are mapped to the internal user group pending admin assignment. We flag any Team Member records that reference inactive CRM Runner users for manual review.

CRM Runner standalone Tasks map directly to Odoo Task records under the customer's Odoo CRM project or under a default pipeline project. Due date, assignee (via Team Member-to-User mapping), status, and description migrate 1:1. Custom fields on tasks map to Odoo custom fields on the project.task model.

CRM Runner call logs are discrete records attached to Contacts or Jobs. We flatten them into Odoo Lead chatter notes or Project Task chatter entries with a formatted note body (date, duration, disposition, recording reference if present). Call records that reference a Contact linked to a Job project get attached to the corresponding Project via Odoo's chatter thread. We do not create Odoo VoIP call records because that requires the Odoo VoIP module to be active; if VoIP is activated, we can adjust the mapping to use Odoo's crm.phone.call model.

CRM Runner SMS threads map to Lead or Contact chatter entries as formatted notes with sender, recipient, timestamp, and message body. If the Odoo SMS module is active in the destination, we map to the Odoo sms.sms model instead. We preserve the SMS direction (sent/received) as a prefix in the note body for audit clarity.

CRM Runner time-clock records tied to Team Members and Jobs are payroll-adjacent and do not map cleanly to standard CRM objects. We export them as a separate structured CSV package with employee name, date, hours, job reference, and clock-in/clock-out timestamps. We recommend pairing the CRM migration with a dedicated payroll or accounting tool migration for this dataset rather than forcing it into Odoo CRM. If Odoo Timesheet module is active, we can map time entries to Odoo account.analytic.line records as a configuration option discussed during scoping.

CRM Runner pipeline stages map to Odoo CRM stage configuration within the CRM pipeline view. We extract stage names, order, and any custom stage logic during scoping and replicate them in Odoo's pipeline editor. CRM Runner's stage-level automation triggers (IFTTT-style) are documented as written specifications for Odoo Studio automated action rebuild. Stage probability values map to Odoo's probability field if they exist in CRM Runner.

CRM Runner custom fields on Contacts, Companies, and Jobs are extracted during scoping and recreated as Odoo custom fields using Studio before data import begins. We document the original CRM Runner field name, data type, and any picklist values as a mapping artifact. Custom fields that reference other CRM Runner objects (e.g., a job reference on a contact) are mapped using the CRM Runner record ID preserved as an external identifier in Odoo.

CRM Runner IFTTT-style automations (trigger-action rules) have no documented export or migration path. We extract every automation during discovery, documenting trigger type, conditions, actions, and any dependent custom fields as a written specification. This document is handed off to the customer's Odoo admin for rebuild using Odoo Studio's automation builder or server actions. Automations are explicitly excluded from the migration deliverable and represent a post-migration implementation step with its own timeline.

CRM Runner embedded payment records tied to Jobs or Contacts are accounting-adjacent and migrate best to a dedicated accounting tool. We export them as a separate structured CSV with transaction ID, amount, date, customer reference, job reference, and payment method. If Odoo Accounting is active in the destination, these can be imported as vendor bills or customer payments depending on direction; this requires coordination with the Odoo Accounting module configuration.