Migrate from Bolten CRM to Odoo CRM

Bolten Contacts map directly to Odoo Contact. We preserve name, phone, email, and custom field values as typed fields in Odoo (text, number, date, selection, or many2one depending on destination field type). Tags stored as multi-checkbox labels migrate to Odoo Tags. Lead-source attribution stored on the Contact migrates to a custom field or the Activity log. We deduplicate on email during import to prevent duplicate Contact creation when multiple Bolten Projects share the same Contact record.

Bolten Leads (separate from Contacts in Bolten's data model) map to Odoo CRM Lead. We preserve lifecycle status, source campaign, owner assignment, and conversion attribution data as custom fields on the Odoo Lead. UTM source and medium values migrate as text fields. Any Bolten Lead that is already converted (status = customer) migrates to an Odoo Contact with a note flagging the original conversion date.

Bolten Deals map to Odoo CRM Opportunity. Bolten's free-text stage names have no enforced ordering property in the API, so we explicitly write an ordinal position (stage_sequence field) during migration based on the customer's confirmed stage order. The pipeline assignment maps to an Odoo CRM Sales Team. Deal value, expected close date, and probability migrate directly. Closed-won and closed-lost reasons from Bolten become custom fields on Odoo Opportunity.

Each Bolten Kanban pipeline becomes an Odoo CRM stage within a Sales Team. We capture stage names and write explicit sequence numbers derived from the customer's confirmed stage order. Odoo enforces stage sequence as a picklist property, so we create the stage in Odoo first, then assign the ordinal sequence number before importing any Deals that reference that stage.

Bolten Tasks migrate to Odoo Project Task or CRM Activity depending on task type. Tasks linked to a Contact or Deal carry the res_id and res_model lookup at migration time. Recurring task rules do not transfer and are documented in the handoff inventory for the customer's admin to rebuild in Odoo Studio. Due date, assignee (mapped via email to Odoo User), and status (new/in_progress/done) preserve directly.

Bolten's full change-audit history per record migrates to Odoo Mail Message records. Each audit entry becomes a Mail Message with author, body, and date preserved. Mail Message records are linked via res_id and model to the parent Contact, Lead, or Opportunity. We batch Mail Message inserts using Odoo's XML-RPC or jsonrpc endpoint with rate-limit handling and parent-record validation to ensure messages attach to the correct record.

Bolten custom fields (text, number, date, dropdown, multi-select) map to Odoo custom fields of equivalent type. We pre-create the destination schema in Odoo via the Settings > Technical > Fields menu or via CSV import of ir.model.fields before any data import. Multi-select fields from Bolten migrate to Odoo tags or many2many relation depending on the target field configuration. Any Bolten custom field with no Odoo equivalent is flagged in the handoff document.

Bolten's lead origin tracking (Google Ads, Meta Ads, direct) and real-time conversion events migrate as custom text fields on the Odoo Lead (utm_source, utm_medium, utm_campaign). Attribution timestamps migrate as custom date fields. The customer should verify UTM reconnection in Odoo's marketing attribution module if they intend to continue paid acquisition tracking.

Bolten Users map to Odoo Users by email match. Suspended or inactive Bolten users are flagged in the reconciliation queue for the customer's admin to map to active Odoo Users before record import. If Bolten has a User not yet provisioned in Odoo, we hold that User's assigned records and import them after the User is created. Owner lookups on Contacts, Leads, Deals, and Tasks all reference User records, so User provisioning must complete before object import begins.

Bolten Tags (flat-label strings on Contacts and Deals) migrate to Odoo Tags. Tags used for deal categorization become Tags on the Opportunity record. Tags used for contact segmentation become Tags on the Contact record. We preserve the tagging relationship per record and flag any tag that appears more than 50 times as a candidate for a dedicated Odoo Stage or Sales Team assignment.

WhatsApp message content cannot migrate because conversations are stored on Meta's servers, not in Bolten's database. We migrate contact phone numbers (already covered by Contact mapping), conversation timestamps as Activity records, and message metadata as Note records on the Contact. A note on the Contact flags that WhatsApp history requires a separate Meta data portability request. The customer should initiate a Meta data export at account.meta.com before cutover to preserve live chat history.

Bolten's AI autofill suggestions auto-populate fields but users sometimes override them without clearing the original suggestion. We migrate the current (user-confirmed) field value, not the AI suggestion history. Any field that shows a discrepancy between the AI suggestion and the final value is noted in the migration report. The AI suggestion log is not accessible via Bolten's standard export and must be requested separately if required for audit purposes.