Migrate from Urban-Hawks to Odoo CRM

Urban Hawks contacts map directly to Odoo res.partner records. Odoo treats contacts and companies as the same model — the is_company boolean field distinguishes a company record from an individual contact. Contacts without a primary company receive a placeholder partner record.

Urban Hawks companies map to Odoo res.partner records with is_company=True. The N:N relationship between Urban Hawks contacts and companies collapses to a single parent_id link on each contact partner — one primary company per contact, with secondary companies stored in partner relations.

Urban Hawks leads map to Odoo crm.lead records with type='lead'. The lead's name, contact name, email, phone, and source information transfer directly, and its status maps to a crm.stage via value‑mapping. Odoo creates a corresponding res.partner from the lead contact data automatically if it does not already exist; otherwise the lead links to the existing partner.

Urban Hawks opportunities map to Odoo crm.lead records with type='opportunity'. The opportunity name becomes the crm.lead name, amount maps to planned_revenue, probability is taken from source probability field, and close_date maps to date_deadline. Stage names are translated via value‑mapping to Odoo crm.stage records, and the owner is resolved by email match to Odoo res.users. If the linked contact does not yet exist in Odoo, a new res.partner record is created.

Urban Hawks pipelines map to Odoo sales teams (crm.team). Each pipeline's stages map to crm.stage records within that team, preserving stage order and probability values. Teams with multiple pipelines in Urban Hawks spawn multiple crm.team records in Odoo, each with its own stage configuration and members. The pipeline name becomes the team name, and the default stage for new leads is set to the first Odoo kanban stage.

Urban Hawks call records map to Odoo mail.activity with activity_type_id set to 'call'. The call duration, outcome, and notes transfer to the activity's fields, while the original timestamp becomes the activity's date. The activity is linked to the parent crm.lead or res.partner, and the owner is resolved by email match to Odoo res.users. If the caller contact is not yet a partner, a new res.partner record is created.

Urban Hawks email records map to Odoo mail.activity with activity_type_id set to 'email'. The email subject becomes the activity's display name, and the body is stored as the activity's note field. The original timestamp is preserved, and the owner is resolved by email match to Odoo res.users. The activity is attached to the corresponding crm.lead or res.partner, creating a full communication history in Odoo.

Urban Hawks meeting records map to Odoo calendar.event with start datetime, stop datetime, and name as the event title. The meeting description and location are transferred to the event's description field. Attendees are resolved by matching the meeting's invitee emails to Odoo res.partner records, populating partner_ids. The organizer is set by matching the original owner to an Odoo res.users record.

Urban Hawks notes map to Odoo mail.message records attached to the crm.lead with message_type='comment'. The original creation timestamp and author are preserved, and the note text becomes the message body. If the note contains file attachments, they are re‑uploaded as ir.attachment records linked to the same crm.lead, preserving the original file name and MIME type.

Urban Hawks custom properties for AR annotations, technician assignments, and service-ticket metadata require Odoo custom fields created via Odoo Studio or a custom module. Some field-service attachments (AR snapshots, diagnostic files) migrate as ir.attachment records linked to the parent crm.lead.

Urban Hawks file attachments are re‑uploaded to Odoo ir.attachment records linked to the parent res.partner or crm.lead. Each attachment preserves its original file name, MIME type, and binary data (datas_base64). The Odoo filestore size limits apply per instance configuration; files exceeding the limit are flagged for manual upload after migration.

Urban Hawks owner IDs are resolved by matching the owner email to Odoo res.users. If a match is found, the Odoo user_id is assigned to the record; if not, the owner is flagged and the record is assigned to a fallback Odoo user or placed in a staging queue for manual resolution. All resolution decisions are logged in the migration audit trail for traceability.