Migrate from solve 360 to Odoo CRM

Solve 360 Contacts map to Odoo res.partner records with partner_type=contact. We extract name, email, phone, mobile, street, city, state, zip, country, and lifecycle properties. Solve 360's relationship linking to a Company record becomes the parent_id field on res.partner. Any user-defined custom fields on Contact migrate as custom res.partner fields of the corresponding type (char, float, date, selection). The migration user must have Odoo admin rights to create custom fields via Settings > Technical > Custom Fields.

Solve 360 Companies map to Odoo res.partner records with company_type=company. The company domain becomes the Website field and is used as a dedupe key during import. Company records are created before Contact records to satisfy the parent_id foreign key. Custom fields on Companies migrate as custom res.partner fields. Address fields (street, city, state, zip, country) migrate directly to Odoo's address format using the public API address fields.

Solve 360 Support Requests do not have a direct Odoo equivalent without the Helpdesk app. If the customer has the Odoo Helpdesk app installed, Support Requests map to crm.helpdesk.ticket with subject, description, priority, and status migrated. If Helpdesk is not installed, we map to crm.lead with the lead source set to 'Support Request Migration' and the original request description stored in the description field. The customer selects the strategy during scoping based on their Odoo edition and whether they plan to use Helpdesk post-migration.

Solve 360 Tasks map to Odoo project.task. The task name becomes project.task name, status maps to Odoo stage_id (New, In Progress, Done, Canceled), priority maps to priority (0-4, where Solve 360 high=4, normal=3, low=2), and the assignee maps to user_id via email resolution against Odoo Users. Due dates, time tracking (hours logged), and billable flags migrate as custom fields or standard Odoo fields depending on whether the Project app is installed. If Project is not installed, Tasks migrate to CRM activities instead.

Solve 360 Follow-ups are time-stamped activity records tied to a Contact or Company. If Odoo VoIP or CRM phonecall app is installed, they map to crm.phonecall with subject, date, duration, and notes. Otherwise, they map to mail.activity with activity_type_id set to the nearest Odoo standard type (call, meeting, email). The related partner_id is resolved from the Contact or Company mapping. Follow-ups without a linked Contact or Company are flagged in the reconciliation report for the customer to assign.

Solve 360 category tags are exported as a tag list per record and re-applied as Odoo native tags. Odoo CRM tags live on crm.lead and are stored in crm.tag. Project tags live on project.task. We map tags by object: Contact/Company tags become crm.tag records; Task tags become project.tags. Solve 360's tag-triggered form field behavior (where selecting a tag reveals additional fields) has no Odoo native equivalent and requires a custom Python module or Odoo Studio configuration to approximate.

Solve 360 Users are both system actors and assignment targets. We extract the user list and map owner_id references to res.users via email match. Any Solve 360 Owner without a matching Odoo User is held in a reconciliation queue; the customer provisions the Odoo User before record import resumes. Active/inactive status maps from Solve 360 to the Odoo active flag.

Solve 360 supports user-defined custom fields on Contacts, Companies, Tasks, Follow-ups, and Support Requests with types including text, number, date, and selection. We export field definitions (name, type, selection options) and create matching custom fields in Odoo via Settings > Technical > Custom Fields before data import. Selection fields map to Odoo selection fields with matching key-value pairs. Date fields map to Odoo date fields. Number fields map to Odoo float or integer depending on the field content.

Solve 360 pipeline stages map to crm.stage records within the customer's Odoo Sales pipeline. Stage names, sequence order, and probability percentages migrate to name, sequence, and probability on crm.stage. The customer configures the pipeline (sales team assignment, team stages) in Odoo before migration if they require multiple pipelines; otherwise all deals migrate into the default Sales pipeline.

Attachments on Contacts, Companies, Tasks, and Support Requests are downloaded as files and re-uploaded to Odoo via the ir.attachment API. Each attachment is linked to its parent record (res.partner, project.task, crm.helpdesk.ticket) via res_model and res_id. File metadata (name, mimetype, create_date) is preserved. Attachments exceeding 25 MB are flagged for the customer to store separately if Odoo file storage limits are a concern.

Solve 360 Workflow definitions encode logic specific to its automation engine (task sequences, intelligent scheduling, assignee notifications). We export all active workflow definitions as structured JSON including trigger conditions, step sequences, delays, and action types. This JSON is delivered as a migration artifact. Workflows cannot be replayed in Odoo because Odoo Automated Actions and Studio workflows use a different trigger and action model. The customer's Odoo admin rebuilds workflows using Odoo Studio or server actions; we provide the JSON as a reference specification.

Solve 360 allows a third custom record type (Work Orders, Cases, Sites, Properties, Projects) with its own fields and tags. Odoo has no native equivalent without custom module development. We map this record type to crm.lead with a custom type field (x_solve_type) to preserve the original record type designation, or to project.project if the custom type is project-oriented. The customer selects the target during scoping. Custom fields specific to the third record type migrate as custom fields on the target model.