Migrate from CentralStationCRM to Odoo CRM

CentralStationCRM People map to Odoo CRM Lead if the record has no attached Deal and is pre-qualification, and to Odoo CRM Contact if the record has an active Deal or has been worked by a sales rep. We apply a Deal-attachment heuristic during scoping: People with at least one non-closed Deal become Contacts; People with no Deal attachment and no contact history become Leads. The original CentralStationCRM record ID is preserved in a custom field csrm_id__c on both Lead and Contact for cross-system audit.

Odoo uses the res.partner model for both individual contacts and companies; companies are distinguished by the is_company flag set to True. CentralStationCRM Company records map to Odoo Partner records with is_company=True and child contact records created for each related Person. The company name, domain, and address fields transfer directly; website becomes the Partner's website field used as the dedupe key.

CentralStationCRM Deals map to Odoo CRM Opportunity. The deal stage maps to an Odoo CRM Stage, and we pre-create stages matching the source pipeline before migration. Deal value, expected close date, and assigned owner transfer to the Opportunity's planned_revenue, date_deadline, and user_id fields. CentralStationCRM Deals attached to a Person without a Company create Opportunities linked directly to the Contact; Deals attached to a Company link to a Company-level Opportunity.

CentralStationCRM's standalone Lead object maps directly to Odoo CRM Lead. Lead status (new, contacted, qualified, lost) maps to Odoo's Lead Status field, and any lead score from CentralStationCRM custom fields transfers to a custom csrm_lead_score__c field on the Odoo Lead. If the destination Odoo instance has no CRM app installed, Leads migrate as Contacts in the base Odoo Contacts module.

CentralStationCRM Activity records map to Odoo CRM Activity records linked to the migrated Lead or Contact via res_id and res_model. Activity type (call, meeting, note) maps to Odoo's activity_type_id; title becomes the activity's summary; description becomes the note body. Odoo allows one activity type per record, so multi-type CentralStationCRM activities on a single date are split into individual Odoo activity records.

CentralStationCRM's flat tag vocabulary maps to Odoo CRM Tags (crm.tag model). Tags are applied to Leads and Opportunities via crm.tag.rel. The tag vocabulary transfers as-is; Odoo supports unicode tag names so German-language tags from CentralStationCRM import without transformation. Tags with special characters (e.g., ampersands) are sanitized to Odoo's allowed character set.

CentralStationCRM tenant-defined custom fields have no fixed schema and require explicit mapping to Odoo custom fields. We discover all custom fields at the source during scoping, create matching custom fields on the appropriate Odoo model (res.partner, crm.lead, crm.lead) using Odoo's Settings > Technical > Fields interface or XML data, and map each field's type (text, number, date, select) to the closest Odoo field type before migration begins. Custom fields must exist in Odoo before any data containing them is imported.

CentralStationCRM Tasks attached to People or Deals map to Odoo CRM Activities (activity type Task) linked to the parent Contact or Opportunity. Task title, due date, and status (open/done) transfer directly. Completed state from CentralStationCRM maps to Odoo's activity's completed status with the completion date preserved. If the destination Odoo instance uses the Project app for task management, tasks attach to a default project created during migration.

CentralStationCRM Offers map to Odoo Sale Orders in Quotation state. Offer line items (product, quantity, unit price, discount) map to Odoo sale.order.line records linked to the Sale Order. Offer totals, tax amounts, and validity dates transfer to the corresponding Sale Order fields. Because CentralStationCRM Offers are standalone and not tied to Odoo's product.price.list model, we create Product records during migration for any Offer line items referencing unnamed products.

CentralStationCRM addresses live as nested child records fetched via GET /api/people/{id}/addrs.json and are not included in the parent Person record. We traverse each nested address route during export, then write address fields (street, city, zip, country) to the Odoo Partner's address fields (street, city, zip, country_id). Multiple addresses per contact create Odoo Contact records of type contact linked as children of the primary company Partner.

CentralStationCRM Owners map to Odoo Users by email match against the destination Odoo instance's res.users table. Any Owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision before record import proceeds. Odoo Users must be active and have CRM app access assigned for Opportunities to route correctly.

Each CentralStationCRM Deal pipeline maps to an Odoo CRM Stage sequence. We pre-create the stage names, sequence order, and fold status (whether the stage appears collapsed in Odoo's pipeline Kanban view) matching the source before Deals are imported. Stage probability percentages are stored on a custom stage_probability field per stage if the customer requires granular forecasting.