Migrate from Teleforce CRM to Odoo CRM

Teleforce Contacts map to Odoo CRM Lead records. We use the Contact's email address as the deduplication key and create the Lead with type='lead' in Odoo. Teleforce's owner assignment maps to the sales team member in Odoo's user_id field. We preserve any Teleforce lifecycle stage or status property as a custom Char field on the Lead for audit. Teleforce's contact phone number is mapped to Odoo's phone field with leading-zero normalization applied during the CSV transform to prevent phone number truncation.

Teleforce Companies map to Odoo res.partner records with partner_type='company'. The company name maps to the partner's name field, domain to website, and industry or sector to a custom field or tag. We resolve the company-contact linkage by matching the Contact's associated company name against the imported partner record and setting partner_id on the Lead. Odoo requires parent_id resolution before child contact import, so partners are imported in a pre-phase before Leads.

Teleforce Deals map to Odoo CRM Opportunity records (the same crm.lead model with type='opportunity'). The deal name maps to the Opportunity name, deal amount to expected_revenue, and the Teleforce pipeline stage to an Odoo stage_id via a pre-built stage mapping table. Owner assignment migrates from Teleforce's deal owner to user_id in Odoo. Lost-won status from Teleforce maps to the Odoo stage probability setting for that stage.

Teleforce pipeline stages are configured in Odoo as crm.stage records within a crm.team. We map each source stage name to an Odoo stage, preserving stage order via the sequence field. Probability percentages per stage migrate from Teleforce to stage_ondemand_available or probability fields on the Odoo stage. If Teleforce has multiple pipelines, we create separate crm.team records in Odoo and assign Opportunities by mapping the Teleforce pipeline identifier to the team_id.

Teleforce Activities (calls, emails, tasks) map to Odoo mail.activity records. We extract available activity data via CSV export and import into Odoo using the mail.activity API or CSV loader with activity_type_id, user_id, res_id, and res_model resolved. Activity dates migrate as calendar_date to preserve the original timestamp. If Teleforce exports are limited to the UI view, we prioritize call logs and email records over chat threads where the export path is unconfirmed.

Teleforce custom fields on Contacts are not documented in a public schema but are confirmed as existing. During discovery, we request the customer's full field inventory from Teleforce and create matching custom fields in Odoo via Studio or direct Python model definition before the CSV import phase. Custom field type mapping is determined by the Teleforce field type: text to Char, number to Float or Integer, date to Date, and multi-value fields to Char (comma-separated) or Odoo tags depending on volume.

Teleforce custom fields on Deals are mapped to custom fields on the Odoo crm.lead model for opportunity records. We create the custom field definitions in Odoo before import and reference them by name during the CSV transform. Custom field data is included in the deal CSV export and loaded alongside the standard opportunity fields during the import phase.

Teleforce Owners referenced on Contacts, Companies, and Deals are resolved by email address against the Odoo res.users table. If the destination Odoo instance has fewer users than the Teleforce owner count, unmapped owners are flagged in a reconciliation queue and the customer provisions missing users before the final import phase. Inactive Odoo users are supported as import targets if the customer specifies they need the historical owner preserved.

Teleforce appears to support Leads as a distinct object or lifecycle stage separate from Contacts. We import Teleforce Leads as Odoo CRM Leads (type='lead') using the same pipeline as Contacts but preserving the lead-specific fields. The Teleforce lead score or qualification status maps to a custom Char or Integer field in Odoo for segmentation use after migration.

Teleforce tag support is not confirmed in the available research. Where tags exist in the source data, we import them as crm.tag records in Odoo and create crm.tag.rel many2many links on the Lead or Opportunity records. Tags without an existing Odoo definition are created during the import phase. If Teleforce exports tags as a comma-separated field on the Contact or Deal CSV row, we split and create tag records dynamically during the transform.

If Teleforce CRM stores product or service records linked to Deals, these map to Odoo product.template. We import product.name, product.default_code (SKU), and list_price into Odoo. Products must be created before Opportunity Line Items if the migration includes deal-product associations. Odoo's product variant model (product.product) is only used if Teleforce tracks variant-level product data; otherwise, product.template covers the standard migration case.

Teleforce attachments are stored within the CRM context but we found no documented bulk export path. We flag attachments as partially migratable: if the customer provides direct database access or a URL-exportable attachment list, we import ir.attachment records with a res_model pointing to the parent crm.lead or res.partner and res_id set to the migrated record ID. Inline file blobs without a URL reference are excluded from the standard migration scope and documented in the handoff report for manual recovery.