Migrate from ChartMogul to Odoo CRM

ChartMogul's parent Customer record (holding name, email, address, tags, custom attributes, opportunities, notes, and call logs) maps directly to Odoo res.partner. The ChartMogul customer external_id becomes the partner's external_id field for reconciliation. Address data from the parent customer migrates to the partner's address fields; if the customer has multiple billing addresses, child contact records are created under the partner with type set to invoice or delivery.

ChartMogul creates one Data Source Customer per billing source per logical customer. In Odoo CRM without the Subscriptions module, we map these to the parent res.partner with billing source stored in a custom field partner/chartmogul_datasource. If Odoo Subscriptions is installed, each Data Source Customer becomes a separate sale.subscription record linked to the parent partner. The mapping decision is made during scoping based on whether the customer licenses Odoo Subscriptions and whether they want subscription-level MRR tracking in Odoo.

ChartMogul Subscriptions (plan_id, quantity, billing interval, MRR contribution, status) map to Odoo sale.subscription if the Subscriptions module is present, or to sale.order records if it is not. Plan name from ChartMogul becomes the subscription template name; quantity and interval map to recurring_quantity and recurring_interval; MRR contribution is stored as a custom computed field or migrated as note text for admin reference. Active, trialing, and cancelled subscriptions migrate with their status preserved.

ChartMogul Plan definitions (name, interval, amount, currency, trial period) map to Odoo sale.subscription.template. The plan's billing interval maps to Odoo's recurring_rule_count and recurring_rule_type fields. Multiple ChartMogul plans that share the same name and interval are deduplicated into a single template in Odoo during import. If Odoo Subscriptions is not present, Plan definitions are stored as custom fields on the partner record or in a dedicated product template.

ChartMogul invoice records (line items, amounts, taxes, transaction fees, invoice date, status) map to Odoo account.move records with move_type = out_invoice for open invoices and out_refund for credits. ChartMogul invoice number becomes the Odoo invoice reference; invoice date maps to invoice_date. Transaction fee amounts are stored in a custom field on the account.move.line since Odoo does not automatically deduct processor fees like ChartMogul does. The transaction fee handling setting from ChartMogul is read at scoping and applied consistently to all migrated invoices.

ChartMogul transactions (payments, refunds, chargebacks) map to Odoo account.payment records linked to the corresponding account.move. Payment date, amount, and payment_method_type migrate directly. ChartMogul's transaction type field (payment, refund, chargeback) maps to Odoo's payment_type and partner_type. For partially refunded invoices, we create individual payment records that sum to the total refunded amount, linked to the original account.move.

ChartMogul Opportunities (deal stage, value, owner, probability, expected close date) map to Odoo crm.lead. ChartMogul's dealstage property maps to the Odoo crm.stage id via a pre-migration stage name match. Deal value maps to Odoo's expected_revenue or a custom currency-amount field. Owner assignment resolves by email against Odoo res.users, with unresolved owners placed in a reconciliation queue for the customer's admin. ChartMogul's win/loss reasons map to Odoo stage as custom fields or tag values.

ChartMogul deal pipelines (up to 15 on Professional, 100 on Enterprise) map to Odoo crm.team records. Each team gets a name matching the ChartMogul pipeline name and its own Kanban view with stages scoped to that team. If the customer uses only one pipeline in ChartMogul, it maps to the default Odoo Sales Team crm.team.

ChartMogul deal stages map to Odoo crm.stage records within the mapped crm.team. Stage probability percentages migrate from ChartMogul and are stored in the stage record or in a custom field probability_override. Any ChartMogul stage that does not match a default Odoo stage is pre-created before the Opportunity import runs, so that stage_id references resolve at insert time.

ChartMogul tags (flat string labels on the parent Customer) map to Odoo res.partner.category (the Tags model). We create any tag in ChartMogul that does not already exist in Odoo before importing partners. Partner category assignments migrate as ir.model.data records linking the partner to the tag. Tag counts and segmentation filters from ChartMogul are preserved in Odoo as partner category membership.

ChartMogul customer-level custom attributes (key-value pairs) map to custom fields on res.partner created via Odoo Studio before migration. Text attributes become char fields; numeric attributes become float or integer fields; date attributes become date fields; multi-select attributes become char fields with comma-separated values or many2many tag fields depending on cardinality. Attributes synced from Pipedrive or HubSpot via ChartMogul's two-way CRM sync are flagged during scoping so the customer can decide whether to keep them as static values or discontinue the sync in the new Odoo environment.

ChartMogul Notes and Call Logs (unstructured text attached to the parent Customer) map to Odoo mail.message records on the res.partner chatter. We create one mail.message per note or call log with message_type = comment and body containing the original text. Call duration and disposition from ChartMogul call logs migrate as custom fields on the mail.message record. Mail message records are linked to the res.partner via res_id and model so they appear in the partner's activity and communication timeline.

ChartMogul Tasks (due date, assignee, completion status, subject, body) map to Odoo mail.activity records linked to the res.partner. Open tasks migrate with their assigned owner resolved by email to an Odoo res.users record. Completed tasks with no future action are migrated as mail.message records (chatter comments) rather than mail.activity since Odoo activities represent forward-looking work items. The ChartMogul task status (open, completed) determines whether a mail.activity or mail.message is created.

ChartMogul MRR movements (new business, expansion, contraction, churn) are computed metric records tied to subscription state changes. Odoo does not store MRR movements as discrete records; instead, MRR is calculated dynamically from sale.subscription state. We do not migrate ChartMogul's MRR movement table. We migrate the underlying subscriptions and invoices, and MRR is recalculated from those records in Odoo after migration. The customer reviews the recalculated MRR against ChartMogul's last known value as a validation step.

ChartMogul Forecast projections are computed dynamically from MRR trends and are not exportable as structured data. Odoo does not have a native forecast projection feature in its standard CRM or Subscriptions modules (BI reporting is a separate module). We do not migrate forecasts. We deliver a written record of the last known ChartMogul forecast values as reference data so the customer can re-establish their forecasting baseline in Odoo BI or a third-party BI tool post-migration.