Migrate from GBuilder to Odoo CRM

GBuilder contacts map to Odoo res.partner records with type='contact'. GBuilder company data embedded in the contact record becomes a separate res.partner (type='company') created first, then linked via parent_id. Address fields (street, city, country) map directly to Odoo address fields.

GBuilder company records become Odoo res.partner with type='company'. The commercial_partner_id field is set to the company record itself. Child contacts are linked via child_ids. GBuilder company hierarchies (parent/child) map to Odoo parent_id on res.partner — the parent must be migrated before children to avoid circular reference errors.

GBuilder deals split into Odoo crm.lead records where type='opportunity'. The partner_id on the opportunity links to the res.partner created from the GBuilder contact. Stage mapping uses a value-mapping table keyed on the GBuilder pipeline stage name. Planned revenue maps to Odoo planned_revenue; close date maps to date_deadline.

GBuilder unqualified prospects (not yet deal-qualified) migrate as Odoo crm.lead with type='lead'. Priority, source information, and any custom fields carry over as x_ custom fields. The partner_id is only set if the lead already has an associated GBuilder contact record.

GBuilder pipeline stages map to Odoo crm.stage records scoped per crm.team. Each sales team in Odoo can have its own stage sequence; FlitStack maps GBuilder stage names to the appropriate team-stage mapping. Stage-entered timestamps are preserved as x_studio_datetime custom fields on crm.lead because Odoo does not maintain a native stage-history table.

GBuilder logged activities (calls, emails, meetings) migrate as Odoo mail.activity records with activity_type_id matching the GBuilder activity category. The res_model is set to 'crm.lead' and res_id to the target opportunity or lead. Original activity date and responsible user_id are preserved via email matching on the owner field.

GBuilder notes and log entries become Odoo mail.message records on the crm.lead. The message_type is set to 'comment' and body carries the note text. Attachments embedded in notes are extracted and reattached as ir.attachment records linked to the message.

GBuilder file attachments are downloaded from GBuilder's storage, re-uploaded to Odoo's ir.attachment table with res_model='crm.lead' or 'res.partner' and the corresponding Odoo record ID. Odoo's default file size limit is 25MB per attachment; larger files are flagged for manual handling.

GBuilder custom properties are recreated as Odoo custom fields (x_ prefix via Odoo Studio or Python-defined in a custom module). Field type mapping is required: text properties become char/text fields, date properties become date fields, pick-list values become selection fields. Custom fields must be created in Odoo before the migration loads data into them.

GBuilder owner or assigned user is resolved by email matching against Odoo res.users. Unmatched owners are flagged before the migration runs; their records are assigned to a fallback user or held for manual reassignment. Odoo user_id on crm.lead sets the opportunity owner.

GBuilder teams or groups map to Odoo crm.team records. Team members are linked via res.users membership in the team. Odoo team stages are associated with the team via team_id on crm.lead; pipeline stage visibility is scoped by team membership.

GBuilder N:N contact-to-company associations require flattening to Odoo's hierarchical model. The primary company becomes parent_id on res.partner; secondary companies are surfaced as Account Contact Relationships (a separate Odoo model) or via the partner_id on crm.lead. Your admin chooses which association model to use during the planning phase.