Migrate from SprintHub to Odoo CRM

SprintHub Lead records map to Odoo crm.lead records. The Odoo crm.lead model serves as both the unqualified prospect record and the opportunity record depending on its stage; when a SprintHub Lead has progressed past initial qualification it becomes an Opportunity in Odoo CRM. We extract the SprintHub lead status, owner assignment, and tag associations and map them to crm.lead stage, user_id, and tag_ids respectively. Custom properties on SprintHub Leads migrate as custom.char, custom.selection, or custom.float fields on crm.lead depending on data type. We resolve the SprintHub owner email against res.users in Odoo to populate user_id at import time.

SprintHub Contacts map to Odoo res.partner records. Odoo uses a single partner model for both individuals and organizations; we distinguish person partners (is_company = False) from company partners (is_company = True) using SprintHub's contact type metadata. SprintHub contact associations with Companies generate the same res.partner record with child contact records if the contact is an employee at a company. Address fields (street, city, state, zip, country) map directly. Custom contact properties migrate as custom fields on res.partner. Email and phone fields map to email and phone without transformation.

SprintHub Company records map to Odoo res.partner with is_company = True. Company name maps to name, industry metadata maps to industry_id (using Odoo's industry res.partner.industry reference), and company size metadata maps to a custom.field for employee_count if the Odoo installation lacks the contacts_rating module. We create the Company partner record before importing SprintHub Contacts so that the parent_id relationship is satisfied at the moment of Contact insert. The res.partner record type distinguishes customer, vendor, or other categories based on SprintHub's company type field.

SprintHub Deal records map to Odoo CRM opportunities. If Odoo CRM is installed as a standalone app (without the full sales module), deals map to crm.lead records with stage set to the corresponding pipeline stage. If the Odoo Sales app is installed, deals map to crm.opportunity records with the Opportunity Type and StageName resolved from the SprintHub pipeline. Deal value maps to expected_revenue, closed date maps to date_closed, and probability maps from the SprintHub stage probability percentage. We preserve SprintHub deal custom properties as custom fields on the target Odoo record.

SprintHub Pipeline definitions (name, stage count, stage order, stage probabilities) map to Odoo CRM stages scoped by crm.team. Each SprintHub pipeline becomes an Odoo crm.team, and each SprintHub stage within that pipeline becomes a crm.stage attached to the team. We extract stage names as Odoo stage names and stage probabilities as stage probability percentages. If SprintHub has multiple pipelines with overlapping stage names (e.g., 'Negotiation' appears in Pipeline A and Pipeline B), we namespace them with pipeline prefixes to prevent Odoo stage collisions.

SprintHub stage configurations (name, order, win/loss flags, probability) migrate as Odoo crm.stage records with sequence order, name, and probability fields populated from the SprintHub stage definition. Stage-specific actions or SLAs that existed in SprintHub are documented for manual Odoo rebuild using Studio Automated Actions. Loss reason and win reason fields in SprintHub become Odoo lost_reason text fields on the opportunity record.

SprintHub tags are global across the instance and attach to Leads, Contacts, and Companies. We extract the full tag list including color metadata and import it as Odoo crm.tag records. Tag associations on SprintHub records migrate as crm.tag.rel many2many records linking the crm.lead or res.partner to the corresponding crm.tag. Tags with identical names across different SprintHub objects merge into a single Odoo tag record. Color metadata from SprintHub is stored as a custom.color field on crm.tag.

SprintHub's multi-account WhatsApp configuration (account-to-team routing, conversation assignment rules, and channel routing logic) has no native Odoo equivalent. Odoo does not include a native WhatsApp channel module in its standard CRM or social modules. We extract the full WhatsApp account list, routing rules, and conversation-to-account mappings from SprintHub as a structured JSON document and a written channel inventory for the customer's admin to rebuild using a third-party Odoo WhatsApp integration (such as those available on the Odoo Apps store) or a custom development. We preserve the WhatsApp conversation history separately as documented attachments for re-import if the chosen WhatsApp integration supports message import.

SprintHub automation rules (triggers, filter conditions, multi-step action sequences) are stored in a proprietary JSON format. We extract the full automation definition including trigger events, condition logic, action types, and delay steps as a structured JSON export plus a written inventory document. Odoo Studio's Automated Actions and Server Actions provide equivalent functionality but require manual rebuild because the automation engine, trigger model, and action library are platform-specific. We do not migrate workflows as executable code; the customer receives the automation inventory as a rebuild guide for their Odoo admin or implementation partner.

SprintHub social media campaign records (campaign name, start/end dates, metrics, post histories) map to Odoo utm.campaign records for attribution tracking and crm.lead records if SprintHub campaign data includes prospect records. Campaign metrics (impressions, clicks, reach) migrate as custom fields on utm.campaign because Odoo's standard UTM module tracks only source, medium, and campaign attribution rather than social-specific metrics. Attribution settings require manual reconfiguration in Odoo's marketing module if the customer installs it.

SprintHub custom field definitions (field name, data type, picklist options, required/optional flag) are extracted as a schema document and mapped to Odoo custom fields. String fields map to custom.char, multi-line text to custom.text, numeric values to custom.float or custom.integer depending on precision, dates to custom.date, and picklist fields to custom.selection with the SprintHub picklist options as Odoo selection tuples. Custom fields are created in Odoo before data import using Odoo Studio or direct model definition. We validate that target Odoo model exists and that field names do not conflict with Odoo reserved field names before creation.

SprintHub engagement history (calls, emails, meetings, tasks) maps to Odoo's activity and communication models. Call engagements map to crm.phonecall records (if the phonecall module is installed) or to mail.activity records with activity_type = call. Email engagements map to mail.message records linked to the res.partner or crm.lead record. Meeting engagements map to calendar.event with attendee_ids resolved to res.partner records. Task engagements map to crm.lead.task or mail.activity records. We resolve the SprintHub contact reference to the Odoo partner_id at migration time using the partner mapping. Timestamp ordering is preserved by setting create_date to the original SprintHub engagement timestamp.

SprintHub Owner records (assigned reps and admins) map to Odoo res.users by email address match. We extract every distinct owner referenced on Leads, Contacts, Companies, Deals, and Engagements and resolve them against the destination Odoo instance's user list. Any SprintHub owner without a matching Odoo user is placed in a reconciliation queue, and the customer provisions the missing users before record import proceeds. Inactive SprintHub owners map to inactive Odoo users if the customer wants to preserve historical assignment.