Migrate from TeamSystem CRM to Odoo CRM

TeamSystem Contact records map to Odoo res.partner with is_company=False and parent_id set to the corresponding company partner record. Address fields (street, city, country, zip) map to partner address fields using Odoo's partner address mechanism. Email, phone, and mobile map to email, phone, and mobile. Owner assignment from TeamSystem maps to Odoo user_id on the CRM activity side; contact-level ownership is implicit through the parent company assignment.

TeamSystem Company records map to Odoo res.partner with is_company=True. The company domain becomes the partner's website field. If TeamSystem stores a VAT number, it maps to vat. Multiple contacts under the same company in TeamSystem all reference the same parent partner record via parent_id. We resolve parent_id foreign keys before inserting contact records to avoid Odoo's partner constraint violations.

TeamSystem Lead records map to Odoo crm.lead with type='lead' and is_lead=True. Lead status from TeamSystem (new, contacted, qualified, disqualified) maps to Odoo's lead_stage_id with a custom stage mapping table built during discovery. Lead source, score, and any custom scoring fields map to Odoo's priority and tag fields, or to custom Char/Integer fields if the customer requests granular scoring retention.

TeamSystem Opportunity records map to Odoo crm.lead with type='opportunity'. Deal value maps to Odoo's planned_revenue. Stage maps to crm_stage with the stage name matching the customer's pipeline stage names. Expected close date maps to date_deadline. Pipeline association in TeamSystem maps to a combination of Odoo's team_id (sales team) and tag_ids for pipeline-level segmentation if multiple pipelines are in use.

TeamSystem pipeline configurations (stage names, probabilities, sequence) map to Odoo crm_stage records ordered by sequence. Each TeamSystem pipeline maps to an Odoo sales team (crm.team), and stage probabilities are set on the stage record. If the customer uses a single pipeline in TeamSystem, we configure one crm.team and map all stages under it. Multi-pipeline customers get multiple crm.team records with their respective stage sequences.

TeamSystem Activities (calls, emails, meetings, tasks) map to Odoo mail.activity records linked to the parent crm.lead via res_model='crm.lead' and res_id. Activity type maps to activity_type_id with a custom mapping table for non-standard types. Activity date and duration map to date_deadline and duration. Owner maps to user_id. For activities linked to Contacts without a related Opportunity, we link to the res.partner record directly using the same mail.activity mechanism.

TeamSystem file attachments linked to deals, contacts, or activities map to Odoo ir.attachment records with res_model pointing to crm.lead or res.partner and res_id pointing to the migrated record ID. We export attachments by URL reference or download to local storage, then re-attach using Odoo's attachment mechanism. Attachment size limits and storage configuration must be verified against the customer's Odoo hosting plan (Odoo Online vs. Self-hosted) before migration.

TeamSystem custom fields on Contacts, Companies, Leads, and Opportunities require pre-creation in Odoo before data import. We extract the custom field registry during discovery, map field types to Odoo field definitions (Char, Integer, Float, Text, Selection, Many2one), and create them via Odoo Studio or direct model definition before import. Custom picklist values become Odoo Selection field options with the same key-value pairs.

TeamSystem Owner records map to Odoo res.users by email match. Any TeamSystem owner without a matching Odoo user is held in a reconciliation queue while the customer's admin provisions the user. Active vs. inactive status maps directly. Team-based ownership in TeamSystem maps to Odoo crm.team membership via res.users.group_id and team member configuration.

If TeamSystem contains custom objects beyond standard Contact, Company, Lead, and Opportunity, we map them to Odoo custom models created via the Studio interface or direct model definition. Custom object relationships (lookup fields to standard objects) map to Odoo Many2one fields pointing to crm.lead or res.partner. The customer chooses whether custom objects migrate as CRM-linked records or as separate Odoo apps during scoping.

Email tracking and inbox association data from TeamSystem migrates as mail.message records linked to crm.lead or res.partner via res_model and res_id. Full email body content may require separate export depending on the TeamSystem integration configuration and whether emails are stored in the CRM layer or the ERP email module. We flag email extraction scope during discovery and exclude ERP-layer email records to avoid including non-CRM correspondence.

TeamSystem workflow automation configurations are stored in the ERP-CRM integration layer and are not exportable as discrete data. We do not migrate automations as code. We document every active TeamSystem workflow trigger, condition, and action in a written inventory with recommended Odoo Automations equivalents using ir.actions.server and crm.lead.rule models. The customer's Odoo partner or admin rebuilds them post-migration.