Migrate from Goals.com to Odoo CRM

Goals.com leads (inquiry captures, filtered and graded prospects) map to Odoo crm.lead records in Lead stage. The Goals.com lead generation source (inbound inquiry, filtered, graded) migrates as a custom selection field on crm.lead because Odoo does not have an equivalent lead grading concept. We preserve Goals.com lead owner assignment as crm.lead.user_id by resolving the email match to an Odoo res.users record. Grading scores and source attribution become custom Char or Float fields on the crm.lead model.

Goals.com Deal records map to Odoo crm.lead records in Opportunity mode (type='opportunity'). The Goals.com dealstage property maps to crm.lead.stage_id by matching stage names against Odoo's CRM Stage configuration. Deal value, expected close date, and owner migrate to planned_revenue, date_deadline, and user_id respectively. We set crm.lead.type='opportunity' for all Deals and type='lead' for all Leads so Odoo's pipeline kanban view reflects the correct record grouping.

Goals.com pipeline stages (standard pipeline movement states) map to crm.stage records within the appropriate Odoo crm.team. We create stages in Odoo matching the Goals.com stage labels and assign probability percentages based on the Goals.com stage configuration. Stage order is preserved by setting sequence values. If Goals.com uses custom stage names, we create matching Odoo stages rather than renaming to Odoo defaults to preserve reporting continuity.

Goals.com Sales Goals (call volume, email count, and revenue targets per rep or team) have no native Odoo CRM equivalent. We offer two migration paths: (1) create custom float fields on crm.lead (target_calls__c, target_emails__c, target_revenue__c) and link goals to the assigned sales rep as a linked record, or (2) create Project tasks with target values linked to the Goals.com rep as a project assignee. The customer chooses during scoping. Progress percentages are recalculated post-import using Odoo computed fields.

Goals.com commission records (payout amounts, calculation basis, rep attribution) do not map to a native Odoo object. We create custom decimal fields on crm.lead (commission_amount__c, commission_basis__c) and optionally on res.users (commission_rate__c) to preserve historical commission data. Active payout rules and scoring logic do not transfer; we deliver a commission schema template specifying fields, formulas, and Odoo Payroll/HR configuration steps for manual rebuild.

Goals.com user accounts with role assignments (manager vs rep) map to Odoo res.users. We resolve by email match. Goals.com manager/rep roles map to Odoo access groups: managers receive CRM Group: User: All Leads, and reps receive CRM Group: User: Own Leads. Territory and region assignments from Goals.com become custom Char fields on res.users or are mapped to crm.team membership depending on the customer's team structure.

Goals.com notes, reminders, and customer interactions map to Odoo crm.lead.activity records (the next activity system on crm.lead). Each Goals.com activity becomes a mail.message or crm.lead.activity with activity_type_id, note, and date_deadline preserved. Goals.com activity timestamps map to crm.lead.activity.date_deadline. Full historical audit trails (every system event) are not available from Goals.com; we migrate the accessible activity log entries and flag any gaps in the reconciliation report.

Goals.com team structures for performance visibility and contests map to Odoo crm.team records and res.groups. Team membership is preserved as crm.team member assignments on res.users. Sales managers from Goals.com become crm.team leader assignments. Contest group logic (how teams compete) is not a native Odoo feature; we map team membership only and flag contest structure for manual rebuild or third-party gamification apps.

Goals.com contest configurations (active scoring rules, point allocations, leaderboard logic) are stored as application rules rather than data records. We export historical contest results and performance scores as CSV data preserved in a custom Odoo model (contest_result__c) with fields for contest name, period, rep, points, and rank. Active contest rules and leaderboard logic cannot transfer; we deliver a written contest schema template listing all extracted fields, the Odoo custom model definition, and step-by-step Studio configuration for rebuilding active contests.

Goals.com file attachments associated with deals, contacts, or activities map to Odoo ir.attachment records linked to the corresponding crm.lead or res.partner via res_model and res_id. We export attachment content and filename, create ir.attachment records with the correct model reference, and store binary content in Odoo's filestore. Large binary attachments (over 10MB) may require separate file transfer outside the standard Odoo import mechanism.

Goals.com does not have a distinct Company object separate from contacts; the company context is embedded in deal and lead records. We create Odoo res.partner records in partner_type='company' for each unique company name encountered in Goals.com deals and leads, then link the corresponding contact-level res.partner records (type='contact') as children of the company record. This establishes the Odoo standard partner hierarchy.

Historical Goals.com leaderboard snapshots (rep rankings, point totals, period dates) migrate to a custom Odoo model (contest_result__c) created during migration. Fields include contest_name, period_start, period_end, user_id, total_points, and rank. This data preserves historical performance records but does not recreate the live leaderboard functionality, which requires Odoo automation rules or a gamification app post-migration.