Migrate from The Service Manager to Odoo CRM

Direct map for individual contacts. Odoo res.partner is a unified model for both persons and organizations — company_type='person' flags individual contacts. Partner records must exist before any opportunity references them via partner_id. Email match resolves owner to an Odoo user.

Direct map for organizations. Odoo res.partner with company_type='company' represents the organization. Address fields (street, city, country) map as separate fields on the same partner record. Parent-company hierarchy resolves via parent_id in a sequenced import to avoid orphaning. This ensures referential integrity across the imported dataset.

The Service Manager tickets have no native Odoo equivalent. The ticket ID, priority, status, and description migrate as custom fields on crm.lead (x_tsm_ticket_id, x_tsm_priority, x_tsm_status). Your Odoo administrator recreates tickets natively in Odoo's helpdesk module post-migration as a separate workflow.

Incidents map to crm.lead with incident-specific fields stored as custom properties. The resolved date becomes x_tsm_resolved_date; incident category maps to a custom selection field. Odoo's crm.lead type='lead' is used for unresolved incidents carried forward. These custom fields enable tracking and reporting of incident metrics within Odoo's analytics tools.

Change requests migrate as crm.lead records with x_tsm_change_id and a custom change_type field. If the change request relates to a specific opportunity, the res_id links to the corresponding crm.lead record. Approval history is preserved as a custom note field. for audit trails and compliance review.

The Service Manager assignment groups contain multiple members. FlitStack AI resolves each group's primary member to an Odoo res.users record by email. If no match exists, the record is flagged for admin review before migration — no opportunity lands without a resolved owner_id.

Odoo CRM has no native SLA tier equivalent for leads. SLA tier names from The Service Manager migrate as a custom selection field (x_tsm_sla_tier) on crm.lead. Post-migration, your team can configure Odoo's helpdesk SLA features if upgrading to the Service Desk module.

Logged calls, emails, and meetings from The Service Manager map to Odoo mail.activity records. activity_type_id differentiates call (phone), meeting (meeting), and email (email) types. user_id is resolved by email match; date_deadline carries the scheduled or completed date. The activity's res_model='crm.lead' and res_id point to the related opportunity.

File attachments associated with tickets or contacts migrate as ir.attachment records. res_model='crm.lead' for opportunity attachments; res_model='res.partner' for contact attachments. res_id holds the target record's database ID. Binary content is re-uploaded; inline images in notes are extracted and stored as separate attachments.

Any custom fields defined in The Service Manager that have no Odoo equivalent become custom fields on the target Odoo model (crm.lead or res.partner). FlitStack AI creates these fields before migration using Odoo's custom field API. Field type is preserved: text stays text, selection stays selection, date stays date.

The Service Manager users and technicians are matched to Odoo res.users by email address. Inactive or deactivated users in Odoo are excluded from matching and flagged. If a technician has no corresponding Odoo user, their records are assigned to a designated fallback user and noted in the migration report.

The Service Manager allows a contact to belong to multiple companies. Odoo's res.partner model supports one parent_id (the primary company). FlitStack migrates the primary association as parent_id on the contact partner record. Secondary company associations are stored as a custom note field (x_tsm_secondary_companies) for manual reconciliation if needed.