Migrate from SalesPro CRM to Odoo CRM

SalesPro Contact records map directly to Odoo crm.lead (in Lead/Opportunity mode) or res.partner depending on Odoo CRM configuration. We preserve the contact's name, email, phone, company association, and address fields. SalesPro permission-based sharing settings have no direct Odoo equivalent; we recommend Odoo's Record Rules configuration in the Access Control menu post-migration.

SalesPro Company records map to Odoo res.partner with is_company = True. The SalesPro company-contact foreign key relationship maps to Odoo's child_ids on the parent Company partner record. Company Website and Industry fields from SalesPro map to Odoo's website and industry_id (industry_id requires a pre-loaded industry list that we configure during schema setup).

SalesPro Events with date ranges, group details, and BEO references map to Odoo calendar.event (for scheduling and resource tracking) and optionally to crm.lead records if the customer wants to track the event commercial outcome as a sales Opportunity. We capture event start/end dates, attendee lists, location, and description. The BEO reference is preserved separately as a lookup field.

BEO records are derived outputs from SalesPro Events and contain cost calculations, timeline details, and event specifications. Odoo has no native BEO object, so we create a custom Odoo model (x_beo_event_order) via the Settings > Technical > Models menu or via XML data migration, with fields for event_id (Many2one to calendar.event), cost_breakdown (HTML or Text), timeline_specs (Text), and signing_status (Selection). The event-to-BEO linkage is preserved as an explicit relational field rather than a derived computation.

SalesPro Task records with assignees, due dates, email reminders, and completion status map to Odoo note.note (for standalone tasks) or project.task (if Odoo Project is installed). We preserve assignee assignment via email-to-user lookup and set the task deadline to the original SalesPro due date. Reminder flags from SalesPro require Odoo mail.activity configuration post-migration.

SalesPro custom Milestones tied to the pipeline or individual deals map to Odoo crm.stage (if using CRM pipeline) or project.milestone (if using Project). We preserve milestone names, relative ordering, and the deal or project association. SalesPro's goal-based milestone definitions require translation into Odoo's stage logic, which we document as a configuration step.

SalesPro pipeline and stage configuration maps to Odoo crm.stage records within a crm.team (Sales Team). Stage names and their relative ordering migrate from SalesPro to Odoo in sequence. SalesPro's tier-dependent pipeline count (which is tier-limited in SalesPro) has no equivalent constraint in Odoo; Odoo supports unlimited pipelines per team. Custom stage names require field mapping documentation.

SalesPro users assigned to contacts, tasks, and events map to Odoo res.users by email address match. Owner reassignment during migration requires explicit user provisioning in Odoo before record import. Permission-based sharing flags from SalesPro map to Odoo Record Rules and Access Control Lists per object, which we configure as part of the schema setup. Inactive SalesPro users map to Odoo inactive users if historical assignment must be preserved.

SalesPro calendar entries map to Odoo calendar.event with start datetime, end datetime, and resource assignments preserved. SalesPro's resource booking fields map to Odoo's calendar.resource. We note that the SalesPro webhook-only API fires on calendar view opens, which means we cannot programmatically extract calendar data in real-time; the full calendar export relies on the formal vendor data request issued during the discovery phase.

SalesPro's live People Tracker dashboard generates time-stamped activity records that track task completion and deal milestone progress. These do not map to a standard Odoo object. We map People Tracker entries to Odoo mail.message records on the related crm.lead or project.task, preserving the timestamp, actor (user), and activity description as a message body. This preserves the live-activity visibility without replicating the dashboard itself.

SalesPro does not expose a bulk attachment export endpoint via its webhook API. Attachments associated with Events or BEOs require manual extraction from SalesPro or a direct vendor request. We notify the customer during scoping that attachments must be manually exported from SalesPro and provided as a file package, which we then import into Odoo ir.attachment records linked to the corresponding calendar.event or custom BEO record. Files without a matching parent record are stored in a temporary ir.attachment container for manual association.

SalesPro's event signing workflow includes a known bug that sometimes inserts spurious spouse signing fields even when no spouse data exists. We strip null-value spouse fields during the transformation step and map the remaining valid signing data (signer name, date, signature status) to custom fields on the Odoo BEO record (x_signing_party, x_signing_date, x_signing_status). Customers using the signing workflow receive a signed-field configuration guide for Odoo Studio.