Migrate from FastTrack to Odoo CRM

FastTrack contacts map directly to Odoo res.partner records. In Odoo, partners serve as the universal contact model — company-type partners (is_company=True) hold company records; individual contacts are partners with a parent_id link to the company partner. FastTrack contact-to-company associations map via parent_id or child_ids depending on whether the source contact is a primary or secondary contact at a company.

FastTrack company records map to Odoo res.partner with is_company=True. Odoo's res.partner holds company_name, website, and address fields on the same record as individual contact data — FastTrack's separate company and contact objects collapse into one partner record per company. Child contacts (individual employees) link via parent_id to the company partner.

FastTrack leads that have not been qualified into deals migrate as Odoo crm.lead with type='lead'. The crm.lead model holds all lead fields — name, contact_name, email_from, phone, source_id, stage_id, and description — on a single record. FlitStack resolves the linked contact partner_id from the FastTrack contact ID before importing the lead.

FastTrack deals convert to Odoo crm.lead with type='opportunity'. In Odoo, opportunities are the same model as leads — the distinction is the type field value. Opportunity-specific fields (amount, probability, expected_revenue) map from FastTrack deal amount and probability values. The stage_id on the Odoo crm.lead references the pipeline stage created during schema setup.

FastTrack pipeline definitions map to Odoo crm.stage records within a crm.team. Each FastTrack pipeline becomes a named stage sequence in Odoo — stage records are created in the Odoo database first, and their integer IDs are used as stage_id values during deal import. Stage ordering in Odoo's kanban view is controlled by the sequence field on crm.stage.

FastTrack stage names map to Odoo crm.stage.name values via value-by-value mapping. Since Odoo stage names are Char fields (not pick-list controlled), FlitStack creates the stage records with the exact FastTrack stage names, then maps deal records to stage_id by matching the stage name. Probability values associated with each stage map to the probability field on crm.lead.

FastTrack owner IDs resolve to Odoo res.users records by email address match. Before migration, FlitStack generates a user-resolution report: matched users use their existing Odoo uid; unmatched owners are flagged so your Odoo admin can create the user record first or assign a fallback user before the migration run commits.

FastTrack engagement records (calls, emails, meetings) map to Odoo crm.activity records linked to the corresponding crm.lead by activity_type_id and res_id. Odoo's crm.activity model stores activity_type, note body (note/description), date_deadline, and user_id. Original timestamps, owners, and outcome/status fields are preserved. FastTrack email body content migrates as a mail.message record on the lead.

FastTrack file attachments on contacts, companies, or deals migrate to Odoo ir.attachment records linked to the target model (res.partner or crm.lead) via res_model and res_id. File name, mimetype, and binary content are preserved. Odoo Community stores files on the server filesystem; Odoo Enterprise uses attachment.storage='database' or 'file' depending on configuration.

FastTrack custom objects map to Odoo either as custom fields on existing models (res.partner or crm.lead) if the data is attribute-like, or as custom Odoo models if the custom object has its own relationships and sub-objects. Custom Odoo models require module development or Odoo Studio configuration — FlitStack generates the model definition as part of the migration plan.

FastTrack contact-to-deal association labels (Decision Maker, Champion, Influencer) have no direct Odoo equivalent. Odoo's crm.lead uses a partner_ids Many2many field for contact associations but does not natively support role labels. FlitStack preserves label names as a JSON array in a custom Char field (association_labels__c) on crm.lead for reference and future manual setup.