Migrate from Zuper to Odoo CRM

Zuper customers map 1:1 to Odoo res.partner records. The partner_type field in Odoo is set to 'contact' for individuals and 'company' for business accounts. Address fields (street, city, state, zip, country) migrate directly via the address fields on res.partner. Phone, email, and mobile fields map to phone, email, and mobile on res.partner.

Zuper jobs are the core migration object. Each job becomes a crm.lead record where the opportunity name is the job title, the partner_id links to the Zuper customer (res.partner), and job-specific properties — job type, job status, priority, description — are stored in custom fields on crm.lead (job_type__c, job_status__c, job_priority__c, job_description__c). The crm.lead.stage_id field maps Zuper job statuses to Odoo pipeline stages.

Zuper job categories (configured in Settings > Jobs > Job Categories) have no native Odoo CRM equivalent. We create a custom selection field job_category__c on crm.lead with the exact Zuper category values preserved. If categories are hierarchical, we store the full path as a Char field and optionally create tags in Odoo (crm.tag) for cross-cutting categorization.

Zuper job statuses (New, In Progress, On Hold, Completed, Cancelled, etc.) map to Odoo crm_stage records. We create or reuse stages in Odoo's pipeline and assign each Zuper status value to the corresponding stage. Stage display names in Odoo can be customized to match Zuper's naming. Closed stages (Completed → Won, Cancelled → Lost) set the crm.lead.stage_id to the appropriate closed stage and the active flag is set accordingly.

Zuper teams map to Odoo crm_team records. The team name and description migrate directly. Members of the Zuper team are resolved by email against Odoo res_users — matched users are added to the crm_team via the crm_team_member relation table. Unmatched users are flagged and assigned to a fallback team or user until Odoo accounts are provisioned.

Zuper team members (assigned_user_id on jobs) map to Odoo res_users records. The mapping is resolved by email address — if a Zuper user email matches an existing Odoo user, their user_id is assigned to the crm.lead as the opportunity owner. If no match exists, the job owner is stored in a custom field job_owner_email__c and the record is assigned to a migration admin user.

Zuper custom fields created on customers become Odoo custom fields on res.partner using the Odoo Studio interface or model definition. Field types (Char, Integer, Float, Date, Selection, Many2one) are preserved. Selection-type custom fields replicate the Zuper pick-list values as options in the Odoo field. Many2one fields may require lookup tables in Odoo.

Zuper custom fields created on jobs migrate to crm.lead custom fields following the same type-preservation logic applied to customer custom fields. These fields extend the opportunity record with Zuper-specific data such as equipment_serial__c, service_contract_type__c, warranty_expiration__c, and parts_used__c that have no native Odoo CRM equivalent. Field definitions including selection pick-lists, date formats, and many2one relationships are recreated identically in Odoo Studio, ensuring data integrity and consistent downstream reporting.

Files attached to Zuper jobs (photos, PDFs, signed documents) are downloaded and re-uploaded to Odoo ir_attachment records linked to the corresponding crm.lead. The original filename, MIME type, and create date are preserved. Large files are chunked to respect Odoo's attachment size limits. Inline images from job notes are extracted and stored as separate attachments.

Zuper Workflow Builder and Guided Workflow definitions do not have a migration path to Odoo CRM. The workflow node structure, condition branches, and action chains are exported as a JSON reference document that Odoo developers can use to recreate equivalent automations using Odoo Studio, server actions, and scheduled actions. This is a manual rebuild step — we provide the map, not the automation.

Zuper timesheet entries linked to jobs have no native equivalent in Odoo CRM. We migrate them as internal notes (mail.message with internal=True) on the corresponding crm.lead, preserving the hours logged, date, user, and timeoff type. For teams that need formal timesheet tracking post-migration, we recommend enabling the Odoo Timesheets app and linking crm.lead to project tasks.

Zuper job locations (service address) that differ from the customer address are stored as a separate location record. We create a secondary address on the res.partner record using the 'Additional Addresses' feature, or store the location as a custom Char field on crm.lead (service_address__c) if the job is always at a different address than the partner record.