Migrate from noCRM.io to Odoo CRM

noCRM.io Leads map to Odoo crm.lead records. We preserve status (Won, Lost, Cancelled, To-Do, Standby) in the Odoo stage_id and probability fields, and map lead tags to crm.tag records via crm.lead.tag.rel. Custom Predefined Fields from Admin > Sales process > Predefined Fields migrate as typed ir.model.fields on crm.lead (char, text, integer, float, date, selection, many2one). The noCRM lead identifier is preserved in an external_id field for audit trail.

noCRM Pipelines map to Odoo crm.team records. Each Pipeline Step in noCRM maps to an Odoo stage within that team, with stage sequence order and probability percentages preserved. Starter noCRM accounts (1 pipeline) map to a single crm.team; Expert and Dream accounts map to multiple crm.team records. We configure the Odoo sales team in the CRM settings before any lead import begins.

Each noCRM Pipeline Step becomes an Odoo CRM stage with a matching name, sequence, and probability percentage. Step-transition history from noCRM (timestamps and step names) is stored as a custom JSON field on crm.lead or as crm.stage.history records depending on Odoo version. The stage configuration is deployed to Odoo Sandbox before production migration.

noCRM Prospecting Lists are exported as static membership lists with lead references. We map each Prospecting List to an Odoo crm.tag of type 'list' plus a crm.segment record that holds the list name and member Lead IDs. If Odoo Marketing is not installed, Prospecting Lists become crm.tag records that can be filtered in Odoo CRM's kanban view. Large list counts may require manual verification post-migration.

Tags applied to noCRM.io Leads migrate as crm.tag records linked via crm.lead.tag.rel. Multi-value tags on a single Lead create multiple crm.tag records on the same crm.lead. Tag labels are preserved as-is. Odoo's tag model is simpler than noCRM's; any tag color or icon metadata is documented for manual Odoo Studio configuration.

noCRM.io lead activity logs (comments, status changes, step transitions, manual entries) migrate as mail.message records linked to the crm.lead via model='crm.lead' and res_id pointing to the Odoo lead ID. Message subtype (note, communication, stage_change) is inferred from the noCRM log type. Timestamps are preserved from the source. Attachments from comments migrate as ir.attachment records linked to the mail.message.

noCRM.io Users assigned to Leads map to Odoo res.users records. We resolve by email match against the destination Odoo instance. Any noCRM User without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission structures do not transfer directly and must be reconfigured in Odoo Access Rights or via Odoo Studio.

Predefined Fields configured under Admin > Sales process > Predefined Fields in noCRM are extracted with their field types (text, number, date, selection, checkbox). Each is created as a custom ir.model.field on crm.lead in Odoo before the lead import phase. Field labels are mapped from the noCRM admin label to the Odoo field name. Any selection (dropdown) options are created as selection key-value pairs on the Odoo field definition.

Files attached to noCRM.io Leads are exported as binary blobs and reattached in Odoo as ir.attachment records linked to the crm.lead via res_model='crm.lead' and res_id pointing to the migrated lead. File names are preserved. Odoo 18 enforces stricter attachment size limits (25 MB default); files exceeding this are flagged during scoping and split or linked externally as URLs. Attachments stored in noCRM's cloud are downloaded during the extraction phase.

noCRM.io Statistics exports (company performance, team activity, forecasts, lead performance per Prospecting List) are exported as filtered Excel or JSON reports. Aggregate metrics that cannot map to a standard Odoo field are stored in a custom ir.config_parameter or a dedicated report table. Odoo does not have an equivalent native Statistics module; the customer may need Odoo Reporting or a BI tool to replicate dashboards. We document all exported statistics and their Odoo equivalents in the handoff document.

Quotes and Invoices created via noCRM.io's Dream-tier integration are separate linked documents stored outside the standard lead export. We extract them from noCRM's document store, map Quote fields to Odoo sale.order and Invoice fields to account.move, and link them to the migrated crm.lead or res.partner. This requires the Odoo instance to have Sales or Accounting apps installed. We scope this as a separate document migration step if applicable.

noCRM.io Custom Actions (account-specific menu items on lead cards that trigger workflows) have no standard schema and do not transfer as code. We document every Custom Action by name, trigger condition, and intended outcome in the migration handoff. Odoo Studio or a Python developer rebuilds these as Odoo Automated Actions (ir.cron + model methods) or as Studio button actions on the crm.lead form view.