Migrate from improveit 360 to Odoo CRM

improveit 360 leads map to Odoo crm.lead records. The type field on crm.lead is set to 'lead' initially. Original lead status (New, Contacted, Qualified) maps via value_mapping to Odoo stage_id. improveit 360's duplicate-prevention flag is preserved as a custom boolean field on the Odoo lead.

improveit 360 contacts map to Odoo res.partner records. When improveit 360 stores a company on a contact, the company becomes a separate res.partner record with customer_rank set, and the contact becomes a child partner linked via parent_id. improveit 360's customer type (Residential, Commercial) maps to a custom field on res.partner.

improveit 360 companies map to res.partner records where customer_rank is set to indicate commercial accounts. Odoo stores company name in the name field, website in website, and industry in industry_id. Parent-child company hierarchies in improveit 360 map via Odoo's parent_id on res.partner. Multi-location companies require one partner record per location if improveit 360 tracks them separately.

improveit 360 deals convert to Odoo crm.lead records where type='opportunity'. The partner_id is set by matching the improveit 360 customer email to an Odoo res.partner. Deal amount maps to planned_revenue. The improveit 360 pipeline becomes Odoo CRM stages via crm.stage records scoped to the relevant sales team.

improveit 360 sale status navigation maps to Odoo crm.stage records. Each improveit 360 pipeline maps to a crm.team in Odoo, with its own set of stage records. We create the stage records in Odoo before migrating deals and set the sequence order to match improveit 360's stage ordering. Stage probability percentages can be set on each Odoo stage if improveit 360 tracks them.

improveit 360 activity logs migrate to Odoo mail.activity records linked to crm.lead or res.partner by res_model and res_id. improveit 360 calls map with activity_type_id set to 'call', emails with 'email', and meetings with 'meeting'. Original timestamps and durations are preserved. Meeting records also create corresponding calendar.event entries for Odoo's calendar view.

improveit 360 photos, contracts, and documents migrate as Odoo ir.attachment records. Each attachment stores the original filename, file content, and link (res_model=improvedit360.lead or res.partner). The attachment is linked to the corresponding Odoo record via res_id. improveit 360's document types (Photo, Contract, Proposal) map to custom mimetype or category fields on the attachment.

improveit 360 custom fields on leads — such as trade_type, lead_source_detail, referral_partner, or project_type — are created as custom fields on Odoo's crm.lead model before migration. Field types are matched: text fields to char/text, pick-lists to selection fields, numeric fields to float or integer. improveit 360 field values are then loaded into these new custom fields during the migration run.

improveit 360 custom fields on contacts and companies — such as trade_license, insurance_expiry, or bonding_capacity — migrate as custom fields on Odoo's res.partner model. If improveit 360 tracks properties per contact (e.g., lead_rating, customer_tier), these are created as selection or char fields on res.partner and populated during migration. Company-level custom fields (e.g., license_number) map to the parent res.partner record.

improveit 360 owner assignments resolve by email match to Odoo res.users records. If a user with the same email exists in Odoo, records are assigned to that user_id. If no match is found, records are assigned to a designated fallback user and flagged in the migration report for manual reassignment. improveit 360's user names (firstname + lastname) are used to create res_users records if Odoo accounts don't already exist.

improveit 360 project records (with job costing, scheduling, and cost tracking) do not have a direct Odoo CRM equivalent. These records are exported as a structured CSV reference file for manual rebuild in Odoo project.project or sale.order modules after the CRM migration. We preserve the project name, customer link, and estimated value fields as a separate export so the project context is not lost.

improveit 360 sales quotes with line items map to Odoo sale.order records, but Odoo sale.order requires product_id links and a product catalog that may not exist in improveit 360. We extract quote data (customer, amounts, line descriptions) into a structured CSV for import into Odoo sale.order after the product catalog is set up. Active quotes in improveit 360 are flagged for priority rebuild in Odoo.