Migrate from CRM.io by 500apps to Odoo CRM

CRM.io Contact records (name, email, phone, company association) map directly to Odoo res.partner records with partner_type set to 'contact'. Email serves as the dedupe key. The CRM.io company-linked contact association resolves to an Odoo res.partner record of type 'company' (the Account equivalent) before Contact import, satisfying the parent partner_id foreign key. Tags on CRM.io Contacts migrate as a comma-separated string into res.partner category_id, which Odoo renders as partner tags.

CRM.io Lead records map to Odoo crm.lead with type = 'lead' (as opposed to type = 'opportunity'). Lead source, status, and owner fields map to crm.lead source_id, stage_id, and user_id respectively. Since CRM.io has no API to retrieve the active pipeline configuration, we infer stage names and order from the Lead records themselves and configure Odoo stage names to match during the setup phase. CRM.io Lead status values are stored as custom fields and mapped to Odoo stage_id values defined in the Odoo CRM pipeline.

CRM.io Account records (business name, industry, size, address) map to Odoo res.partner with partner_type = 'company'. The company ID from CRM.io is stored in a custom reference field on each Contact partner record to maintain the Account-to-Contact link through the migration. Odoo handles industry and company size via custom fields or the built-in industry_id and company_size selection if configured during setup.

CRM.io Deals map to Odoo crm.lead with type = 'opportunity'. Deal stage maps to crm.lead stage_id; deal value maps to planned_revenue; close date maps to date_deadline; owner maps to user_id. The Account-to-Deal link from CRM.io is reconstructed using a compound key of Account name plus Deal value as a fallback when the Account record does not yet have a stable Odoo ID. Pipeline stage order is inferred from the deal records since CRM.io exposes no API to retrieve the active pipeline configuration programmatically.

CRM.io Activity records link to Contacts or Deals. CSV exports do not reliably preserve parent object IDs, so we reconstruct associations using date plus subject matching as a fallback. Call disposition and duration migrate to custom mail.activity fields. Email content migrates as mail.message records attached to the related res.partner or crm.lead. Task migrates as mail.activity with activity_type_id set to the matching Odoo activity type. We perform a multi-pass reconciliation against the Contact and Deal import timestamps to match orphaned activity records.

CRM.io Document Management stores file metadata (filename, type, associated record ID) in the CSV export. Binary files themselves require a separate bulk transfer via secure shared storage or manual re-upload by the customer post-migration. We export the metadata CSV and create ir.attachment records in Odoo with the correct res_model and res_id pointing to the migrated Contact, Account, or Deal, leaving the binary file pointer flagged for the customer's post-migration upload step.

CRM.io record owners map to Odoo res.users via a customer-provided email lookup table. Any CRM.io Owner that has no matching Odoo User goes into a reconciliation queue for the customer's admin to provision before the production migration runs. Inactive CRM.io owners map to inactive Odoo users so that historical assignment is preserved even when the user no longer has active login.

CRM.io pipeline stages for Deals are inferred from deal records since the platform exposes no pipeline configuration via API. We configure Odoo crm.team (sales team) and crm.stage records to match the inferred stage names and order. If CRM.io uses multiple pipelines, we create multiple Odoo crm.team records with corresponding stage sets scoped per team.

CRM.io tags on Contacts and Deals export as comma-separated values in the CSV. We expand these into Odoo res.partner.category (for Contacts) and crm.tag (for Opportunities) records during the transformation phase. Tag records are created first so that the tag IDs are available during Contact and Deal import.

CRM.io Email Templates exist within the platform UI but are not exported via standard CSV. We do not migrate Email Templates as a data operation. The customer should manually export these from within the CRM.io UI if needed, as the template content and merge field syntax will require manual reconstruction in Odoo Mail Template editor.

Forecasting in CRM.io is a reporting view derived from Deals data. Historical forecast snapshots are not independently exported. We recommend rebuilding forecasts in Odoo CRM using crm.lead planned_revenue fields and Odoo's built-in CRM reporting views, which calculate pipeline value from migrated Deal data.

CRM.io explicitly states 'Customization Possible: No' in published specifications. There are no documented custom fields, custom objects, or extended schemas in the source platform to migrate. Odoo's custom field capabilities remain available to the customer's admin post-migration for any new customization needs.