Migrate from Thunderbolt Pipeline to Odoo CRM

Thunderbolt Pipeline contacts map to Odoo res.partner records. Email, phone, address, and job title fields transfer directly. Role type flags (General Contractor, Subcontractor, Supplier) migrate as partner category tags in Odoo for downstream segmentation. Contacts without a company link in Thunderbolt create standalone partner records.

Thunderbolt Pipeline company records map to company-type res.partner in Odoo. Company name becomes partner name, website maps to the website field, and address fields transfer directly. Employee count and annual revenue have no native Odoo equivalent and migrate as custom fields if that data exists in Thunderbolt. Parent-company hierarchies in Thunderbolt map to the parent_id field on res.partner.

Thunderbolt Pipeline allows contacts to be associated with multiple companies (N:N relationship). Odoo res.partner stores a single parent_id for the primary company link. We migrate the most recently modified company as the primary link and surface secondary company associations as notes on the partner record for manual rebuild in Odoo's Contact module if needed.

Thunderbolt Pipeline bid records become Odoo CRM leads. Bid amount maps to planned_revenue, bid stage maps to crm.stage, and bid owner resolves to crm.lead.user_id by email. Bid records without a primary contact link to the company partner record. Attachments re-upload as Odoo ir.attachment records linked to the crm.lead.

Thunderbolt Pipeline bid stages (Bidding, Under Review, Awarded, Lost, etc.) map to Odoo CRM stage records. Odoo stages must be pre-created with exact name matches before the migration runs, otherwise leads import with no stage or fail validation. Each Thunderbolt stage requires a corresponding Odoo stage ID in the value-mapping table.

Thunderbolt Pipeline bid owner resolved to Odoo res.users by email match. If the owner email does not correspond to an active Odoo user, the record is flagged and assigned to a fallback user or team lead. Owner resolution happens before bid records are imported to prevent orphaned leads without a responsible user.

Thunderbolt Pipeline file attachments on bid records re-upload as Odoo ir.attachment records linked to the corresponding crm.lead. Files download from Thunderbolt, re-upload to Odoo, and attach via the ir.attachment model. File size limits from Odoo apply (default 25MB per file for file storage; larger files require adjustments to Odoo file storage configuration).

Thunderbolt Pipeline notes on bid records become Odoo mail.message records on the crm.lead. Original timestamps and note authors are preserved in the mail.message fields create_date and create_uid. Notes import as plain text; rich-text formatting may simplify during import but the content and timing are preserved.

Thunderbolt Pipeline project records map to Odoo project.project. Project name, address, start date, and end date transfer directly. Contract value maps to the Odoo accounting module if Project plus Accounting are activated; otherwise stored as a custom Decimal field for reference. Projects without the Odoo Project module active import as crm.lead records with a project reference flag.

Thunderbolt Pipeline's Trade Category field (Electrical, Plumbing, HVAC, General, etc.) maps to Odoo partner categories. Partner categories must be pre-created in Odoo CRM before import with exact name matches. If a category name in Thunderbolt has no matching Odoo category, the record imports as uncategorized and is flagged for review.

License numbers or contractor certification IDs migrate as custom Char fields on res.partner. Requires Odoo developer mode to create the field or a custom module. The field name in Odoo follows the x_studio prefix convention (e.g., x_license_number). The custom field must be created before migration begins or the data is skipped during import.

Bonding limits migrate as custom Decimal fields on res.partner (for contractor info) or on crm.lead (for bid-level bonding requirements). The placement depends on whether the bonding info is a contractor attribute or a bid-specific requirement. Odoo developer mode or a custom module is required to create the field before migration runs.

Thunderbolt Pipeline lead source tracking (Website Inquiry, Referral, Trade Show, Bid Invite) has no native Odoo equivalent unless the Odoo Marketing module is activated. Without Marketing, source data migrates as a custom Char field on crm.lead for reporting reference. If Marketing is active, UTM source and medium tags are created and linked to the lead.

Thunderbolt Pipeline's workforce assignment feature (assigning workers or crews to bids) has no Odoo CRM equivalent. Assignments migrate as a custom Many2many field linking crm.lead to res.users, or as a text note on the crm.lead for manual entry. If the Odoo Project module is active, worker assignments can be tracked via project.task records linked to the opportunity.