Migrate from Estimate Rocket to Odoo CRM

Estimate Rocket clients are individuals with a company_name text field. We split these: if company_name is non-empty and non-trivial, we create a res.partner with is_company=True (the company) and a linked individual res.partner with parent_id pointing to the company. If company_name is absent or generic (e.g., 'Residential'), the client lands as an individual res.partner.

Estimate Rocket stores address on the client record. We map street, city, state, zip, country to Odoo's street, street2, city, state_id (state_id is a Many2one to res.country.state), zip, country_id (Many2one to res.country). State and country require lookup by code/name since the stored values are free text in Estimate Rocket.

Client contact details map directly to Odoo partner fields. Email, phone, and mobile from Estimate Rocket transfer to res.partner.email, res.partner.phone, and res.partner.mobile respectively. No transformation is applied; the values are copied as-is into the destination fields during the migration load.

Each Estimate Rocket project becomes an Odoo crm.lead record with type='opportunity'. The project name becomes the opportunity name. Project status (Late, Today, Future) is not natively represented in Odoo — we preserve it as a custom Char field (ER_Project_Status__c) and optionally map to opportunity stage based on your defined stage set.

Odoo's create_date is set at migration time. To preserve historical context, we create custom datetime fields on the crm.lead: x_er_original_create_date holds the Estimate Rocket project creation date, and x_er_last_modified holds the last modification timestamp. This maintains reporting continuity for projects that originated months before the migration date.

An Estimate Rocket estimate attached to a project migrates as an Odoo sale.order in 'draft' or 'sent' state, linked to the opportunity (crm.lead) via the sale_order_ids field on the opportunity. The estimate total and any accepted status flags translate to Odoo's confirmation state.

Estimate Rocket line items (Name, Unit Price, Unit Cost, Section, Type, Taxable flag) map to Odoo sale.order.line records. Section maps to Odoo's name field with the section label prepended. Unit Price maps to price_unit. Taxable=True triggers tax_id lookup (Odoo's account.tax). Type (material/labor) is preserved in a custom Char field since Odoo line types require product configuration.

Estimate Rocket schedule entries with start/end times migrate to Odoo calendar.event records linked to the res.partner or crm.lead via res_model and res_id. Original timestamps and assigned user (user_id) are preserved. Estimate Rocket's address-directions feature has no Odoo equivalent — directions links are stored as plain text in the event description.

Estimate Rocket's Activity History (internal notes logged by team members) migrates to Odoo mail.message records attached to the res.partner or crm.lead. Each message preserves the author (user_id), create_date, and body text. Automations and reminders from Estimate Rocket do not migrate.

Estimate Rocket full users and field users are resolved by email against Odoo res.users. Unmatched users are flagged before migration; their records can be assigned to a fallback Odoo user or imported as res.partner-only records without login access. Field users without Odoo login access become contacts but cannot access the Odoo interface unless user accounts are created for them separately.

Any Estimate Rocket custom properties beyond the standard set (Name, Units, Description, Unit Price, Unit Cost, Section, Type, Taxable) are detected during the pre-migration audit and created as custom fields in Odoo using ir.model.fields with prefix x_er_ before the field name. Field type is inferred from Estimate Rocket's data type (Char, Integer, Float, Boolean, Selection).

Estimate Rocket workflows built in Zapier (e.g., new estimate → notify team, client signed → trigger invoice) do not migrate to Odoo. Odoo's Automations (ir.actions.server, base.automation) provide equivalent trigger logic but require manual rebuild. We export your Zap configuration as a written specification to support the rebuild.