Migrate from ChartMogul to Salesforce Sales Cloud

ChartMogul's parent Customer maps to Salesforce Account. The external_id on the parent Customer becomes the Account's Account Number or an external ID field for cross-reference. ChartMogul's Customer name becomes Account Name. Tags migrate as a multi-select picklist or custom tag field on Account. Custom attributes from the parent Customer map to custom fields on Account, using the API name as a suffix key (e.g., cm_mrr_tier__c). We create these custom fields during schema build before any data moves.

Each ChartMogul Data Source Customer (one per billing source: Stripe, Chargebee, Recurly) maps to a Salesforce Contact on the parent Account. If the same logical customer has multiple billing sources, we create one Contact per Data Source Customer with a custom field ds_source__c (Stripe, Chargebee, Recurly) and ds_customer_id__c holding the billing platform's customer ID for cross-referencing. This preserves the multi-source stitching logic that drives ChartMogul's unified customer view.

ChartMogul Subscriptions have no direct Salesforce standard object. We create a custom Subscription__c object with fields for plan_id, status, quantity, billing_interval, mrr_amount__c, arr_amount__c, and billing_cycle_start__c. Active and trial subscriptions migrate as Subscription__c records linked to the Account or Contact. Cancelled subscriptions migrate with status=cancelled and cancellation_date__c for historical MRR movement attribution. If the customer prefers Opportunity-based subscription tracking, we create a Subscription Opportunity record type with MRR and ARR custom fields instead.

ChartMogul Plan definitions (name, interval, amount, currency, trial period) map to Salesforce Product2 records. The ChartMogul plan_id becomes Product2 ProductCode. We create a Standard Pricebook entry during migration for each Plan so that Subscription Opportunity Line Items reference the correct Product2. Plan pricing history (past plan changes) migrates as separate Subscription records to preserve the MRR movement attribution.

ChartMogul Invoices with line items, amounts, taxes, and transaction fees map to a custom Invoice__c object with Invoice_Number__c, Invoice_Date__c, Total_Amount__c, Currency__c, Status__c, and a relationship to the parent Account or Contact. Each Invoice Line Item maps to Invoice_Line_Item__c with description, quantity, unit_price, and tax_amount. If ChartMogul PDFs are available via the API, we attach them to the Invoice__c record as ContentDocument. The customer chooses Invoice object versus attachment during scoping based on their Salesforce edition and reporting needs.

ChartMogul Transactions (payments, refunds, chargebacks) map to a custom Transaction__c object linked to the Invoice__c record. We capture the transaction type (payment, refund, chargeback), amount, currency, date, and the fee handling flag. ChartMogul's transaction fee handling setting (which deducts fees for Google Play and PayPal) is read during scoping and applied consistently so that net amounts align with the MRR calculations in the destination. If fees were deducted at source, we store both gross and net amounts for accurate reporting.

ChartMogul calculates MRR movements (new business, expansion, contraction, churn, reactivation) from subscription state changes. We import these as MRR_Movement__c records with movement_type__c, amount_change__c, effective_date__c, and a lookup to the parent Account. This preserves the historical MRR waterfall even though Salesforce has no native subscription metrics engine. The customer rebuilds the MRR waterfall visualization in Salesforce Reports or CRM Analytics using these custom records.

ChartMogul CRM Opportunities (deal stages and amounts) migrate to Salesforce Opportunity. The ChartMogul opportunity stage maps to Salesforce StageName, and any ChartMogul deal pipelines map to Salesforce Sales Processes or Record Types that we configure during schema build. Opportunity amount, close date, owner, and probability migrate directly. Closed-Lost and Closed-Won reasons from ChartMogul become Salesforce Loss Reason and custom win_reason__c fields.

ChartMogul Tasks migrate to Salesforce Task. We map due dates, assignees (resolved via email to Salesforce User), completion status, and task subject and body. Open tasks migrate fully; completed tasks with no future action are optionally omitted to reduce import volume. Task status (completed, not completed) maps to Salesforce Task Status (Completed, Not Started).

ChartMogul Notes and call logs migrate as Salesforce ContentNote (Lightning Experience rich text notes) linked via ContentDocumentLink to the parent Account or Contact. Call logs include call disposition and duration where available from ChartMogul, stored as custom fields on the Note record. Plain-text notes migrate as-is; any HTML formatting is stripped to plain text for Salesforce compatibility.

ChartMogul tags are flat string labels on parent Customer records. We migrate them as a multi-select picklist field on Account. The tag set is extracted during scoping, deduplicated, and a picklist value set is created in Salesforce before migration. Tag counts are preserved in a custom field tag_count__c for segmentation filters. Customers with more than 500 distinct tags may choose a custom Tag_Category__c junction object for more flexible segmentation.

ChartMogul Customer-level custom attributes migrate as custom fields on the Account object. We create fields during schema build using the attribute key as the field label and a sanitized API name (e.g., lead_source_detail__c). Attribute type (string, number, date, boolean) maps to the equivalent Salesforce field type. Attributes synced from Pipedrive or HubSpot via ChartMogul's CRM sync are flagged with a cm_origin__c label so the customer knows which attributes are CRM-sourced.