Migrate from Barantum CRM to Odoo CRM

Barantum Contact records map to Odoo Contact. Standard fields (name, phone, email, website) migrate directly. WhatsApp profile linkage stored on Barantum contacts migrates to the WhatsApp field on Odoo Contact if the destination Odoo instance has a WhatsApp gateway app installed; otherwise it is preserved in a custom field barantum_whatsapp_id__c. Mobile number formatting is normalized from Indonesian format (08xx) to E.164 during transform to ensure Odoo validation accepts the value.

Barantum Company records map to Odoo Company (res.partner with is_company=True). Company-contact parent relationships are resolved by matching the company name field: we create the Odoo Company record first, then link child Contact records via the parent_id field on the Contact. If multiple Barantum contacts share the same company name, we apply a company dedupe rule during import to avoid duplicate Company records in Odoo.

Barantum Deals map to Odoo CRM Opportunity. Deal name becomes Opportunity name; deal value maps to planned_revenue; expected close date maps to date_deadline. The Barantum pipeline stage assignment maps to an Odoo Stage via a customer-approved mapping table created during scoping. Closed-won and closed-lost statuses from Barantum map to Odoo stage categories won and lost respectively.

Barantum pipeline stages are enumerated during discovery and mapped to Odoo CRM stages. Odoo stages belong to a single pipeline per sales team by default; if Barantum uses multiple pipelines, we configure Odoo Sales Teams (crm.team) with separate stage sequences. Stage probabilities from Barantum are stored in custom fields on Odoo stages if the customer requires them, since Odoo stage probability is configured per stage but not exposed as a standard field on the Opportunity view.

Barantum Leads map to Odoo CRM Lead. Lead source, status, and score fields from Barantum migrate to Odoo custom fields (x_barantum_source, x_barantum_status, x_barantum_score) since Odoo CRM Lead does not have native equivalents. Leads are not converted to Opportunities during migration; the customer decides the conversion cadence post go-live.

Barantum Tickets map to Odoo Helpdesk Ticket if the destination Odoo instance includes the helpdesk app; otherwise they map to CRM Lead records tagged with a custom ticket flag. Ticket status (open, in_progress, resolved, closed) maps to Odoo ticket_stage via a mapping table. Agent assignment migrates by email matching to Odoo User. Conversation history on the ticket migrates as Odoo message records on the ticket.

Barantum Meeting records map to Odoo Calendar Event. Title, scheduled time, attendees, and outcome notes migrate directly. Recurring meetings are enumerated and each occurrence is imported as a separate Calendar Event linked to the same CRM record (Lead or Opportunity). Odoo calendar synchronization with external calendars (Google, Outlook) is configured separately post-migration.

Barantum WhatsApp chat threads stored as conversation logs linked to Contact records are extracted as separate note entries during migration. Each message in the thread becomes a line in an Odoo Note (using the note.note model) with the message body, timestamp, sender (agent or customer), and a link to the migrated Contact via a Many2one reference. This approach is necessary because Odoo does not have a native WhatsApp conversation object; conversation threads are preserved as readable note history rather than a threaded chat interface.

Barantum VoIP call logs (call direction, duration, agent extension, recording URL) map to Odoo CRM Log Activities with activity_type set to Phone Call. Call disposition migrates to a custom field x_call_disposition. Recording links are preserved as URLs in a custom field x_recording_url on the activity; the actual audio files are exported as attachments and re-linked post-migration.

Barantum user and agent records are mapped to Odoo User records by email address. We extract the role (admin, agent, manager) and extension number from Barantum and store them in Odoo user fields or custom fields. Odoo User provisioning (creating login credentials) is the customer's responsibility during the migration window; we provide a User mapping worksheet that lists every Barantum user and the recommended Odoo User ID to assign.

Barantum custom fields added to contacts, companies, deals, tickets, or other objects are enumerated during discovery and mapped to Odoo custom fields of matching data type. Text fields map to char or text; numeric fields map to float or integer; date fields map to date; dropdown fields map to selection. Odoo custom fields use the x_ prefix in the database and are created via Odoo Studio or programmatically before migration begins.

Barantum workflow automation rules (auto-assignment, auto-reply, SLA timers) are not exposed through the public API and cannot be migrated programmatically. We enumerate every active workflow during discovery, document its trigger, conditions, and actions in a Workflow Audit Worksheet, and hand this to the customer for manual rebuild in Odoo Studio. Odoo automated actions, server actions, and base_automation rules replicate the Barantum logic; we provide a mapping table that translates each Barantum action type to its Odoo equivalent.