Migrate from Shark Byte CRM to Odoo CRM

Shark Byte Customer records (representing the end-client organization or homeowner for service work) map to Odoo res.partner records with partner_type set to 'contact' for the organization entity. Standard fields including company name, address, phone, and email map directly. The customer_id in Shark Byte becomes the Odoo partner's external_id for dedupe validation. We apply Odoo's partner deduplication on (email, website_domain) during import to prevent duplicate organization records.

Shark Byte Contact records (individual points of contact at each Customer site with name, phone, email, and role) map to Odoo res.partner records with partner_type set to 'contact' and parent_id referencing the linked organization partner. Role and title fields migrate to Odoo's function and title fields. We resolve parent_id references during import so that every Contact is correctly attached to its parent Organization partner, satisfying Odoo's partner hierarchy requirement.

Shark Byte Estimates are the core product object and include line items, labor rates, material costs, and contract-term classification (1-3 year, 3-5 year, 10+ year). We map Estimates to Odoo crm.lead records and create custom selection fields x_contract_term (for the term bucket), x_labor_rate, x_material_cost, and x_equipment_spec on the crm.lead model. The Estimate's total amount and line item count are stored as Odoo custom fields. We do not migrate the Shark Byte pricing engine itself; the customer documents their pricing logic for Odoo configuration post-migration.

Shark Byte Proposals are generated from Estimates and include pricing, scope, and terms. Each Proposal record maps to an Odoo crm.lead capturing the proposal status (draft, sent, accepted, lost), estimated value, and linked customer. The Proposal PDF (if generated in Shark Byte) migrates as an Odoo ir.attachment linked to the crm.lead via res_model='crm.lead' and res_id set to the lead's ID. Proposal-to-Estimate linkage is preserved via the custom x_source_estimate_id field on the crm.lead.

Shark Byte Service Agreements represent recurring maintenance contracts with 1-3 year, 3-5 year, and 10+ year term buckets. We create a custom Odoo model (x_service_agreement) inheriting from crm.lead via model inheritance, with fields for agreement_term, annual_value, start_date, end_date, and equipment_list. The crm.lead's name field stores the agreement title and the x_contract_term field captures the term bucket classification. Active and expired agreement status is preserved in the migration.

Shark Byte Work Orders track individual jobs dispatched to technicians with status, assigned technician, line items, and mobile survey attachments. We map Work Orders to Odoo project.task records within a dedicated Project record created during migration setup. Work order status (pending, in_progress, completed, cancelled) maps to Odoo task.stage_id with a stage sequence. Technician assignment migrates as task.user_id resolved against the User table by email. Work order line items migrate as task description notes or to a related sale.order if the Work Order feeds into a billing document.

Photos and site condition data captured via Shark Byte's mobile surveying tools are attached to Work Orders and Estimates. We extract all available attachments at original resolution from Shark Byte exports and create Odoo ir.attachment records linked to the corresponding project.task (for Work Orders) or crm.lead (for Estimates). Image format, compression, and EXIF metadata vary based on the source mobile device; we extract at the highest available fidelity and note that some images from older surveys may be compressed or missing EXIF data. This is documented in the migration validation report.

Shark Byte Proposal PDFs generated from Estimates are exported and attached to the corresponding crm.lead in Odoo via ir.attachment with res_model='crm.lead'. The PDF file name is preserved to indicate proposal version and date. If Shark Byte does not generate PDFs directly, we flag this and the customer generates proposals post-migration using Odoo's proposal template builder.

Shark Byte CRM supports custom fields on Estimates and Service Agreements to capture industry-specific data like equipment specifications, refrigerant type, tonnage ratings, or contract classification. We create equivalent custom fields on the Odoo crm.lead model (x_equipment_type, x_refrigerant_type, x_tonnage_rating) using Odoo's web interface or XML data migration before importing Estimate data. Field type mapping (text to char, number to float, date to date) is validated during the Sandbox phase.

Service Agreement custom fields for contract classification, equipment schedules, and compliance flags migrate to the x_service_agreement custom model. We create these fields during schema setup, validate type mapping in the Sandbox phase, and import the values during the main migration. Custom fields that reference other Shark Byte objects are resolved via the external_id lookup during import to maintain referential integrity.

Shark Byte Owner records (technicians and sales reps) map to Odoo res.users by email address. Any Owner without a matching Odoo User is placed in a reconciliation queue for the customer to provision before record import. Inactive Owners in Shark Byte map to Odoo Users with active=False so that historical assignment is preserved without licensing impact.

Shark Byte Workflows and automations are vertical-specific (service agreement renewal reminders, technician dispatch rules, estimate approval flows) and do not have a documented export mechanism. We deliver a written inventory of every active Shark Byte workflow including its trigger, conditions, actions, and recommended Odoo Automations or Studio action equivalent. Odoo Automations (the successor to server actions and scheduled actions) rebuild is outside the migration scope and requires the customer's Odoo admin or an Odoo partner.