Migrate from SalesTown CRM to Odoo CRM

SalesTown Leads are the primary acquisition object collected via auto-capture and smart distribution rules. They map 1:1 to Odoo CRM Lead records. The SalesTown lead status and source attribution migrate to Odoo's LeadStatus and Source fields. Any SalesTown custom fields on Lead records create Odoo custom field entries (char, integer, selection) before migration so that no source data is dropped at import time.

SalesTown Pipelines with configurable Stages map to Odoo CRM Sales Teams. We export the pipeline names, stage order, and stage-specific win/loss flags, then configure Odoo Sales Teams with the matching stage sequence before any Deal records load. If the customer has multiple SalesTown pipelines, we create one Odoo Sales Team per pipeline and attach the stage configuration to each.

SalesTown Stage records carry names, probabilities, and ordering per pipeline. We map each SalesTown stage explicitly to an Odoo Stage by name rather than by position, handling the common case where the source and destination have different stage counts. Stage probability percentages from SalesTown become Odoo Stage probability values. The Odoo stage sequence is ordered to match the SalesTown pipeline flow before Deals import.

SalesTown Deals carry amount, stage assignment, owner, and expected close date. They map to Odoo CRM Opportunity records. The Deal stage maps to Odoo Stage via the pipeline-to-Sales-Team resolution established in the stage mapping step. Closed-won and closed-lost reasons from SalesTown custom fields become Odoo Opportunity lost reason values. Deals are sequenced after Pipelines and Stages during migration to preserve stage associations.

SalesTown Contact records map 1:1 to Odoo CRM Contact. Standard fields (name, phone, email) transfer directly. Owner assignment migrates by email-based user reconciliation. Custom properties on SalesTown Contacts create corresponding custom fields in Odoo before import; we inspect the CSV export to identify all available fields and flag any that lack a clear Odoo equivalent for post-migration review.

SalesTown Company records map to Odoo Partner records with the is_company flag set to true. The SalesTown field schema is not publicly documented, so we inspect the export output to identify available company fields and map them to Odoo Partner fields (street, city, country, phone, website, vat). Any unmapped fields are flagged in the field inventory delivered alongside the migration.

SalesTown Activities are individual touchpoints linked to Contacts or Leads. WhatsApp activities include message status flags that lose thread-level association in flat CSV exports. We reconstruct thread relationships using timestamp ordering and sender IDs during the transform phase, then load individual activities into Odoo Chatter on the corresponding Lead, Contact, or Opportunity record. Calls migrate as Task records with subtype=call; emails migrate as mail.message records in Chatter; generic tasks migrate as Odoo Project Task entries linked to the CRM record.

SalesTown Users carry name, email, and team assignment. They map to Odoo Users by email address match. Any SalesTown Owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision before Deal and Activity imports resume. Duplicate email addresses in the destination Odoo instance block user creation and are flagged during scoping.

SalesTown custom communication templates exist in the product but have no documented schema. We export available template metadata (name, subject, body content) and attempt to map body structure to Odoo Email Templates using the mail.template model. Template body mapping is flagged as a post-migration cleanup task because template field naming conventions differ between platforms and may require manual adjustment in Odoo's template editor.

SalesTown CRM report and dashboard definitions are stored server-side with no documented export mechanism. We migrate the underlying data records (Leads, Deals, Activities) so that equivalent reports can be rebuilt in Odoo CRM. The customer receives a written inventory of the report types and dashboard configurations visible in SalesTown, along with recommended Odoo Reporting equivalents (Odoo Invoicing Reports, Sales Analysis, Pipeline Reports) for the admin to implement.

SalesTown LMS associations on Leads (routing rules, lead source attribution, distribution assignments) have no direct Odoo equivalent. We preserve LMS metadata as Odoo Tags on Lead records, preserving the assignment context for post-migration audit. If the customer requires full LMS rule recreation, this is scoped as a separate Odoo automation rebuild task outside standard migration scope.

If the SalesTown instance carries custom objects beyond the standard Contact, Lead, Deal, and Activity schema, we inspect the export for additional record types and map them to Odoo custom models. Odoo supports custom model creation via its Studio app or directly via the ir.model and ir.model.fields interfaces. We pre-create the destination schema including all fields and relational links before any custom object data is loaded.